-
Notifications
You must be signed in to change notification settings - Fork 22
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
Cloe recipes: Fix ABI compatibility issues #251
Merged
scpa1055
merged 22 commits into
eclipse:develop24_x
from
fgguidi:feature/add-strict-mode-to-recipe
Jul 26, 2024
Merged
Cloe recipes: Fix ABI compatibility issues #251
scpa1055
merged 22 commits into
eclipse:develop24_x
from
fgguidi:feature/add-strict-mode-to-recipe
Jul 26, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fgguidi
commented
Jul 22, 2024
- Changes shall be released as Cloe v0.24.1.
- Add full_package_mode() to dependencies. Conan configuration default parameter is semver_direct_mode. This means that only a package will be rebuilt when the consumer changes the package version to a newer major version. For example, if consumed nlohmann_json/3.11.2 is consumed by fable/, but the final application recipe overrides nlohmann_json/3.11.3, with the default Conan configuration, fable won't be rebuilt causing a runtime error due to ABI incompatibility. Most of the times the Conan configuration in a project is not under our control making it impossible to change this from the Conan configuration side. Hence, having the recipes with the mode that we want becomes important.
- Fix shared option value for OSI and Protobuf when consumed in esmini conan package. The OSI.shared=True and protobuf.shared=False is set on purpose to avoid runtime issues with Protobuf with either WSL or Linux (different values will produce runtime issues).
clsim
approved these changes
Jul 22, 2024
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
- Fix OSI to be shared=True and Protobuf to be shared=False. A different combination has demonstrated to be challenging/impossible to be integrated when both WSL and Linux are supported in the same project. - Set full_package_mode to dependencies: The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
The Conan configuration has as default semver_direct_mode. This means that from the final consumer recipe perspective if I override the version of a dependency package A from v1.0.0 to v1.0.1, any dependency that is also part of the dependency tree and is also consuming package A, will not be rebuilt because semver_direct_mode doesn't consider patch releases in the package_id of the consumer. We set full_package_mode to the dependencies to consider this case and the user, channel and package_id of the dependencies to define the resulting package_id of the consumer.
Align overrides in the master conanfile of the Cloe-eclipse project to the same used in master branch (avoid unnecessary differences with private packages which are produced with different versions of Cloe).
fgguidi
force-pushed
the
feature/add-strict-mode-to-recipe
branch
from
July 23, 2024 14:38
372a3c0
to
45e12a4
Compare
CzBalti
reviewed
Jul 25, 2024
fgguidi
force-pushed
the
feature/add-strict-mode-to-recipe
branch
from
July 25, 2024 13:53
7f75e52
to
7b4d1ac
Compare
CzBalti
approved these changes
Jul 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.