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.<br><br><div><span class="gmail_quote">On 10/25/06, <b class="gmail_sendername">
Brad King</b> <<a href="mailto:brad.king@kitware.com">brad.king@kitware.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Doug Henry wrote:<br>> Before I commit anything, I would like to verify how cmake is doing its<br>> compiler detection. Is everything simply based on name? I can have cc<br>> in my path which is gcc, or I can set my path in a way that has cc from
<br>> sun studio. Is cmake capable of telling the difference? I have a<br>> problem where I could have f77 from either set of compilers but each<br>> requires different compiler options. Can this be done using cmake?
<br><br>Alot of it is currently based on name, but you can actually run the<br>compiler using EXEC_PROGRAM or EXECUTE_PROCESS to determine it's real<br>identity. Eventually we may compile/run a small source file that uses
<br>the preprocessor to identify the compiler but that is not yet done.<br><br>-Brad<br></blockquote></div><br>