List Info

Thread: controlling library names




controlling library names
country flaguser name
United States
2007-07-29 15:54:40
I am using Boost.Build V2 (Milestone 11) Boost.Jam 03.1.15.

I am now at the stage when I want to alter the library names
that a lib 
rule builds so I can move both release and debug into a
common directory 
via a stage rule.

What I want to know is the simplest way to append a
"-d" to the base 
name of the debug library.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Re: controlling library names
user name
2007-07-29 18:51:55
Jeffrey Holle wrote:
> I am using Boost.Build V2 (Milestone 11) Boost.Jam
03.1.15.
>
> I am now at the stage when I want to alter the library
names that a lib 
> rule builds so I can move both release and debug into a
common directory 
> via a stage rule.
>
> What I want to know is the simplest way to append a
"-d" to the base 
> name of the debug library.
>   

I don't know if it's the simplest way to do it, but here's
how I do it: 
http://article.gmane.org/gmane.comp.lib.boost.build/130
19

HTH,

Phillilp
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Re: controlling library names
country flaguser name
United States
2007-07-29 20:50:04
Phillip Seaver wrote:
> Jeffrey Holle wrote:
>> I am using Boost.Build V2 (Milestone 11) Boost.Jam
03.1.15.
>>
>> I am now at the stage when I want to alter the
library names that a lib 
>> rule builds so I can move both release and debug
into a common directory 
>> via a stage rule.
>>
>> What I want to know is the simplest way to append a
"-d" to the base 
>> name of the debug library.
>>   
> 
> I don't know if it's the simplest way to do it, but
here's how I do it: 
> http://article.gmane.org/gmane.comp.lib.boost.build/130
19

After simplified the rule that you pointed me to, I get a
syntax error 
on this line:
local extension = [ type.generated-target-suffix $(type) :
$(property-set)

I did an "import type ;" line in addition in my
Jamfile, but it didn't help.

Any help appreciated.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Re: controlling library names
country flaguser name
United States
2007-07-29 23:40:17
In looking at an old related email that Vladimir wrote, I
found this 
rule that looks like it is exactly what I want:

rule my-tag ( name : type ? : property-set )
{
    if $(type) = LIB && [ $(property-set).get
<variant> ] = debug
    {
        return [ virtual-target.apply-suffix $(name)_d :
$(type): 
$(property-set) ] ;
    }
}

But it preforms as a NOOP.
I assume that why it doesn't work is because Boost.Build has
changed 
alot in 2 years.

Can anyone point out what wrong?

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Re: controlling library names
country flaguser name
United States
2007-07-30 00:28:15
Never mind, I fixed it myself, after discovering that
"echo" works.

rule my-tag ( name : type ? : property-set )
{
    if $(type) = STATIC_LIB && [ $(property-set).get
<variant> ] = debug
    {
        local result = [
virtual-target.add-prefix-and-suffix $(name)_d 
: $(type) : $(property-set) ] ;
        return  $(result) ;
    }
}

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Re: controlling library names
country flaguser name
United States
2007-07-31 10:12:40
on Sun Jul 29 2007, Jeffrey Holle
<jeffreyholle-AT-bellsouth.net> wrote:

> Phillip Seaver wrote:
>> Jeffrey Holle wrote:
>>> I am using Boost.Build V2 (Milestone 11)
Boost.Jam 03.1.15.
>>>
>>> I am now at the stage when I want to alter the
library names that a lib 
>>> rule builds so I can move both release and
debug into a common directory 
>>> via a stage rule.
>>>
>>> What I want to know is the simplest way to
append a "-d" to the base 
>>> name of the debug library.
>>>   
>> 
>> I don't know if it's the simplest way to do it, but
here's how I do it: 
>> http://article.gmane.org/gmane.comp.lib.boost.build/130
19
>
> After simplified the rule that you pointed me to, I get
a syntax error 
> on this line:
> local extension = [ type.generated-target-suffix
$(type) : $(property-set)

Add a trailing semicolon?

-- 
Dave Abrahams
Boost Consulting
http://www.boost-cons
ulting.com

The Astoria Seminar ==> http://www.astoriasemin
ar.com

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[1-6]

about | contact  Other archives ( Real Estate discussion Medical topics )