[PATCH] for libfoo.py
Ralf Habacker
ralf.habacker at freenet.de
Tue Jan 3 15:30:26 CET 2006
David Faure schrieb:
>On Tuesday 03 January 2006 07:14, Christian Ehrlicher wrote:
>
>
>>LIBSUFFIX is the suffix of the static libary and SHLIBSUFFIX is for
>>dynamic libs. The problem here is that win32 needs the static lib
>>(because it's the import lib) and you the dynamic one.
>>I've fixed it by explicit specifying the correct extension and will
>>think over how to handle this.
>>
>>
>
>Thanks; this isn't enough though. It must be .dylib on Mac, and the "lib" prefix is missing
>on unix and mac.
>
>ext=env['SHLIBSUFFIX'] solves the first part (in the non-windows part of the if of course),
>but what about the libprefix?
>I see self.libprefix in generic.py, do we need to put it in env[] so that libjpeg.py can use it?
>
>
>
>>What about linking against a static libjpeg? Should this be possible and
>>how to say this bksys?
>>
>>
>
>I don't know; but I personally don't care much for a static libjpeg ;)
>
>I'm so surprised that scons doesn't handle all of this already. We chose scons
>to avoid developing our own solution from scratch, but in the end it really looks
>like we have no other choice :(
>
>
The configure support of scons seems to be in a very early stage. The
problem is that the compiler/platform detection was performed to late in
the configure process, so that this environment could'nt be used for the
custom configuration process.
I have thoughed already if it would be better to create at first a
initial environment detecting compiler/platform and than in a do the
configure with this environment. bksys uses then the resulting
environment for building. This requires a partial rewrite of the scons
configuration stuff.
I have heard from several other issues reported by Thomas and others. It
is posssible to collect all these issues, so that we can get an overview
and may be able to find a good way out of this problems ?
Does anyone have discussed this issues already with the scons people ?
May be they are aware of this problems and are interested in working
together on a solution for this configure problems.
Ralf
More information about the Kde-buildsystem
mailing list