Re: [jamboost] Stage targets for V2

From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-11-10 17:36:04

[2002-11-10] Vladimir Prus wrote:

>Rene Rivera wrote:
>Okay.. I seem to understand this better now, thanks. One more question on
topic:
>is there a way to hardcode the path to shared library in exe? I want it in
>order to avoid setting LD_LIBRARY_PATH when debugging, when libraries live
>in build directories.

Yes, you can, and this is what I do in my projects for debug binaries also.
In V1 I have this set for all my targets:

<gcc><linkflags>"-Wl,-rpath -Wl,."
<gcc><linkflags>"-Wl,-rpath -Wl,$(GCC_STDLIB_DIRECTORY)"

>> Yes, that would be a good way to get both uses. In fact it might be
usefull
>> to specify that for each source in the stage. Basically allowing to
create
>> symlinks in the stage to arbitrary other targets.
>
>Nice idea. We'd need a mechanism for specifying different processing for
>different sources, though.

Any ideas on how to do that? I'll think about it.

>>>Then we should allow either directory or category for stages, not both.
>> 
>> 
>> Yes, good point. Any idea on syntax to differentiate them?
>
>Nothing especially bright, other then prepending something to
>category.

:-( ... Lik above I'll think about something.

>We have DLL target: "lib". Whether "lib" target generates static or shared
>library is determined by the value of "shared" property.

Yes, I saw after I started looking a bit after my post ;-)

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