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

Cloe recipes: Fix ABI compatibility issues #251

Merged

Conversation

fgguidi
Copy link

@fgguidi 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).

@fgguidi fgguidi requested review from cassava and tobifalk as code owners July 22, 2024 14:52
@clsim clsim self-requested a review July 22, 2024 14:54
Franco Guidi added 21 commits July 23, 2024 15:48
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 fgguidi force-pushed the feature/add-strict-mode-to-recipe branch from 372a3c0 to 45e12a4 Compare July 23, 2024 14:38
@fgguidi fgguidi requested a review from scpa1055 as a code owner July 24, 2024 14:34
@fgguidi fgguidi force-pushed the feature/add-strict-mode-to-recipe branch from 7f75e52 to 7b4d1ac Compare July 25, 2024 13:53
@scpa1055 scpa1055 merged commit 3008b85 into eclipse:develop24_x Jul 26, 2024
8 checks passed
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