Skip to content
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

support list in conan command during version check #668

Open
wants to merge 1 commit into
base: develop2
Choose a base branch
from

Conversation

oleksandr-prykhodko-quickbase

We have custom wrapper around conan command and use it in cmake as set(CONAN_COMMAND "py;conan_command.py")
Passing it to conan_get_version unwraps it as a list thus version check calls whatever is first in the list instead of the whole command.

@CLAassistant
Copy link

CLAassistant commented Aug 27, 2024

CLA assistant check
All committers have signed the CLA.

Copy link
Member

@memsharded memsharded left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution @oleksandr-prykhodko-quickbase

@@ -560,7 +560,7 @@ macro(conan_provide_dependency method package_name)
get_property(_conan_install_success GLOBAL PROPERTY CONAN_INSTALL_SUCCESS)
if(NOT _conan_install_success)
find_program(CONAN_COMMAND "conan" REQUIRED)
conan_get_version(${CONAN_COMMAND} CONAN_CURRENT_VERSION)
conan_get_version("${CONAN_COMMAND}" CONAN_CURRENT_VERSION)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not very clear. The CONAN_COMMAND variable is the one defined in the above find_program(), not a custom defined one, but you said you defined it as set(CONAN_COMMAND "py;conan_command.py"). Where did you defined it? And how it gets to this location with that value?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your script defines this variable at this point, but you don't own it—we can define it too! :)

At the beginning of CMakeLists.txt, we set up various configurations, including the CONAN_COMMAND. Because of this setup, CONAN_COMMAND is not being set by the find_program() call mentioned above (as described in the documentation: 'If the program is found, the result is stored in the variable, and the search will not be repeated unless the variable is cleared.').

As a result, we define CONAN_COMMAND before any actual work is done, meaning that when find_program() is invoked later, it effectively does nothing.

The conan_provider is used as advised with -DCMAKE_PROJECT_TOP_LEVEL_INCLUDES=../conan_provider.cmake. When CMake retrieves dependencies from Conan, conan_provide_dependency is called. By this point, our pre-setup has already executed, and CONAN_COMMAND has been set.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But that approach is a bit risky, isn't it? If there is some other Conan installed in the system, the find_program() will find it and use it, while your intention was to use your own wrapper always, is that correct?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, no sorry, you are right, if the find_program() finds that it is set, it will not even try to find it, reusing, it.
Understood, thanks for the clarification!

Copy link
Member

@memsharded memsharded left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I am fine with this change, but will assign @jcar87 to review.

Thanks for your contribution @oleksandr-prykhodko-quickbase

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants