they happen in order...and are the void the default values...here is an example...

LDFLAGS default value is -L%p/lib but in some cases the Makefile with put LDFLAGS ahead of LIBS well in most cases this is true, but for upgrading a library you want -L%p/lib to be last on the link line or it could link the old version of a lib from %p/lib and not the new one being built. So in this case you want -L%p/lib in LIBS so it's at the end... To get this behavior you first need to take it out of LDFLAGS yet you still might want say -ldl in LDFLAGS so

NoSetLDFLAGS: true
SetLDFLAGS: -ldl
SetLIBS: -L%p/lib

---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.

On 9-Jan-04, at 5:29 PM, Koen van der Drift wrote:

Hi,

I am not sure if I understand the use of the NoSetENVFLAGS field. I see it in several packages used (with a value 'true'), while also the SetENVFLAGS field is used. Aren't these two contradicting each other?


thanks,


- Koen.



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Attachment: PGP.sig
Description: This is a digitally signed message part



Reply via email to