$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-12-02 04:11:30
On Thursday 02 December 2004 11:52, Vladimir Prus wrote:
> Hi,
> the code which is responsible to v1 install of Boost, in top-level Jamfile,
> uses HardLink to create links to shared libraries on Unix:
>
> HardLink $(noversion-file) : $(version-file) ;
>
> Why hard link is used? I always though symlink should be used; all
> libraries use symlinks on my system.
>
> Any comments?
Also:
ls *
libboost_program_options-gcc-d-1_32.a
libboost_program_options-gcc-d.a
libboost_program_options-gcc-d-1_32.so
libboost_program_options-gcc-d.so
libboost_program_options-gcc-d-1_32.so.1.32.0
1. Why there's no
libboost_program_options-gcc-d-1_32.so.1
linking to
libboost_program_options-gcc-d-1_32.so.1.32.0
2. Why there's both
libboost_program_options-gcc-d.so
and
libboost_program_options-gcc-d-1_32.so
3. Why do we need "1_32" duplicated in:
libboost_program_options-gcc-d-1_32.so.1.32.0
Overall, I'd expect a library file to be named
libboost_program_options-gcc-d.so.1.32.0
and have
libboost_program_options-gcc-d.so
libboost_program_options-gcc-d.so.1
symlinks.
Comments?
- Volodya