James

Hi @Adnn > If this is only those 4 lines, have you tried copying them to the generate() method of the class MyWs(ConanFile): conanfile in the conanws.py? The idea is...

> In our limited situation it is not too bad, but it appears that with medium or large scale projects it might become a maintenance burden. It is possible that...

Hi @sandybhat16 If you want to install "Release" dependencies for both Debug and Release project configurations this is done with: ```bash conan install . -s &:build_type=Release -s build_type=Release conan install...

No, this is not possible in conanfile, conanfiles cannot define settings, only profile/command line arguments can define settings. > s(Other packages need separate debug and release for x86 & x64)....

But you recipe didn't remove the ``build_type``: - I can see that it contains ``settings = "os", "compiler", "build_type", "arch"`` so, the binary depends on ``build_type`` - I can see...

Sorry, I am afraid I still don't fully understand the issue. If I do: ``` conan install --requires=zlib/1.3.1 -g MSBuildDeps ``` Then the generated ``zlib.props`` file contains only the Release...

Hi @sandybhat16 Any further feedback from my last comment above? Thanks for your feedback.

Closing as staled, please re-open or create a new ticket if you have any further feedback.

Hi @vison-yang Thanks for your question. This is not very clear. When using ``cmake-conan`` it is not necessary to call ``conan install`` yourself. Can you please provide the full command...

Hi @HazyMrf Thanks for your question. > Hello! I'm writing conanfile.py to pull gperftools into my project. I need my libraries to be built static as .a files so I...