Library with nested source file structure
Ingolf Steinbach
Ingolf.Steinbach at jena-optronik.de
Fri Jun 30 13:27:02 BST 2006
Andreas Pakulat schrieb:
> I didn't say you should use symlinks.
Ok. Then, I misunderstood you.
> Just create a subproject for
> include and for src, then in that create subprojects for each module.
> Then you should be able to add whatever filenames you want, they only
> have to be "unique" within that subproject (each subproject maps to a
> directory).
Yes, that works (i.e. adding the files). However, these subprojects do
not each produce a separate library but just contribute to the *one*
library. It is not clear to me how to specify that.
> If you still have problems, please provide the steps to reproduce this
> on a simple automake-based project.
See my example in the original post. The output of the top-
level project should be *one* library plus all the public
header files. The library contains all object files resulting
from compiling the sources in the various modules (i.e.
subprojects).
Kind regards
Ingolf
--
Ingolf Steinbach Jena-Optronik GmbH
ingolf.steinbach at jena-optronik.de ++49 3641 200-147
PGP: 0x7B3B5661 213C 828E 0C92 16B5 05D0 4D5B A324 EC04
More information about the KDevelop
mailing list