Re: [jamboost] back to paths

From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-07-23 14:21:29

[2003-07-23] Paul Schmidt wrote:

>First, many thanks to everyone who's helped out so far- I'm making
>progress; sorry to be such a n00b.
>
>I'm back to a path problem, I think. I've got a jamfile:
>
>#jamfile for $(Top)EE/Hello
>
>subproject ee/hello ;
>
>exe hello
> : hello.c crt0.s <lib>../init/init
> : <instruction-set>ee <include>../include
>;
>
>The problem is, according to the output (-d2) the path to the library
>specified comes out as:
>
><ee!init\init.a\snps2\debug\instruction-set-ee>init.a
>
>Yes, I recall that someone pointed out this is internal syntax that
>can be ignored in most debug output, but it'ss appearing in the
>command line for the linker, and of course the linker can't find the
>file as specified. 

Very strange!

>Previously, I was not seeing the library passed to the linker at all,
>until I finally figured out that I needed to add $(NEEDLIBS) to the
>link action in the toolset. But clearly, there's some translation that
>has to occur before the command line is formed, but it's not
>happening. Help?

Well normally the translation is done automatically, but I can't think of
why it would not happen.

Could send me a test case that I can look at? No need to include source code
just the Jamfiles/Jamrules and the toolset itself. Of course the smaller the
test case the better ;-)

-- grafik - Don't Assume Anything
-- rrivera (at) acm.org - grafik (at) redshift-software.com
-- 102708583 (at) icq