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

List:       kde-sdk-devel
Subject:    Re: KDESDK to git migration: Build system changes
From:       Sebastian_Dörner <sebastian () sebastian-doerner ! de>
Date:       2012-05-23 23:05:37
Message-ID: CA+_kBjDwNOc_sHpwP-MWj=mxPMyUDUzT=4sJnB_LEnjrauchZw () mail ! gmail ! com
[Download RAW message or body]

Thanks for your insight, Jeremy.

List: I'm adding this bit to the process section of our wiki page.

On 23 May 2012 22:56, Jeremy Whiting <jpwhiting@kde.org> wrote:
> This is correct. =A0When we migrated kdeedu to git, we first made each
> application buildable as a separate project. =A0(And made the top
> CMakeLists.txt just a list of add_subdirectory( blah ). =A0That way it
> is buildable as a whole tarball and as individual projects. =A0The
> trouble lies in if parts of kdesdk depend on other parts at build
> time. =A0Kde edu hit this issue because of libkdeedu, but I don't think
> kdesdk has that problem.
>
> thanks,
> Jeremy
>
> On Wed, May 23, 2012 at 3:29 PM, Sebastian D=F6rner
> <sebastian@sebastian-doerner.de> wrote:
>> Hi,
>> how does the new structure works in terms of building?
>>
>> So far we have one top-level CMakeLists.txt for the whole of KDESDK.
>> This seems to be useful for releasing a KDESDK tarball to end users /
>> distributions. However I suppose that every single repository should
>> have an independently-working build file in its own root directory,
>> i.e. one that does not depend on the KDESDK one for finding stuff out
>> (as is the case now).
>>
>> Can anyone confirm or correct this?
>>
>> Regards
>> Sebastian
>> _______________________________________________
>> kde-sdk-devel mailing list
>> kde-sdk-devel@kde.org
>> https://mail.kde.org/mailman/listinfo/kde-sdk-devel
_______________________________________________
kde-sdk-devel mailing list
kde-sdk-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-sdk-devel
[prev in list] [next in list] [prev in thread] [next in thread]