On 2007-08-06 14:52-0700 Marie-Christine Vallet wrote:
Hi,
I wanted to use LD an F flags for my compilation, but I cannot seem to find
how to set them up
Thanks,
Marie
To specify the fortran compiler and fortran compiler flags use the
environment variable FC _before_ cmake (starting with emp
Hi,
I wanted to use LD an F flags for my compilation, but I cannot seem to
find how to set them up
Thanks,
Marie
---
In configure.ac it looked like that, I managed to get the libraries ok,
but
Things like FIND_LIBRARY create a cache entry for the result. Is there a way to
remove the variable from the cache or make it never get in there in the first place?
James
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cma
Bill Hoffman wrote:
David Blado wrote:
It is a cmake bug. CMake is doing a string compare somewhere. And
when cmake gets
the current working directory, windows gives back the case that was
given to cd.
Do you think it would be possible to send me the script that causes the
problem?
-B
On 2007-08-06 15:27-0400 Alexander Neundorf wrote:
On Friday 03 August 2007 13:27, Alan W. Irwin wrote:
On Linux (at least for both my Debian and Ubuntu platforms), FindX11.cmake
sets X11_INCLUDE_DIR to /usr/include;/usr/include;/usr/include.
This triplication is an annoyance at least in the c
David Blado wrote:
Hi Bill,
Yes, this worked fine in 2.4.6.
I would think that the case sensitivity would only cause a problem on
Unix since Windows is case insensitive.
I'm not sure where to specify or why cmake is using 'C' for one of the
paths and 'c' for the other.
I am setting: SET(CTEST
On Monday 06 August 2007 14:46, David Blado wrote:
> Hi All,
>
>
>
> After upgrading to cmake/ctest 2.4.7, I started experiencing the
> following problems when running my automated builds using ctest:
>
>
>
> c:/builds/dds4.2.3/dds/CMakeLists.txt:6:
>
> ADD_SUBDIRECTORY not given a binary directory
I found the problem. The output from the custom command has to
explicitly specify the destination path of the output file.
OUTPUT ${PROJECT_BINARY_DIR}/output.cc
I was already specifying the full path for the input to the library.
Regards,
Juan
Juan Sanchez wrote:
> I created a custom comman
I created a custom command to generate a cpp file.
I then use this cpp file to create a library as a separate add_library
command.
Whenever I type make, this cpp file is regenerated, and the library is
recreated. Compiling this file is super expensive. Nothing has changed
between invocations of
Hi Bill,
Yes, this worked fine in 2.4.6.
I would think that the case sensitivity would only cause a problem on
Unix since Windows is case insensitive.
I'm not sure where to specify or why cmake is using 'C' for one of the
paths and 'c' for the other.
I am setting: SET(CTEST_START_WITH_EMPTY_BIN
On Friday 03 August 2007 13:27, Alan W. Irwin wrote:
> On Linux (at least for both my Debian and Ubuntu platforms), FindX11.cmake
> sets X11_INCLUDE_DIR to /usr/include;/usr/include;/usr/include.
>
> This triplication is an annoyance at least in the case where you are using
> SET_SOURCE_FILES_PROPE
The file names in the CMake output differ : one begins with an uppercase "C"
the other a lowercase "c" -- maybe the reason behind that difference is the
reason behind this "mis-reported error..." ?
HTH,
David
On 8/6/07, David Blado <[EMAIL PROTECTED]> wrote:
>
> Hi All,
>
>
>
> After upgrading
Bill Hoffman wrote:
So, this worked with 2.4.6?
The problem is the C: vs c:, note the case
Also, did you re-run cmake on a clean binary tree for the test?
-Bill
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cma
David Blado wrote:
Hi All,
After upgrading to cmake/ctest 2.4.7, I started experiencing the
following problems when running my automated builds using ctest:
c:/builds/dds4.2.3/dds/CMakeLists.txt:6:
ADD_SUBDIRECTORY not given a binary directory but the given source
directory "C:/builds/dds4
Hi All,
After upgrading to cmake/ctest 2.4.7, I started experiencing the
following problems when running my automated builds using ctest:
c:/builds/dds4.2.3/dds/CMakeLists.txt:6:
ADD_SUBDIRECTORY not given a binary directory but the given source
directory "C:/builds/dds4.2.3/dds/Accounting
Miguel A. Figueroa-Villanueva wrote:
On 8/6/07, Mathieu Malaterre wrote:
Hi Miguel,
I do that all the time. You only need to modify PATH to work on
cyginw (ie. replace the ; with :). You should NOT change LIB or
INCLUDE, those variable are read by cl/link thus should contains ; as
separato
On Monday 06 August 2007 14:09, Miguel A. Figueroa-Villanueva wrote:
...
> BTW, the mingw cmake does generate "NMake Makefiles" the cygwin cmake
> doesn't. I successfully generated the "NMake Makefiles" with the mingw
> cmake and built with nmake from the cygwin shell.
>
> I think this is something
On 8/6/07, Mathieu Malaterre wrote:
> Hi Miguel,
>
> I do that all the time. You only need to modify PATH to work on
> cyginw (ie. replace the ; with :). You should NOT change LIB or
> INCLUDE, those variable are read by cl/link thus should contains ; as
> separators
This was the source of it al
2007/8/6, Eric Noulard <[EMAIL PROTECTED]>:
>
> rpmbuild -bb --define="_topdir
> /LOCAL/ERIC/tools/CMake/build_CMake/RPM"
> --buildroot=/LOCAL/ERIC/tools/CMake/build_CMake/_CPack_Packages/RPM
> /LOCAL/ERIC/tools/CMake/build_CMake/RPM/SPECS/cmake_fast.spec
just a precision regarding the --define ar
2007/8/6, Christian Convey <[EMAIL PROTECTED]>:
> > but the CMake macro writer may want to SET value as a GUESSED.
> >
> > SET(VAR [VALUE] [CACHE TYPE DOCSTRING [FORCE]] [GUESSED])
> >
> > Do you think this proposition deserve a feature request?
> >
>
> I think something about CMake needs rethinkin
2007/8/6, Alexander Neundorf <[EMAIL PROTECTED]>:
>
> Yes, it seems so. The one for the source RPM would be a full regular spec file
> as far as I understand.
Yes.
I attached a example of such a generated file: cmake.spec
> The one for the binary would have to be quite special.
> How does rpmbuil
On 8/6/07, Eric Noulard <[EMAIL PROTECTED]> wrote:
> 2007/8/5, Christian Convey <[EMAIL PROTECTED]>:
> [...]
> If I summarize I think a VAR may be tested with
>
> IF (DEFINED VAR) --> if true VAR is defined with a value
> IF (CACHED VAR) --> if true VAR value comes from CACHE
> IF (PROVIDED VAR
Hi Miguel,
I do that all the time. You only need to modify PATH to work on
cyginw (ie. replace the ; with :). You should NOT change LIB or
INCLUDE, those variable are read by cl/link thus should contains ; as
separators
HTH
-Mathieu
On 8/6/07, Miguel A. Figueroa-Villanueva <[EMAIL PROTECTED]>
Hello everyone,
Does anyone generate NMake makefiles and spawns the build from a
cygwin bash shell. If I generate Visual Studio 8 project files, then I
can use the following:
devenv8.com CMake.sln /build Release /project ALL_BUILD
from cygwin bash shell with no problems. But I can't manage to la
Hi,
On Saturday 04 August 2007 15:58, Eric Noulard wrote:
> Re-send to the list because previous attached files were too big.
...
> rpmbuild take RPM building specification file (the .spec file)
> which contains [among other things]
> explicit dependencies given by the user who wrote the .spec,
>
25 matches
Mail list logo
