Re: [jamboost] Question on patch

From: Rene Rivera (grafik666_at_[hidden])
Date: 2001-12-18 18:21:17

Dave,

Sorry for the delayed response, I'm in the middle of takling Win32 & cross DLL
memory problems :-(

On 2001-12-18 at 03:19 PM, david.abrahams_at_[hidden] (David Abrahams) wrote:

>Why did you comment out these lines in gcc-stlport-tools.jam?
>
># STDHDRS = ;
># STDLIBPATH = ;
>
>The point was that whatever was given by the gcc toolset should be replaced
>by what we calculate in this toolset. This could be important in the case of
>stlport, since the stlport paths must precede the system-supplied paths. The
>flags rule might otherwise just tack the new STDHDRS values onto the end of
>the existing list.

Those lines where reseting the values AFTER they where set by the <sysinclude>
use. Which is why I changed the GCC tools to put the includes in the system
path "-isystem" which places them before any defaults of the compiler.
Unfortunately I only have GCC on Linux to test this with so I don't know
wether this works in the other GCC installations :-( And at least for me (on
Linux) the GCC_INCLUDE_DIRECTORY and GCC_STDLIB_DIRECTORY are always empty.

I'll try and see if I can make both of them work together, probably using a
different variable that the other tools use, like STLPORT_INCLUDE_DIRECTORY
and STLPORT_STDLIB_DIRECTORY.

>You added "lib" to the beginning of the library name for gcc-stlport to
>find. I'm pretty sure that won't work, since the -l option automatically
>prepends "lib". So there would have to be a library called
>"liblibstlport_<version>.a". Did you test this change?

Hmmm, don't know why I did that... I don't even remeber doing that change :-\
I know I changed the literal version number that was on the dynamic version
because to me it made more sense to point to the symbolic link instead of the
specific version. Which thinking about it would cause problems with stlport
system that don't generate the symlink during the build. So that change would
also not work on non-*nix types like Windows with GCC.

Which begs the question, which I saw someplace else, probably in the TODOs, of
better support for stlport than using the tools approach. Because as it is it
will never work for everyone :-(

-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq - Grafik666_at_AIM - Grafik_at_[hidden]