[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-windows
Subject:    Fwd: Using msvc solution files
From:       Carlo <brandon.ml () gmail ! com>
Date:       2009-11-10 19:01:02
Message-ID: 3262b6180911101101t26fc2d7ald5e66457b26c9969 () mail ! gmail ! com
[Download RAW message or body]

On Tue, Nov 10, 2009 at 7:49 PM, Alexander Neundorf <neundorf@kde.org> wrote:
> On Tuesday 10 November 2009, Carlo wrote:
>> On Tue, Nov 10, 2009 at 7:03 PM, Peter Kümmel <syntheticpp@gmx.net> wrote:
>> >> Attached my hardcoded solution handling. On problem is that the name of
>> >> the solution, defined by cmake (for instance 'project(Automoc4)') must
>> >> match the internal emerge name self.subinfo.options.make.slnBaseName
>> >> or self.package, maybe someone could help me there.
>> >
>> > It is possible to always use the same solution name?
>> > Is this the intention of 'slnBaseName'?
>> >
>> > Peter
>> > _______________________________________________
>> > Kde-windows mailing list
>> > Kde-windows@kde.org
>> > https://mail.kde.org/mailman/listinfo/kde-windows
>>
>> I don't know about this option, but I wouldn't use the cmake visual
>> studio generator since it breaks at least in kdelibs
>
> What breaks ?
> I'd really like to know, because I can't remember that I heard of that before.
>
> Alex
>

if I remember correctly the problem is in solid, the backends dir has
no CMakeLists.txt
http://websvn.kde.org/trunk/KDE/kdelibs/solid/solid/backends/
and cmake complains that it can't find CMakeLists.txt in that dir even
if it's not needed
_______________________________________________
Kde-windows mailing list
Kde-windows@kde.org
https://mail.kde.org/mailman/listinfo/kde-windows

[prev in list] [next in list] [prev in thread] [next in thread]