[cmake-developers] New platform file for Cray Compute Node Linux

[Chuck Atkins]

Yep, I had a few other tweaks as well but I didn't want to bombard the list
with a series of tweaks.  I just got access to a newer XC30 and things
start to break on there since the new environment modules use different
variable names, things like that.  It needs a little more before it will
work universally on a generic Cray but I think it's close.  I'll wait until
I get it working on the XC30 as well before I push it.

- Chuck


On Sun, Aug 17, 2014 at 4:57 AM, Rolf Eike Beer <eike at sf-mail.de> wrote:

> Chuck Atkins wrote:
> > Updated to allow for static and shared libs (yes, you can use shared libs
> > on a cray).  The expectation is that your toolchain file will have the
> > appropriate logic to deal with this.  Something like:
> >
> > set(CMAKE_SYSTEM_NAME ComputeNodeLinux)
> > ...
> > if(DEFINED ENV{CRAYPE_LINK_TYPE} AND
> >    "$ENV{CRAYPE_LINK_TYPE}" EQUALS "dynamic")
> >   set(_CRAY_LINK_OPTS "-dynamic")
>
> This looks wrong. There is no EQUALS operator in if, and EQUAL is for
> comparing numbers. You probably just meant something like
>
> if(ENV{CRAYPE_LINK_TYPE} STREQUAL "dynamic")
>
> Eike
> --
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20140818/0f044a89/attachment-0002.html>