Luis Caro Campos

Hi @rturrado - 1. Yes, you should be able to set this as well. Bear in mind that this is currently autodetected based on whether `CMAKE_CXX_STANDARD` is defined (if you...

Hi @tim-goto, thank you for your contribution. @memsharded - the proposed logic more or less matches what the `CMakeToolchain` does by setting `CMAKE_PROGRAM_PATH`. This overcomes one of the limitations mentioned...

Indeed! What would work for all platforms is evaluating the value for `CMAKE_SYSTEM_PROCESSOR` (which should reflect the 32-bit intel architecture if the `CMAKE_GENERATOR_PLATFORM` was `x86`) - and then map the...

From what I remember, Visual C++ does not really have compiler flags for C++11 (Starts with C++14, docs [here](https://learn.microsoft.com/en-us/cpp/build/reference/std-specify-language-standard-version?view=msvc-170)), so that's what Conan mirrors and that's why there is an...

Hi @irieger - thanks for reporting this issue. There are two aspects of this - what happens at link time (where cmake passes the `-rpath` flag), and what happens at...

> An example is here: https://github.com/irieger/cpp-playground/tree/main/ocio-conan-dynamic-linking The given link shares a docker for having a clean build env & a modified recipe for OCIO that allows building it as a...

Thanks @irieger - I've been able to reproduce this with your repository. I have a question: this only fails with the changes you have made to the `opencolorio` recipe -...

> Any idea how we could properly improve that or what the underlying problem might be? Why is a linker even caring what a so that is being linked into...

Thanks @EstebanDugueperoux2 - glad to hear this works, as it confirms the issue. For what it's worth, I suspect the linker will still produce exactly the same files (assuming the...

Hi @hoyhoy, thanks for your contribution. - Please note that we no longer consider or prioritize PRs to bump versions of dependencies unless a reason is provided in the PR...