⛏️ index : buildtools.git

author Paweł Dziepak <pdziepak@quarnos.org> 2014-08-25 22:58:39.0 +02:00:00
committer Paweł Dziepak <pdziepak@quarnos.org> 2014-08-25 22:58:39.0 +02:00:00
commit
862b5480a92d92516e08cfebd62fcb1c85a18b0a [patch]
tree
7de074e11c3117929b0d36762ce87ca9e405d00e
parent
6f9a8fa02b59666640980bb622980fa13f5a2508
download
862b5480a92d92516e08cfebd62fcb1c85a18b0a.tar.gz

jam: do not set OPTIM by default

If setting OPTIM by jam basically makes it impossible for the project that
is using jam to set its own optimization level while still allowing user
to override that in command line. For example in Haiku jam files there is
line like this: "OPTIM ?= -O2", which obviously is meant to set optimization
level to O2 unless user overwrites it. Unfortunately, because Jam have already
set OPTIM to -O this line never had an intended effect.

After this Jam no longer thinks it knows best what is good for projects
that are using it and Haiku is by default compiled with -O2.

Signed-off-by: Paweł Dziepak <pdziepak@quarnos.org>

Diff

 jam/Jambase | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/jam/Jambase b/jam/Jambase
index 148e36f..72c1cc6 100644
--- a/jam/Jambase
+++ b/jam/Jambase
@@ -540,7 +540,7 @@
	LEX		?= lex ;
	LINKFLAGS	?= $(CCFLAGS) ;
	LINKLIBS	?= ;
	OPTIM		?= -O ;
	OPTIM		?= ;
	RANLIB		?= ranlib ;
	YACC		?= yacc ;
	YACCGEN		?= .c ;