| 153 | | ==== Add Support for x86_64h Architecture ==== #x86_64h |
| 154 | | |
| 155 | | The system compilers have recognized, at various times, x86_64, i386, ppc, and ppc64 as valid architectures. |
| 156 | | MacPorts has support for all four. |
| 157 | | Relatively recently, system compilers started supporting the x86_64h architecture, which is a lot like x86_64, except it allows the compiler to take advantage of the Haswell microarchitecture. |
| 158 | | Adding the architecture support itself would be straightforward. |
| 159 | | However, it is not clear what, if any, performance improvement this could bring. |
| 160 | | Also, unlike other architectures in MacPorts, x86_64h and x86_64 libraries can be linked together. |
| 161 | | |
| 162 | | * Difficulty: Medium |
| | 153 | ==== Allow for Multiple Runs of Each Phase. ==== #multipleruns |
| | 154 | |
| | 155 | There are times when it is convenient to run configure/build/destroot more than once. |
| | 156 | For example: |
| | 157 | * cargo depends on the port cargo-stage1, whose only purpose is to help build cargo. Instead, one could run configure/build and use the resulting binary without installing another port. |
| | 158 | * [https://github.com/macports/macports-ports/pull/3583 fluidsynth] depends on a subproject, which has no use beyond aiding the build process. The subproject does not inherit the MacPorts settings. It would be nice to configure/build the subproject properly (from a MacPorts point of view). |
| | 159 | * 75% of the muniversal PortGroup is to get multiple runs of the configure/build/destroot phases. |
| | 160 | |
| | 161 | * Difficulty: Difficult |
