Re: Library file names

From: David Abrahams (dave_at_[hidden])
Date: 2003-11-28 11:38:19

"John Maddock" <john_at_[hidden]> writes:

>> ALL Of the above are handle by the includes ... the user NEVER sees the
>> name of the file.....EVER and you don't have to change the project, just
>> rebuild with the new includes (of course, since they didn't have to wait 5
>> years for the committee to figure out there's a gaping hole in the spec,
>> they implemented #pragma comment(lib, "libraryname") ) which gets around
>> the USER having to see all the ugliness underneath. Further notice, they
>> didn't have to change anything... install, build, done.
>
> And for Boost on Windows, that will be the reality real soon now, as people
> are starting to place support for windows-style automatic linking in their
> libs, since I documented how to do it (in
> libs/more/separate_compilation.html).
>
> Rene,
>
> On Unix can we add symlinks:
>
> libboost_whatever$(variant).so -> libboost_whatever$(variant)$(version).so
>
> and:
>
> $(prefix)/include/boost -> $(prefix)/include/boost$(version)/boost
>
> I don't know how easy that would be to implement of course :-(

AFAICT that's not needed. As Voldya said, all you need to do is add
-lboost_whatever. Or am I missing something?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com