Closed jdee closed 4 years ago
@jgsogo OpenSSL definitely sets vcvars: https://github.com/conan-community/conan-openssl/blob/release/1.1.1c/conanfile.py#L488 as we're running conan from the Visual Studio context, it's possible that vcvars variables are already set in this context, but might be for .NET/C# development, or another form. it might be needed to reset some environment variables when launching conan process(es).
I've opened an issue to the Conan repository, I think it is the place to fix it. If the issue doesn't get enough priority we can think about patching it here to the extension. Let's wait for the triaging of that one.
@jdee new release with fix is available on marketplace
Thank you, @SSE4. I found it, and it works well. Sorry for the delay in getting back to you.
Here is an example app using our new conan package and the VS extension: https://github.com/BranchMetrics/cpp-branch-deep-linking-attribution/tree/master/BranchSDK-Samples/Windows/BranchDemo. This SDK is still alpha, but will be released to production and conan-center soon.
The one thing that would be nice for me during testing would be to be able to specify a specific remote to the extension. If there's not an open issue about this already, I'll open one. It's a minor concern.
Thanks for addressing this so quickly!
When using this extension to build a Visual Studio project with Poco, the build step for OpenSSL always fails. I always have to set the build_policy to missing or never and then manually seed the Conan cache. The conan command that the extension attempts to run always fails, but the same command succeeds in a Native Tools Command Prompt. I suspect the vcvars32/vcvars64 environment is somehow not available to the extension, but it's not clear why or how to enable it.
An example project to demonstrate the problem can be found here: https://github.com/jdee/ConanExtensionExample.
Complete VS output from Conan: