-
-
Notifications
You must be signed in to change notification settings - Fork 228
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
version mismatch message #324
Comments
If you install b2 it can be easily cached without version mismatches. So not sure what you are asking for. Also, the bump_version.py script is obsolete and not used any longer. |
There was a recent report of the mismatch error: boostorg/url Issue 760 You are suggesting to install b2. Not sure if that's different from building b2, which is what occurs during CI testing. After building, b2 resides in the boost folder. Installation to /bin/ or /usr/local/bin would not get cached. I think I have already fixed this by adding new logic in boost-ci. It just seemed that perhaps the comparison check should live in the bfgroup/b2 repository instead of boostorg/boost-ci . Otherwise, it's ok to close the issue. |
Unlike all the other actions in gcc, the archive action was producing platform paths instead of regular slash paths. The platform paths on Windows (\) cause problems when placed in response files as gcc/mingw interpret them as escape markers. This adds the :T qualifier to normalize the slashes. fixes #324 fixes #352 fixes boostorg/url#779
Hi,
Just ran into an issue, notice this line:
When caching in CI it could be helpful to not rebuild b2 (saving time) or only rebuild b2 when necessary.
A way to facilitate that would be to add functionality in src/engine/bump_version.py, which is already manipulating version numbers and has knowledge about versions.
Add flags to bump_version.py:
In the CI scripts, use
--compareversions
to decide if b2 should be rebuilt.It would have simple output such as "match" "nomatch", or perhaps distinctive exit codes: 0 for success, 2 for failure.
The text was updated successfully, but these errors were encountered: