Luis Martinez

Hi, the new environment mechanism in develop2 should work just fine for these cases, because all the environment is wrapped in a "bat" or "sh" launcher, then the `self.run` command...

> Something similar happens if we want, leaving the fPIC=True default, to change to False those that are static libraries not reused by shared ones, it would be quite challenging...

There is another use case that might be valid for this cpp_info new model, the COM objects from @thorntonryan https://github.com/conan-io/conan/pull/11601#issuecomment-1243880002 > Importantly the consuming application doesn't link directly against these...

> From a documentation perspective, what is a meson "user filename"? Shouldn't this use a name more evocative of the fact that Meson calls them native machine files? But there...

Thanks for reporting. Do you have a `capnproto` branch that we can use to reproduce this?

Hi, I was trying a patch for this but: > I would have expected: > /Users/spaceim/.conan/data/capnproto/0.10.1/_/_/package/86b3b8f1d2506eef508c4383f35d09efc02ebc0b/bin/capnp: > @rpath/libcapnpc-0.10.1.dylib (compatibility version 0.0.0, current version 0.0.0) That won't work either, because when...

@uilianries In develop (Conan 1.X) we have a known different behavior with the `settings` and the `info`. We want, by looking into this issue, the different use cases, and possibly...

I think this might be solved already by this PR: https://github.com/conan-io/conan/pull/12049/files If you could confirm, it would be very nice. Thanks

You could add my remote, checkout the branch of the PR and install that conan version: ``` git remote add lasote https://github.com/conan-io/conan.git git fetch lasote git checkout feature/test_cmakedeps_config_mapping pip install...

Oh, my mistake, my remote is `git remote add lasote https://github.com/lasote/conan.git`