James

Hi @NetVince Yes, if you want to implement a general compatibility policy between intel-cc and gcc, the recommended way would be the ``compatibility.py`` plugin, not the method. If you want...

The mechanism and definition is almost the same, just defined externally to conanfiles, in a ``compatibility.py`` file that you put in the cache (and can be shared and distributed with...

If you want to explicitly specify the compiler for specific packages, using the above syntax: ``` [settings] compiler=intel-cc compiler.version=xx ... mypkg/*:compiler=gcc mypkg/*:compiler.version=14 ``` You can use the ``&`` placeholder to...

Which Conan version? Which ``log4cxx``, the one from ConanCenter? Can you please share the full output of your command? (hint, use triple backticks to format correctly, not single backticks)

I see. > It's not the one from ConanCenter, it comes from a mirroring repo on our own network. You are running with an old, no longer maintained version of...

Now you have a missing binary message, that is totally expected, as there is no pre-compiled binary for ``intel-cc``, you need to build the binary for that ``intel-cc`` and upload...

> Unfortunately, I can't build it. No access to internet on my network. There is no way to tell Conan that packages compiled with GCC are compatible with my profile...

Yes, exactly, it seems you want the other way round: - Dependencies with ``gcc`` - Your own consumer with ``intel-cc``. That is represented by the opposite: ``` [settings] compiler=gcc compiler.version=14...

Yes, you can either explicitly tell in the profile: ``` [settings] compiler=gcc compiler.version=14 ... dep1/*:compiler=intel-cc dep1/*:compiler.version=2024.X ... &:compiler=intel-cc &:compiler.version=2024.X ... ``` (Note, there are mechanisms to write this in a...

> The problem is log4cxx has dependencies also compiled with GCC. What should I modifiy to tell Conan that requirements can be either from GCC or intell-CC. The recommended way...