On Wed, Dec 19, 2018 at 11:24 AM Peter Dimov via Boost wrote:

Our "b2 --help" documentation says

--exec-prefix=<EPREFIX> Install architecture dependent files here. Default: <PREFIX>

--libdir=<LIBDIR> Install library files here. Default: <EPREFIX>/lib

and bootstrap.sh also supports --exec-prefix and when given, records it in project-config.jam.

But it doesn't work and has never worked. Only --prefix is honored, --exec-prefix is simply ignored.

I think that we should bring the documentation and the actual behavior in sync, either by making --exec-prefix work as documented, or removing it from the documentation.

Which one should we do? Comments?

If there isn't an open issue in Boost.Build for it, then it probably isn't important enough to implement. - Jim

On 2018-12-19 11:13 a.m., Peter Dimov via Boost wrote:

Our "b2 --help" documentation says

--exec-prefix=<EPREFIX> Install architecture dependent files here.                        Default: <PREFIX>

--libdir=<LIBDIR>       Install library files here.                        Default: <EPREFIX>/lib

and bootstrap.sh also supports --exec-prefix and when given, records it in project-config.jam.

But it doesn't work and has never worked. Only --prefix is honored, --exec-prefix is simply ignored.

I think that we should bring the documentation and the actual behavior in sync, either by making --exec-prefix work as documented, or removing it from the documentation.

Which one should we do? Comments?

I believe $exec_prefix is a relict of the past, so I'd suggest we remove it, given that it wasn't ever working. Stefan -- ...ich hab' noch einen Koffer in Berlin...