[Boost-build] hardcode-dll-paths in shared lib

From: Jorge Suit Perez Ronda (josp.jorge_at_[hidden])
Date: 2006-12-27 21:18:15

Hello, I build a shared lib A which use a prebuilt shared lib B. The lib
is installed in a non-standard place /usr/local/B/lib

lib B : : <search>/usr/local/B/lib ;
lib A : sources_of_A B ;
exe C : sources_of_C A ;

when the project is built C "know" where B is, but A does not "know"
where B is. Is there a way that B location be "hardcoded" into A in the
same way as it is in C?

regards,

Jorge