static library dependencies in gideon
BERND.GEHRMANN at gruppotc.com
Fri Nov 15 15:57:04 UTC 2002
On Friday 15 November 2002 12:57, Brian Gold wrote:
> >> Let's suppose I've got a project (foo) with a subdirectory (bar).
> >> The subdirectory is set to build a static library, and foo links to
> >> it.
> > You should build a libtool library instead. Then the whole dependency
> > tracking is done automatically.
> Agreed, and I have done that for my specific project. However, if the
> "library" option is going to be available when adding a new target in
> autoproject, shouldn't gideon make sure the dependencies work?
Maybe then the library option shouldn't be available in the first place ;-)
> Is there
> a downside to my proposed fix (adding everything in LDADD and LIBADD to
In my experience, it's always good to solve problems where they occur, not try
to work around them in a layer on top. The main problem with KDE's build
system is already that instead of implementing moc and ui file handling in a
build tool written from scratch, it is built on an existing build system and
totally changes its semantics. If you include the IDE as another layer which
messes with the build system, you get another source of errors.
What is the downside of letting libtool do the job?
More information about the KDevelop-devel