Originally posted by kpedersen
View Post
Thats where dependency management comes in, ideally you DL a source package on *any* platform and can compile for *any* target and dont inadvertently use mismatched headers/libraries from the host.
This is completely independent from installing stuff for your host, it makes sure you get the dependencies your target needs, whether these are DSO or static libs.
Originally posted by kpedersen
View Post
I am using CMake + Conan and the project is a normal CMake project which just uses the normal method to find stuff (find_package, etc).
Run normally, it will resolve the host's libraries. If I run conan before it will download or compile dependencies, prepare them in a folder in your subdirectory and generate a configfile so CMake finds them. The only difference to a "pure" CMake project is that I include that generated configfile if it exists.
If id push this package into, say debian, it would use the distros way of fetching dependencies. Again, this is purely a developer tool.
And if you build a cross-platform library, everything will work in Windows or Mac the same way.
Comment