I noticed that the default options for build mode may be a bit strange for sun compilers. The release mode uses -xO2 and the minimum size mode uses -xO3 (higher optimization level?). There seems to be an option -xspace which reads:
-xspace Do not do optimizations that increase code
Doug Henry wrote:
> I noticed that the default options for build mode may be a bit strange
> for sun compilers. The release mode uses -xO2 and the minimum size mode
> uses -xO3 (higher optimization level?). There seems to be an option
> -xspace which reads:
>
> -xspace Do not do op
Before I commit anything, I would like to verify how cmake is doing its compiler detection. Is everything simply based on name? I can have cc in my path which is gcc, or I can set my path in a way that has cc from sun studio. Is cmake capable of telling the difference? I have a problem where I
Doug Henry wrote:
> Before I commit anything, I would like to verify how cmake is doing its
> compiler detection. Is everything simply based on name? I can have cc
> in my path which is gcc, or I can set my path in a way that has cc from
> sun studio. Is cmake capable of telling the difference?
The sun compilers also have aliases: suncc, sunCC, sunf95, etc. Maybe those names should be used instead? I assume this is as easy as making a Linux-sunCC.cmake file.On 10/25/06,
Brad King <[EMAIL PROTECTED]> wrote:
Doug Henry wrote:> Before I commit anything, I would like to verify how cmake is
Since no one has used thiscompiler before I don't mind including the option until someone
complains their version doesn't have it.I would think the same options would apply to SunOS.cmake.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailm
Doug Henry wrote:
The sun compilers also have aliases: suncc, sunCC, sunf95, etc. Maybe
those names should be used instead? I assume this is as easy as
making a Linux-sunCC.cmake file.
Will that not get you in trouble with filesystems like Windows' that do not
consider the case to be disti
