[MacPorts] #46536: qt5-mac-devel submission: provides Qt 5.4.x
MacPorts
noreply at macports.org
Fri Mar 27 10:38:05 PDT 2015
#46536: qt5-mac-devel submission: provides Qt 5.4.x
----------------------------+--------------------------------
Reporter: rjvbertin@… | Owner: macports-tickets@…
Type: submission | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: qt5-mac-devel |
----------------------------+--------------------------------
Comment (by larryv@…):
Replying to [comment:22 rjvbertin@…]:
> This *is* about end user convenience
The select mechanism is only meant for use outside of MacPorts (e.g., as a
convenience to users who compile their own code). A user who only compiles
via MacPorts should never have to use `port select` for anything.
> The Portfile guides users on 10.6 to set up their environment in such
> a way that 1) the compiler version is not going to be baked in and 2)
> the port can actually build without having to jump through all kinds
> of hoops and loops to ensure that the installed clang is used.
So the majority of users would not be able to install `qt5-mac-devel`
without manual fiddling?
> The "requirement" takes the form of instructing the user to use port
> select if there is no clang++ in ${prefix}/bin . If you know of
> a better way to check for and "require" the presence of clang and
> clang++ (so not clang*-mp-*) in the path that are NOT the ones from
> Xcode 3 or Xcode 4.2 I'm all ears.
1. I’d frankly just require a specific version of Clang and be done with
it. Yes, I know it takes extra time and space.
1. Can Qt / qmake not be told to use another compiler?
--
Ticket URL: <https://trac.macports.org/ticket/46536#comment:23>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list