Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 08 Nov 1999 08:50:50 -0500
From:      "Pedro Fernando Giffuni" <pfgiffun@bachue.usc.unal.edu.co>
To:        Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG>
Cc:        "R. Imura" <imura@cs.titech.ac.jp>, andrews@technologist.com, ports@FreeBSD.ORG
Subject:   Re: Possible change in the Qt port.
Message-ID:  <3826D53A.D584DCED@bachue.usc.unal.edu.co>
References:  <38209354.5A0E1416@bachue.usc.unal.edu.co> <3.0.6.32.19991103230433.008afc90@mail.psn.net> <19991106044140H.imura@cs.titech.ac.jp> <vqcaeoqpseq.fsf@silvia.hip.berkeley.edu> <3825A24F.A98124BC@bachue.usc.unal.edu.co> <vqc7ljtmjv0.fsf@silvia.hip.berkeley.edu>

next in thread | previous in thread | raw e-mail | index | archive | help


Satoshi - Ports Wraith - Asami wrote:
> 
>  * From: "Pedro Fernando Giffuni" <pfgiffun@bachue.usc.unal.edu.co>
> 
>  * There is a binary: moc, AFAIK it's onlt used during the building process
>  * in some ports and they expect to find it in $(QTDIR)/bin.
> 
> Is it a problem to tell those ports that QTDIR=${PREFIX} ?
> 
You hit the point: I don't care where it is as long as we have a QTDIR.
It collides with qt1, so currently we are patching everything to find
$(PREFIX)/lib/libqt2, $(PREFIX)/include/qt2, and $(PREFIX)/bin/moc2.

>  * Not really; we already use this approach when the port wants to create
>  * it's own directory. The example that comes to mind is Scilab. Lesstif is
>  * a case where NOT applying this is clearly violating hier().
> 
> Just because the rule isn't enforced in all cases doesn't make the
> rule invalid. :)
> 
In Scilab's case you suggested this solution as the correct one :).

cheers,

    Pedro.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3826D53A.D584DCED>