#54516 closed enhancement (invalid)
suggestion: "use_configure no" should automatically imply "variant universal {}"
| Reported by: | kencu (Ken) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | |
| Keywords: | Cc: | ||
| Port: |
Description
I believe this is what would be desired in nearly all cases.
If it is not desired or available, the universal variant could be explicitly disabled, which I would assume to be the rare case.
It is my understanding that the using PortGroup muniversal would override this setting, if it is included.
Change History (1)
comment:1 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
No, this is not desired. The portfile author is responsible for adding the necessary code to the portfile, and/or patching the build system, so that the correct
-archflags are used. Each build system is different so MacPorts shouldn't make assumptions. Just defaulting to providing an empty universal variant would result in tons of ports that claim to build universal but do not.