Re: [jamboost] <file> specifier in library causes Duplicate name for actual target

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-02-10 07:32:50

Hi Michael,

> It seems to have gone quite with regards to "Duplicate name for actual
> target" errors. The latest CVS HEADshows there seems to be at least one
> more case that is problematic. Following test Jamfile shows the problem.
>
> # Jamfile - See Boost.build v2
> # Test for duplicate name for <file> library problem
>
> # System libraries - specify local link requirements for lapack
> lib lapack : : <file>"lapack.a" ;

The <file> feature is going to be deprecated in M10 and removed some time 
after that. You can use

alias lapack : : lapack.a ;

to achieve the same effect. The reason <file> will go away is because it 
precisely because there's another equivivalent. Moreover, there's hidden 
code duplication -- and <file> handling is a bit broken with respect for 
handling of "libpack.a" in sources.

HTH,
Volodya