-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conan 2 #373
Conan 2 #373
Conversation
Noticed while I was updating CI and documentation that at the moment, the Dependencies doc says:
That isn't true - hasn't been true for a long time now. However, we haven't changed this because the required library is different on Windows (mDNSResponder) than on Linux (Avahi or mDNSResponder), and that can't be expressed in a simple conanfile.txt. It would be good to improve this, as it would simplify the build even further. We could adopt the CCI conanfile.py which expresses the necessary logic. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Not sure whether we want to note anywhere what a user will experience if they are not ready for the migration, which requires:
If they try to use previous
If they have conan 1.X but do use the new
|
How about under the Recent Activity, we extend and bold the wording |
I've started investigating how to use Conan 2 with earlier versions of CMake, by manually running Approximately... mkdir build
cd build
conan install .. -g CMakeToolchain --settings:all build_type=Release --build=missing --output-folder=conan
conan install .. -g CMakeToolchain --settings:all build_type=Debug --build=missing --output-folder=conan then either... (hmm, this doesn't work because the generated CMakePresets.json is in the build/conan directory not the source directory) cmake .. --preset conan-default -DCMAKE_CONFIGURATION_TYPES="Debug;Release" or... (this does seem to work...) cmake .. -G "Visual Studio 16 2019" -DCMAKE_TOOLCHAIN_FILE=conan/conan_toolchain.cmake -DCMAKE_CONFIGURATION_TYPES="Debug;Release" |
NMOS_CPP_USE_CONAN
cache variable is no more, but there are two newNMOS_CPP_USE_SUPPLIED_xxx
options to use the supplied json-schema-validator and jwt-cpp if you're not using ConanCMAKE_PROJECT_TOP_LEVEL_INCLUDES
must be used explicitly, which is documented in the Getting Started guide (see Dependency Providers for the rationale)