From owner-freebsd-ports@FreeBSD.ORG Sun Jun 13 14:35:37 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 83C50106567F; Sun, 13 Jun 2010 14:35:37 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8C0768FC19; Sun, 13 Jun 2010 14:35:36 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA08922; Sun, 13 Jun 2010 17:30:13 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1ONoCT-000616-IH; Sun, 13 Jun 2010 17:30:13 +0300 Message-ID: <4C14EB74.9090203@icyb.net.ua> Date: Sun, 13 Jun 2010 17:30:12 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100603) MIME-Version: 1.0 To: Max Brazhnikov References: <4C128F14.9060605@FreeBSD.org> <4C1334A9.1000208@icyb.net.ua> <4C1417BB.1020906@FreeBSD.org> <201006131736.56082.makc@issp.ac.ru> In-Reply-To: <201006131736.56082.makc@issp.ac.ru> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kde-freebsd@kde.org, Doug Barton , freebsd-ports@freebsd.org, Rob Farmer 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 14:35:37 -0000 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