From owner-freebsd-ports@FreeBSD.ORG Sun Jun 13 20:06:08 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 345A8106564A for ; Sun, 13 Jun 2010 20:06:08 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id B2DA28FC08 for ; Sun, 13 Jun 2010 20:06:07 +0000 (UTC) Received: (qmail 28408 invoked by uid 399); 13 Jun 2010 20:06:07 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 13 Jun 2010 20:06:07 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C153A2E.4020100@FreeBSD.org> Date: Sun, 13 Jun 2010 13:06:06 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: Andriy Gapon References: <4C128F14.9060605@FreeBSD.org> <4C1334A9.1000208@icyb.net.ua> <4C1417BB.1020906@FreeBSD.org> <201006131736.56082.makc@issp.ac.ru> <4C14EB74.9090203@icyb.net.ua> In-Reply-To: <4C14EB74.9090203@icyb.net.ua> X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kde-freebsd@kde.org, Rob Farmer , freebsd-ports@freebsd.org Subject: Re: [kde-freebsd] qt4-moc link failure X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jun 2010 20:06:08 -0000 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/