#50862 closed request (wontfix)
default targets for ports llvm and clang?
Reported by: | RJVB (René Bertin) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | jeremyhu (Jeremy Huddleston Sequoia), larryv (Lawrence Velázquez) | |
Port: | llvm, clang |
Description
What would be a minimal set of architectures to target (instead of "all") by the LLVM and Clang ports, one suitable for most MacPorts users and one that would that lead to a significant reduction in disk footprint and/or build time?
I'm personally not even sure that there's much interest to being able to target ARM for most users, or is common (and acceptable) practice to build iOS apps using MacPorts?
Change History (2)
comment:1 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 Changed 9 years ago by RJVB (René Bertin)
This was actually a request for information!
Does that thing about a complex matrix mean you couldn't simply do something like
-DLLVM_TARGETS_TO_BUILD=AMDGPU,ARM,CppBackend,PowerPC,X86
to get rid of the less likely targets?
I'd try, but it seems that each time you tweak a configure (cmake) setting you end up rebuilding the whole shebang instead of only the files that require rebuilding.
Note: See
TracTickets for help on using
tickets.
Not gonna do this. The matrix is complicated enough as it is. If you're worried about build time, use the binary distributions.