SpaceIm

I don't know whether it's fully compliant with conan v2, but this workflow should work with modern conan generators. In project root folder: - conanfile.txt ```ini [requires] foo/x.y.z bar/u.v.w [generators]...

> I'm also interested in having multiple profiles for the install command. I have seen a few examples make use of multiple `-p:...` arguments. It's 2 profiles. AFAIK, in conan...

> I see. Is it safe to just auto-detect the initial profile and use that for both contexts? I guess since the target platform is the host platform in the...

I have created libdeflate recipe in conan public repository, and I'm also interested in CMake support in libdeflate. Indeed libdeflate is now an optional dependency of libtiff (since 4.2.0) and...

> @SpaceIm / how you could you add your proposed changes to this PR ? By making a PR in my repo ? Sure.

@bsergean Please consider https://github.com/bsergean/libdeflate/pull/1 - fix export of symbols for non-Windows if shared - change target to libdeflate, and imported target to libdeflate::libdeflate - honor lib name from original Makefile...

another one: https://github.com/bsergean/libdeflate/pull/2 MinGW is broken by the way (for utility & tests). `-municode` must be injected during compilation of the the utility & tests, but I can't make it...

> Integration with other projects via imported targets is an antipattern, pkg-config exists and has the benefit of working with projects that aren't cmake. It's not an anti-pattern. C++ ecosystem...

I don't know which symbol is not exported. But you have to be aware that `CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS` (which is bad practice, this should only be a temporary workaround) can't export global...

It's not a recipe issue. Please report this error to conan client (AFAIK it's a known issue of conan v1 mode with layout).