-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8296904: Improve handling of macos xcode toolchain #11113
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
|
👋 Welcome back clanger! A progress list of the required criteria for merging this PR into |
|
@RealCLanger The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
d9dcf5b to
dd80821
Compare
|
@RealCLanger Please do not rebase or force-push to an active PR as it invalidates existing review comments. All changes will be squashed into a single commit automatically when integrating. See OpenJDK Developers’ Guide for more information. |
erikj79
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.
I think this looks good. It's technically possible to achieve what you need using the existing --with-toolchain-path, but in the case of Xcode, that is rather cumbersome as you need to point to the internal bin directories in the Xcode installation instead of just the top level Xcode application dir.
|
@RealCLanger This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 7 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
|
Thanks for the review, I took over your suggestion. Will integrate shortly. |
magicus
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.
Looks good, thanks for fixing this!
|
Is there perhaps some documentation in doc/building.md that needs updating? I know there is a bit written about Xcode, I can imagine some pointers to this new argument would fit in there. |
Good suggestion. I made some edits in building.md. Please have a look. Also, what about building.html? Is this generated and if so, how can I regenerate it? |
|
It is generated, and you can re-generate it using To help you out, I checked out your branch and regenerated it for you. You can find it at 66ef4b7 (from https://github.com/magicus/jdk/tree/xcode-toolchain). If you are not a git wrangling pro, you can download it as a diff and apply it locally by appending |
Woho, [66ef4b7] is a super power trick 😄 I've added it and then figured out that my new enumeration isn't displayed well in html. Can you please regnerate it once more? Other than that, are my edits ok? |
|
Yes, I thought your edits were okay. I'll re-generated the html for you, and then I think you're good to go. |
|
Hm, the changes you made to the markdown file does not result in any changes in the generated html file. :( I fixed it by adding an additional empty line in the markdown file. The commit including both these fixes are here: magicus@2844de1 |
|
@magicus Thanks for fixing my enumeration. I recognized that you have regenerated all the html files with a newer pandoc and I had to resolve with master. I guess you'll need to regenerate with my current branch once more - otherwise I think I'm breaking some of the new style. |
|
@RealCLanger Finally regenerated once more: fcd20c73ed9f0a44c0614a54580c755a16387a6a |
|
Thanks @magicus for your help. /integrate |
|
Going to push as commit 470f342.
Your commit was automatically rebased without conflicts. |
|
@RealCLanger Pushed as commit 470f342. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
With this PR I'd like to make it easier to use dedicated installations of Xcode on Mac OS for OpenJDK builds without having to switch the active Xcode globally via
xcode-select.I propose adding a new configure flag
--with-xcode-paththat takes the path to an Xcode installation. If the option is set, this path is expanded to a validTOOLCHAIN_PATH.Furthermore, I fix detection of xcodebuild and correctly setting the sysroot from the toolchain by moving
AC_SUBST(TOOLCHAIN_PATH)before callingBASIC_SETUP_XCODE_SYSROOTand honoringTOOLCHAIN_PATHinBASIC_SETUP_XCODE_SYSROOTin the case when no devkit is specified. As I see it, this is a viable fix, even if not introducing--with-xcode-path.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11113/head:pull/11113$ git checkout pull/11113Update a local copy of the PR:
$ git checkout pull/11113$ git pull https://git.openjdk.org/jdk pull/11113/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11113View PR using the GUI difftool:
$ git pr show -t 11113Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11113.diff