www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - dmd linux makefile

reply Trass3r <un known.com> writes:
Why is it still necessary to edit the linux makefile in order to switch  
between release and debug or 32 vs. 64 bit?
The windows one has had proper targets at least for the former issue for  
ages.
Jul 13 2011
next sibling parent reply Trass3r <un known.com> writes:
Oh and any reason why it only uses -O2 in release mode?
Jul 13 2011
parent Robert Clipsham <robert octarineparrot.com> writes:
On 13/07/2011 16:14, Trass3r wrote:

 Oh and any reason why it only uses -O2 in release mode?



-O2 is standard across most linux distributions. There's some discussion 
here: http://en.gentoo-wiki.com/wiki/CFLAGS#-O2_or_-O3.3F you can find 
more with some googling though.

-- 
Robert
http://octarineparrot.com/
Jul 13 2011
prev sibling next sibling parent Jonathan M Davis <jmdavisProg gmx.com> writes:
On Wednesday 13 July 2011 17:13:54 Trass3r wrote:

 Why is it still necessary to edit the linux makefile in order to switch
 between release and debug or 32 vs. 64 bit?
 The windows one has had proper targets at least for the former issue for
 ages.



It's not, use MODEL=32 or MODEL=64 if you want to switch between the compiler 
being compiled as 32-bit or 64-bit.

- Jonathan M Davis
Jul 13 2011
prev sibling next sibling parent Trass3r <un known.com> writes:
 It's not, use MODEL=32 or MODEL=64 if you want to switch between the  
 compiler being compiled as 32-bit or 64-bit.



Ah true, always forget that way to set variables.
Jul 13 2011
prev sibling parent Jonathan M Davis <jmdavisProg gmx.com> writes:
On Wednesday 13 July 2011 17:25:45 Trass3r wrote:

 It's not, use MODEL=32 or MODEL=64 if you want to switch between the
 compiler being compiled as 32-bit or 64-bit.



 Ah true, always forget that way to set variables.



It's the same convention that druntime and Phobos using for choosing to 
between compiling the 32-bit and 64-bit versions of themselves.

- Jonathan M Davis
Jul 13 2011