-
Notifications
You must be signed in to change notification settings - Fork 38.7k
doc: improve note on choosing posix mingw32 #22088
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
Conversation
|
Huh... Perhaps our |
6e745eb to
dafab2b
Compare
|
updated from 6e745eb -> dafab2b (pr22088.01 -> pr22088.02, diff) Changes: |
hebasto
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK dafab2b
Also, it seems reasonable to s/"both the 32 and 64 bit Mingw-w64 packages install"/"Mingw-w64 package installs"/ in the footnote, don't it?
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
|
Clearly an improvement, agree that it was confusing |
dafab2b doc: improve note on choosing posix mingw32 (Jarol Rodriguez) Pull request description: The current [windows build doc](https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md) can lead someone to believe that the step where you must choose the posix mingw32 g++ compiler option is only for `Ubuntu 18.04`. It is only until you (or just me) go through the cross-compile process and realize that it's not building because you didn't set this option on > `Ubuntu 18.04`. Then you come back and read the footnotes and see: `Starting from Ubuntu Xenial 16.04...`. This PR improves this portion of the doc by editing the text around this stage to state "this is now the next step". We could add a note saying `Ubuntu 18.04 and up`, but this is redundant as it's unlikely someone will be using < Ubuntu 18.04 since it's not officially supported by our build system. While here, some minor fixups and add some more guidance to completing this step. **Master:** [render](https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md#building-for-64-bit-windows) **PR:** [render](https://github.com/bitcoin/bitcoin/blob/dafab2b1b37d1966610b2189e71c52e3af38dfaa/doc/build-windows.md#building-for-64-bit-windows) ACKs for top commit: laanwj: ACK dafab2b hebasto: ACK dafab2b Tree-SHA512: d8d50fa13c34be753700843183a1a4addad6447c813bfc039865ba11d5fa03c25206ed6f3782331df4c6a44448e3fec4138ae911b995b5cacc5b756bb5d74bb4
The current windows build doc can lead someone to believe that the step where you must choose the posix mingw32 g++ compiler option is only for
Ubuntu 18.04. It is only until you (or just me) go through the cross-compile process and realize that it's not building because you didn't set this option on >Ubuntu 18.04. Then you come back and read the footnotes and see:Starting from Ubuntu Xenial 16.04....This PR improves this portion of the doc by editing the text around this stage to state "this is now the next step". We could add a note saying
Ubuntu 18.04 and up, but this is redundant as it's unlikely someone will be using < Ubuntu 18.04 since it's not officially supported by our build system. While here, some minor fixups and add some more guidance to completing this step.Master: render
PR: render