Qmake does not respect compiler choice

[Michael Dickens]

Hi Nicolas - qmake by itself will not "do the right thing", as you note,
for pretty much any 'port' setting (CC, CXX, *FLAGS).
If you use the qmake 1.0 PortGroup, then qmake should "do the right
thing". If you're using this PG & qmake is still not doing the right
thing, then the issue is likely the 'Makefile' or 'configure' script
interface.
Hope this helps! - MLD

On Sat, Jul 1, 2017, at 08:07 AM, Nicolas Pavillon wrote:
> While trying to solve an issue where one of my ports does not respect
> the compiler choice (ticket #54372, thanks Ryan for pointing that
> out), I realised that qmake seems to not be respecting the choice of
> compiler in any case.> On Mac, qmake uses by default the 'macx-g++’ configuration, which sets
> everything to use clang, regardless of the choice of compiler,
> including flags such as Xarch which are not compatible with gcc. I
> could reproduce that problem with both mine and other ports.> I noticed that qmake also has config files for instance for gcc 4.2
> (macx-g++42) or llvm (macx-llvm), but I did not yet confirm if those
> could be used.> 
> I assume that the PortGroup would have to be modified to properly
> choose the config file depending on the chosen compiler (which I could
> try to implement), but I wanted to check first if someone already
> solved that issue, or if I am missing something obvious.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20170701/1f2fc774/attachment.html>