[CMake] cmake 2.8.1 compile problems on Solaris?
Attila Nagy
nagy.attila at yahoo.com
Thu Jun 3 14:45:01 EDT 2010
No, not yet.
For Slicer we need 2.8, or 2.8.1, so this is why I'm at 2.8.1, and have not tried more recent versions.
According to the web-git page
http://cmake.org/gitweb?p=cmake.git;a=history;f=Utilities/cmlibarchive/libarchive/archive_write_disk.c;h=8221a9f2e9a9c34f2ad34aaf9cba8021ae3ea04a;hb=next
that specific file has not been touched for a while - nevertheless I'll check that version too.
Thanks,
Attila
--- On Thu, 6/3/10, Bill Hoffman <bill.hoffman at kitware.com> wrote:
> From: Bill Hoffman <bill.hoffman at kitware.com>
> Subject: Re: [CMake] cmake 2.8.1 compile problems on Solaris?
> To: cmake at cmake.org
> Date: Thursday, June 3, 2010, 8:19 PM
> On 6/3/2010 11:44 AM, Attila Nagy
> wrote:
> > Hi,
> >
> > it would be easy with a conditional define, something
> like
> >
> > // If we're on Solaris...
> > # if defined(sun) || defined(__sun)
> > // ...and we use Studio C compiler
> > # if defined __SUNPRO_C
> > # define BSD_COMP
> > # endif
> > // Solaris
> > # endif
> > // Studio C compiler
> >
> > (or of course<sys/ioccom.h> can be
> included, but _I_ think the former is more elegant)
> >
> > But would there a way that BSD_COMP can be defined in
> some CMakeLists.txt or similar file?
> > I mean that way the source itself shouldn't be
> touched. I don't know cmake that well.
> >
>
> Have you tried git next yet? We did some work with
> someone to build on
> solaris.
>
> -Bill
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>
More information about the CMake
mailing list