Building multiple source modules

[Michael Pyne]

On Thursday, January 20, 2011 19:01:39 Michael Jansen wrote:
> > If you're worried about what that means, don't be: kdesrc-build just runs
> > cmake and make like you'd normally do. If you can keep that working for
> > individual projects *and* their supersets that would be awesome. strigi
> > does /not/ work like that unfortunately: It must be built from the strigi
> > supermodule, which then uses CMake to download and build the rest. That's
> > fine as a one-off, but I really think *requiring* supermodules in order
> > to build submodules is a recipe for a great deal of annoyance if that
> > problem spreads.
> 
> Really? Didn't notice that. build-tool is building strigi in 5 steps and i
> did not notice any problems.
> 
> stream
> analyzer
> daemon
> strigiclient
> strigiutils
> 
> I am skipping the strigi repo.

The bug report I received from kdepepo indicated that it's an issue with some 
retained setting. (I didn't have an issue either).

https://bugs.kde.org/show_bug.cgi?id=261638

I guess that if you'd ever built strigi successfully that the version marker 
required for the submodules would have already existed. I've been too lazy to 
just delete all my CMake stuff and try that out though.

Regards,
 - Michael Pyne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-buildsystem/attachments/20110121/3b826c6e/attachment.sig