new profile [runenv] section

[memsharded]

Changelog: Feature: Implement a new [runenv] section in the Profile, to define the runtime environment.
Docs: conan-io/docs#2771

I hit this limitation while preparing docs for Windows-CLang integration:

• When building for Msys2-Clang, I can add [buildenv]...<path/to/clang/bin> so the clang compiler is found
• But when I am executing a test_package test() or something in the "run" scope, like self.run("myexe", env="conanrun") it will fail, because it cannot find the libc++.dll and libunwind.dll shared libs in the msys2 clang folder.

[jcar87]

Just a very minor comment.

But when I am executing a test_package test() or something in the "run" scope, like self.run("myexe", env="conanrun") it will fail, because it cannot find the libc++.dll and libunwind.dll shared libs in the msys2 clang folder.

Is this with a clang-cl.exe or clang++.exe that are not part of a "system" package or similar? Otherwise I'm surprised libc++.dll is not already found in the "default" search path in this environment (although I'm not very familiar with msys2)

[memsharded]

Is this with a clang-cl.exe or clang++.exe that are not part of a "system" package or similar? Otherwise I'm surprised libc++.dll is not already found in the "default" search path in this environment (although I'm not very familiar with msys2)

Yes, the msys2 clang++.exe can be installed in a custom location, like C:/msys2/clang64/bin/clang++.exe. This C:/msys2/clang64/bin folder can be indeed added to the system PATH and everything will work. But if this folder is not added, and it is defined in the Conan profile (which makes sense if we are dealing with multiple compilers and versions), then, the libc++.dll will not be in the path either.

This behavior is hidden because in test we add the pytest.mark.tool("msys2") to the test, which injects the path to msys2 during the whole test.