[Chandler-dev] Compiler versions

[Mike Taylor]

On Apr 20, 2006, at 2:39 PM, Reid Ellis wrote:

> As a follow-up, how hard is it to change the compiler used? Can we 
> just do this?
>
> 	make CC=gcc-3.3
>
> It would be great if that did it.

The build currently assumes that the developer knows what they are 
doing.  There already is an existing "make env" that tests the one part 
of the build that is the most specific about versions: gcj for 
PyLucene.

True, you could replace CC and CXX with gcc-3.3 or g++-3.4 or whatever 
but I feel that isn't the job of our Makefile but the job of the 
developer who has already decided what compiler they are comfortable 
with by making it their default.  Changing that assumption inside the 
build would lead to many sessions on IRC where developers ask "why do I 
get error foo" because they think we are using their gcc 3.4 but our 
default is gcc 4.1.

I would rather get the "it doesn't build on gcc 5.9" and we can respond 
"yep - check the wiki page for known compilers, patches are welcome".

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bear at osafoundation.org
http://www.osafoundation.org

bear at code-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20060420/1d29d2a0/PGP.pgp