Details
-
Enhancement
-
Resolution: Fixed
-
P4
-
11, 17, 19, 20
-
b25
-
os_x
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8297888 | 19.0.2 | Christoph Langer | P4 | Closed | Won't Fix | |
JDK-8298490 | 17.0.7 | Christoph Langer | P4 | Resolved | Fixed | b01 |
JDK-8299013 | 11.0.19 | Christoph Langer | P4 | Resolved | Fixed | b01 |
Description
In the latter case, however, the required value for the path is neither self-explaining nor well documented. It turns out that the toolchain path needs 2 components, <xcode_path>/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin and <xcode_path>/Contents/Developer/usr/bin to become effective.
To make it more convenient to pick a certain xcode for a certain build, I suggest adding a configure option --with-xcode-path that simply needs the path to the xcode installations, e.g. /Applications/Xcode.app.
Attachments
Issue Links
- backported by
-
JDK-8298490 Improve handling of macos xcode toolchain
- Resolved
-
JDK-8299013 Improve handling of macos xcode toolchain
- Resolved
-
JDK-8297888 Improve handling of macos xcode toolchain
- Closed
- links to
-
Commit openjdk/jdk11u-dev/8a4915e5
-
Commit openjdk/jdk17u-dev/57e6d92a
-
Commit openjdk/jdk19u/7275da49
-
Commit openjdk/jdk/470f3424
-
Review openjdk/jdk11u-dev/1584
-
Review openjdk/jdk17u-dev/931
-
Review openjdk/jdk19u/92
-
Review openjdk/jdk/11113