[MacPorts] #46536: qt5-mac-devel submission: provides Qt 5.4.x
MacPorts
noreply at macports.org
Fri Mar 27 10:59:43 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 rjvbertin@…):
Replying to [comment:23 larryv@…]:
> > 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.
>A user who only compiles via MacPorts should never have to use port
select for anything.
Oh ... so I could just use `system port select .....` from the Portfile if
it detects that the call hadn't been made? O:-)
>
> So the majority of users would not be able to install `qt5-mac-devel`
without manual fiddling?
Because the majority of users are on 10.6? I don't see how else you
reached that conclusion?
> 1. Can Qt / qmake not be told to use another compiler?
With difficulty, that's what has been the greatest hurdle. On 10.6 . On
later OS X versions xcrun is "clever" enough to realise it shouldn't try
to find a full path in the Xcode toolchain, but the 10.6 xcrun errors out
when it is handed a full path. So yes, you can tell it to do that, but
either it will result in an error or else you'll still get the Xcode
version.
--
Ticket URL: <https://trac.macports.org/ticket/46536#comment:24>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list