chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] CMakeLists.txt CYGWIN vs. CMAKE_COMPILER_IS_GNUCC


From: felix winkelmann
Subject: Re: [Chicken-users] CMakeLists.txt CYGWIN vs. CMAKE_COMPILER_IS_GNUCC
Date: Mon, 12 Dec 2005 07:30:36 +0100

On 12/12/05, Brandon J. Van Every <address@hidden> wrote:

> Sometimes a test is given like
>
> IF(WIN32 AND NOT CYGWIN)
>
> when really what is warranted is
>
> IF(WIN32 AND NOT CMAKE_COMPILER_IS_GNUCC)
>

Applied.

>
> Or at least, this fixes a problem in library output names.  Without it,
> CMake generates liblibchicken.dll, and later stuff fails because
> libchicken.dll can't be found.  I'm not entirely sure if this is due to
> MinGW's behavior, or if CMake is generating stuff erroneously, but the
> above seems reasonable.  Similarly, I will hazard a guess that we really
> want:
>
> IF(WIN32 AND NOT CMAKE_COMPILER_IS_GNUCC)
>   ADD_DEFINITIONS(-DC_DEFAULT_TARGET_STACK_SIZE=300000)
>   ADD_DEFINITIONS(-DHAVE_LOADLIBRARY)
>   ADD_DEFINITIONS(-DHAVE_GETPROCADDRESS)
> ENDIF(WIN32 AND NOT CMAKE_COMPILER_IS_GNUCC)
>
> but I am not actually sure of this.  Is this a VC++ specific issue, or a
> non-GCC issue?  If it's VC++ specific, then VC++ should be explicitly
> tested for.  I'm not sure what the best test variable is for this.  The
> CMake documentation is decidedly mediocre as far as documenting the test
> variables.  There's a list of stuff on the CMake wiki, kinda buried amid
> other things, and doesn't seem to be complete either.
>

I think this is a non-Cygwin issue. On Mingw32 the LoadLibrary stuff
is used, since we have no dlopen wrapper (or do we?).

Attached is the current CMakeLists.txt.


cheers,
felix

Attachment: CMakeLists.txt
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]