Javier Gonzalez wrote:
Good Fortran support is relatively new to CMake. In fact, CVS CMake
is really the only version that handles all the Fortran depend stuff
reliably. CMake relies on the compiler to provide the correct run
time libraries. If you build with a C++ compiler, it will
automat
Hi
I have create and script for search google/ctemplate package
source is here
http://ydra-cmake.googlecode.com/svn/trunk/cmake/ydra/FindGoogleCtemplate.cmake
any comments for improve it are well come.
There are also other cmake scripts for use antlr c++ in the same repository.
http://ydra-cmake
Bug 0006286 submitted.. finally..
On Jan 14, 2008 12:33 PM, Mike Jackson <[EMAIL PROTECTED]> wrote:
>
> On Jan 14, 2008, at 12:20 PM, Bill Hoffman wrote:
>
> > Mike Jackson wrote:
> >> I just built the latest CVS head of CMake and tried running on OS
> >> X (10.4.11 Intel) and noticed a few thing
Bill Hoffman wrote:
> Honest Guvnor wrote:
>> On Jan 29, 2008 3:33 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote:
>>
>>> Well, you are sort of stuck...
>>
>> That is surprising. The combination of C++ (GUI) and Fortran
>> (science/engineering number crunching) is going to be a common one and
>> I had
On Jan 29, 2008 10:42 AM, Yogesh Marwaha <[EMAIL PROTECTED]> wrote:
> Ok, got it.
>
> Here is new CMakeLists.txt
>
> project (eSpy)
> cmake_minimum_required (VERSION 2.4.0)
> if(NOT CMAKE_BUILD_TYPE)
> set (CMAKE_BUILD_TYPE Release)
> endif(NOT CMAKE_BUILD_TYPE)
> if(NO
Honest Guvnor wrote:
On Jan 29, 2008 3:33 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote:
Well, you are sort of stuck...
That is surprising. The combination of C++ (GUI) and Fortran
(science/engineering number crunching) is going to be a common one and
I had assumed I was doing something wrong.
Hi,
I am dealing with a similar situation, and use the attached file.
Tested with gnu fortran and absoft, but i believe adding other
combinations to the
KNOWN_FORTRAN_LIBRARIES
variable should help.
any feedback or suggestions welcomed
Andrew
FortranLibraries.cmake
Description: Bi
On Jan 29, 2008 4:06 PM, Maik Beckmann <[EMAIL PROTECTED]> wrote:
> Am Dienstag 29 Januar 2008 15:15:48 schrieb Honest Guvnor:
> > I have tried adding a dummy fortran file to the list of C++ files to
> > force it know about Fortran and get prompted to declare the
> > linker_language property.
>
> D
On Jan 29, 2008 3:33 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote:
> Well, you are sort of stuck...
That is surprising. The combination of C++ (GUI) and Fortran
(science/engineering number crunching) is going to be a common one and
I had assumed I was doing something wrong.
Is there no cmake vari
Please excuse the brainfart. I assume the true answer is that CMake doesn't
set any preprocessor variables on its own. CMake just sets certain CMake
variables, and if you want them reflected as preprocessor variables, you write
the CMake calls to achieve that.
- C
> -Original Message---
Awesome! Thanks.
I wonder why it's not in CMake's online docs.
> -Original Message-
> From: Mike Jackson [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 29, 2008 11:29 AM
> To: Convey Christian J NPRI
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Does CMake set preprocessor variables
I would take a look at:
http://predef.sourceforge.net/precomp.html
and use those. If _I_ were to do it I would do the following:
If I were targeting specifically windows (MSVC, MINGW, CygWin)
#if __WIN32
#else
#endif
OR if I was targeting Visual studio then
#if _MSC_VER
#else
#endif
Sorry - shift key stuck.
WIN#@ should have read, WIN32
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> On Behalf Of Convey Christian J NPRI
> Sent: Tuesday, January 29, 2008 11:15 AM
> To: cmake@cmake.org
> Subject: [CMake] Does CMake set preprocessor varia
Does CMake automatically set preprocessor variables that indicate the operating
system?
I'd like to write some code similar to this:
#ifdef UNIX
...
#elif WIN#@
...
#endif
But if CMake is already setting some of those preprocessor variables for me,
it's not clear what variables it's sett
Ok, got it.
Here is new CMakeLists.txt
project (eSpy)
cmake_minimum_required (VERSION 2.4.0)
if(NOT CMAKE_BUILD_TYPE)
set (CMAKE_BUILD_TYPE Release)
endif(NOT CMAKE_BUILD_TYPE)
if(NOT CMAKE_INSTALL_PREFIX)
set (CMAKE_INSTALL_PREFIX "/usr/local")
endif(NOT CMAKE_INS
Hello,
I posted a question about the use of EXCLUDE_FROM_ALL directive in
ADD_SUBDIRECTORY a couple of days ago, but got no response ; so I thought I
give it a try again. I searched everywhere including the bug reports but i
could not find anything on this issue. The closest report I came acros
On Jan 29, 2008 8:18 AM, Ali - <[EMAIL PROTECTED]> wrote:
>
> (1) Somewhere in this file the include line for the existing make file is
> added.
>
> (2) Somewhere in the compile command all the flags from the existing make
> file, stored in one single variable $(EXISTING_MAKE_FLAGS), is added.
>
>
Am Dienstag 29 Januar 2008 15:15:48 schrieb Honest Guvnor:
> I have tried adding a dummy fortran file to the list of C++ files to
> force it know about Fortran and get prompted to declare the
> linker_language property.
Did you altered your project(..) statement to
project(foo CXX Fortran)
or ad
Honest Guvnor wrote:
I am building a program with a C++ main (WxWidgets) and linking with C
and Fortran libraries. My problem is that on each platform I am
currently having to find the basic Fortran library (e.g. libg2c for
g77) and include it explicitly in the target_link_libraries list.
I have
I am building a program with a C++ main (WxWidgets) and linking with C
and Fortran libraries. My problem is that on each platform I am
currently having to find the basic Fortran library (e.g. libg2c for
g77) and include it explicitly in the target_link_libraries list.
I have tried adding a dummy f
Hi,
There is this existing big project which is based on autotools and I am trying
to simply include the existing make files into my cmake project (don't even
mention the possibility of converting the whole thing to cmake, this is the
project owners problem). I was able to sucessfully implement
Check the modules for something like "selfexecutablepackers".
Just add a POST_BUILD step & everythin would be fine ;-)
On 29/01/2008, Filipe Sousa <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I'm trying to use upx to compress the final executable but I have a
> few problems.
> What I did was adding a cu
Hi!
I'm trying to use upx to compress the final executable but I have a
few problems.
What I did was adding a custom command:
add_executable(gal WIN32 ${sources})
get_property(galpath TARGET gal PROPERTY LOCATION)
add_custom_command(
TARGET gal POST_BUILD
COMMAND upx ${galpath})
Th
> Von: "Surya Kiran Gullapalli"
> Hi all,
> I'm trying to install a shared library using INSTALL Method on win32
> platform. (Visual Studio 2005)
>
> But what i found was only the dll is getting installed. the import
> library .lib is not getting installed.
>
> I've specified the RUNTIME and LIBR
Hi all,
I'm trying to install a shared library using INSTALL Method on win32
platform. (Visual Studio 2005)
But what i found was only the dll is getting installed. the import
library .lib is not getting installed.
I've specified the RUNTIME and LIBRARY options for Install method.
I've browsed thr
Hi all,
There is a CMake Chinese Community under the construction at
http://www.cmake.cn . This site aims at providing the CMake Chinese
documentations and also an open platform to share the experiences of using
CMake ,solve the problems and offer the CMake technicalsupports for Chinese
speaking u
Hi Michael,
simply add the .def file to your target's sources.
Best regards, Gerhard
-Ursprüngliche Nachricht-
Gesendet: Dienstag, 29. Januar 2008 11:30
An: cmake@cmake.org
Betreff: [CMake] The /DEF-option of MSVC-link
How can I place the /DEF:"Debug\File.def" option to the
MSVC linker
How can I place the /DEF:"Debug\File.def" option to the
MSVC linker ?
I thought
SET_TARGET_PROPERTIES(mYtarget PROPERTIES
LINK_FLAGS "/DEF:\"Debug\\File.def\"")
would be a good idea, but that doesn't work.
Michael Renner
___
CM
On Jan 29, 2008 12:26 AM, Yogesh Marwaha <[EMAIL PROTECTED]> wrote:
> All I want is the ability to change default values for CMAKE_BUILD_TYPE and
> CMAKE_INSTALL_PREFIX, i.e. if the user configures with only cmake ..
>
> If the user want it, these options should be changeable by supplying
> -DCMAKE
On Jan 28, 2008 9:31 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote:
> So,
> a small focused patch for documentation will be addressed much quicker
> than a large complicated patch.
I will also say, documents have been getting fixed lately without
patches, if the new text is trivial. Generally I just
30 matches
Mail list logo