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

[boost] fix emscripten build #29481

Merged
merged 9 commits into from
Feb 8, 2023
Merged

Conversation

Pospelove
Copy link
Contributor

fixes #27641
fixes #28423
fixes #29470

this PR adds support for non-header-only Boost libraries build under Emscripten

tested with:

  • vcpkg install boost-exception[core]:wasm32-emscripten -- issue discovered here
  • vcpkg install boost-outcome[core]:wasm32-emscripten -- depends on boost-exception
  • vcpkg install boost-regex[core]:wasm32-emscripten -- there is an issue for this failure

proven .a files in /lib and /debug/lib and headers in /include

while my changes seem to work, I'm looking forward to your review. I'm not familiar with b2 so I probably did in CMake too much

see also
https://github.com/boostorg/build/blob/develop/src/tools/emscripten.jam
https://www.boost.org/doc/libs/1_81_0/tools/build/doc/html/index.html#bbv2.extending.toolset_modules

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

PRs must add only one version and must not modify any published versions

When making any changes to a library, the version or port-version in vcpkg.json or CONTROL must be modified.

error: checked-in files for boost-modular-build-helper have changed but the version was not updated
version: 1.81.0#1
old SHA: 6e28e9a445dc3442e89761e500fbb8bb5e175c00
new SHA: 901e950fd90fca536c98289e5f2f9beac7d959de
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***

@Pospelove Pospelove changed the title [boost] fix wasm32-emscripten build [boost] fix emscripten build Feb 6, 2023
@JonLiu1993 JonLiu1993 added the category:community-triplet A PR or issue related to community triplets not officially validated by the vcpkg team. label Feb 7, 2023
@JonLiu1993 JonLiu1993 added the info:reviewed Pull Request changes follow basic guidelines label Feb 7, 2023
@JavierMatosD JavierMatosD merged commit 1c48ec7 into microsoft:master Feb 8, 2023
@Pospelove Pospelove deleted the patch-1 branch February 8, 2023 12:27
@tobbi
Copy link
Contributor

tobbi commented Feb 8, 2023

@Pospelove Maybe you could take a look at this new emscripten boost build failure that just popped up? #29529

@Pospelove
Copy link
Contributor Author

@tobbi Yeah, I think so, I'll take a look.
Did my PR break boost-filesystem:wasm32-emscripten or just changed error?

@tobbi
Copy link
Contributor

tobbi commented Feb 8, 2023

@tobbi Yeah, I think so, I'll take a look. Did my PR break boost-filesystem:wasm32-emscripten or just changed error?
I actually don't know. I think we never got that far with installing the dependencies, so I can't tell.

@Pospelove
Copy link
Contributor Author

@tobbi ok I see, thanks

BillyONeal added a commit to BillyONeal/vcpkg that referenced this pull request Feb 18, 2023
…rts.ps1.

microsoft#29540 and microsoft#29481 forgot to rerun generate-ports.ps1.

Note that the default port-version was bumped because most everything depends on boost-build that change touched.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:community-triplet A PR or issue related to community triplets not officially validated by the vcpkg team. info:reviewed Pull Request changes follow basic guidelines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[boost-exception] build failure [boost-exception] Build error [boost-regex] build failure with emscripten
4 participants