Re: [Boost-build] "install" rule strange behaviour

Subject: Re: [Boost-build] "install" rule strange behaviour
From: dimak (dvb.kharkov_at_[hidden])
Date: 2012-08-30 11:29:41

Volodya,

Thank you for your answer. You explain this really good, thanks! I've tried
your "force copy" solution using <hardcode-dll-paths>, and it works - two
links are made to "bin" and "inst" directories. However I do not want to
have binary at "bin" which is not built with -Wl,-rpath and thus requires
library paths (e.g. LD_LIBRARY_PATH) modifications. Following algorithm you
underlined I change the building file in this way:

exe app : app.cpp /library-example/foo//bar ;                                                              
                                                                                                                                       
install inst : app ;                                                                                                                   
explicit inst ; 

So yes, explicit rule invocation is still here, but we hide "inst" from
direct invocation. And when we run "bjam inst", we, as I thought, make it
"visible" and thus link to "inst" directory should be done. And it is indeed
done, but again... no link to "bin" directory! In this case, in-tree
executable is not "explicit". Volodya, could you please clarify why it is
not still working for me?

PS I am hiding "inst" via "explicit" as I do not want installation to be
performed by default, but explicitly using "bjam inst".

Best regards,
Dima

--
View this message in context: http://boost.2283326.n4.nabble.com/install-rule-strange-behaviour-tp4634962p4634968.html
Sent from the Boost - Build mailing list archive at Nabble.com.