qt4-moc link failure
in [Ports]
|
Prev: deskutils/alexandria - why does it create a world readable and writable directory?
Next: FreeBSD Port: php5-mysqli-5.3.2_1
From: Andriy Gapon on 13 Jun 2010 10:30 on 13/06/2010 16:36 Max Brazhnikov said the following: > qmake is designed to use special mkspecs for compilers. The only solution now > is to create qmake mkspecs files for each compiler. Then switching between > different compilers can be done via QMAKESPEC environment. Right. OTOH, CC and CXX variables somehow get honored without altering any spec file. So, the question remains if it's possible to derive LINK* values from those in the same fashion as well. -- Andriy Gapon _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Doug Barton on 13 Jun 2010 16:06 On 06/13/10 07:30, Andriy Gapon wrote: > on 13/06/2010 16:36 Max Brazhnikov said the following: >> qmake is designed to use special mkspecs for compilers. The only >> solution now is to create qmake mkspecs files for each compiler. >> Then switching between different compilers can be done via >> QMAKESPEC environment. > > Right. OTOH, CC and CXX variables somehow get honored without > altering any spec file. So, the question remains if it's possible to > derive LINK* values from those in the same fashion as well. Right, we really need to make this transparent to the user. The common requirement in ports is that they respect CC. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Alberto Villa on 16 Jun 2010 05:02 On Sunday 13 June 2010 22:06:06 Doug Barton wrote: > On 06/13/10 07:30, Andriy Gapon wrote: > > on 13/06/2010 16:36 Max Brazhnikov said the following: > >> qmake is designed to use special mkspecs for compilers. The only > >> solution now is to create qmake mkspecs files for each compiler. > >> Then switching between different compilers can be done via > >> QMAKESPEC environment. > > > > Right. OTOH, CC and CXX variables somehow get honored without > > altering any spec file. So, the question remains if it's possible to > > derive LINK* values from those in the same fashion as well. > > Right, we really need to make this transparent to the user. The common > requirement in ports is that they respect CC. ok, i think i'll fix this, also thanks to a contribution from clang folks unfortunately, it really means adding more qmake.conf's, but after all there aren't so many compilers and, of course, it will respect CC -- Alberto Villa, FreeBSD committer <avilla(a)FreeBSD.org> http://people.FreeBSD.org/~avilla If all the world's economists were laid end to end, we wouldn't reach a conclusion. -- William Baumol
From: Alberto Villa on 16 Jun 2010 09:22
On Wednesday 16 June 2010 11:02:38 Alberto Villa wrote: > ok, i think i'll fix this, also thanks to a contribution from clang folks > unfortunately, it really means adding more qmake.conf's, but after all > there aren't so many compilers > > and, of course, it will respect CC here's (attached) what i've made so far: please , have a look i'm not able to test it at the moment because i am at the university (which means that i could have written all sort of stupid things)... will do some tests later. meanwhile, if you have suggestions or complaints, send them (pay attention: the patch was made against qt 4.7 in area 51... after the tests prove successful, i'll backport it to qt 4.6 (it requires just a couple of modifications)) i've added support for all the c++ compilers i've found in the ports: gcc(34|42|43|44|45|46), icc, llvm and clang. pcc is not a c++ compiler as far as i know. if something (even if exotic) is still missing, let me know. chances are you won't be able to build qt with them (in qt 4.7 there is at least one test which requires gcc or icc... i've already sent my complaints to qt developers, and i'll soon patch it), but at least you'll be able to try to make things even more tasty, bsd.qt.mk is able to understand if `c++` is actually g++ or clang++. yes, clang people, i'm talking to you :) -- Alberto Villa, FreeBSD committer <avilla(a)FreeBSD.org> http://people.FreeBSD.org/~avilla Tact in audacity is knowing how far you can go without going too far. -- Jean Cocteau |