Discussion: build.py output path override

[headupinclouds]

This is probably a rare use case, but...

If a hunter (or any CMake) project resides on a disk that is shared across different machines, then it is possible for the same toolchain (say libcxx) to be run multiple times, which could lead to collisions. Currently, I don't think there is a way for a user to override the generated ${PROJECT}/_{install,build}/${TOOLCHAIN} paths. It is easy enough to create a dummy libcxx-linux.cmake or libccxx-osx.cmake toolchain to accomplish this, but there might be other scenarios where the user may want to modify or append to the generated path as well.

[ruslo]

that is shared across different machines

Well this may be a problem even for the one machine. In case user add clang 3.4 in PATH and then changing it to clang 3.5. libcxx will pick up different compilers, this is a task for the Hunter toolchain-id calculation module.

What about adding --toolchain-dir option? Say --toolchain libcxx --toolchain-dir libcxx-osx and --toolchain libcxx --toolchain libcxx-linux?

[headupinclouds]

That sounds good. I think I can probably add that.

On Mon, Nov 23, 2015 at 6:03 PM, Ruslan Baratov notifications@github.com
wrote:

that is shared across different machines

Well this may be a problem even for the one machine. In case user add clang
3.4 in PATH and then changing it to clang 3.5. libcxx will pick up
different compilers, this is a task for the Hunter toolchain-id calculation
module.

What about adding --toolchain-dir option? Say --toolchain libcxx
--toolchain-dir libcxx-osx and --toolchain libcxx --toolchain libcxx-linux
?

—
Reply to this email directly or view it on GitHub
#51 (comment).