[question] Should XCRun use the conanfile's build env?

[sfackler]

What is your question?

I realized that #14195 doesn't fully solve the issues I was having when doing a Linux -> macOS cross build, since XCRun still assumes that xcrun is in the ambient PATH. I can work around it without too much trouble by just doing:

with VirtualBuildEnv(self).vars().apply():
    fix_apple_shared_install_name(self)

but ideally the tool would apply the build env internally.

Have you read the CONTRIBUTING guide?

• I've read the CONTRIBUTING guide

[memsharded]

Hi @sfackler

I just realized that XCRun() is not fully applying Conan profiles PATH env-var.
If something like this:

[buildenv]
PATH+=(path)/path/to/my/cross/xcrun

That would be a good solution, wouldn't it?

Note I don't think with VirtualBuildEnv(self).vars().apply(): is a good solution, doesn't look great.

[sfackler]

I think you'd probably want the whole build env applied for things like LD_LIBRARY_PATH.

[memsharded]

Yes, exactly, I am trying to do #14326, so whatever you inject in the profile is used to run xcrun.

[memsharded]

#14326 was merged, it will be in next 2.0.10 release

[sfackler]

Thanks!