Opened 3 days ago
Last modified 2 days ago
#70320 new enhancement
llvm should build with option LLVM_CREATE_XCODE_TOOLCHAIN
| Reported by: | crowell (Jeffrey Crowell) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.9.3 |
| Keywords: | Cc: | jeremyhu (Jeremy Huddleston Sequoia), cjones051073 (Chris Jones), larryv (Lawrence Velázquez) | |
| Port: | llvm |
Description
when building LLVM, it's helpful to include the LLVM_CREATE_XCODE_TOOLCHAIN to create an .xctoolchain for use in xcode.
This should probably be the default, or at least, a variant (probably the default though, as it's not really any overhead).
Change History (3)
comment:1 Changed 2 days ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | jeremyhu cjones051073 larryv added |
|---|
comment:2 Changed 2 days ago by ryandesign (Ryan Carsten Schmidt)
Also be very sure that you are only increasing the revision of the subports that would actually change. For example, if it is the llvm-18 port whose contents would change, increase the revision only of the llvm-18 subport, not of the mlir-18, clang-18, lldb-18, and flang-18 subports. Or, if this .xctoolchain file ends up getting installed by the clang-18 subport, then increase the revision of only that subport, not the others.
comment:3 Changed 2 days ago by cjones051073 (Chris Jones)
the latest LLVM port (18) sees relatively frequent revision bumps at the moment, so I suggest adding this the next time that happens.
However it is a considerable overhead to rebuild any version of llvm on our build servers. Building llvm-18, for example, took over 5 hours on some build machines that are particularly overcommitted. Therefore if this is implemented please combine it with a version update of an llvm version that is still receiving updates, and for older versions that aren't receiving updates please make the change in only one version of llvm at a time, at a time when the build machines are not already backlogged with other builds.