On 2007-03-16 15:30-0500 Matthew Woehlke wrote:
So maybe ADD_TEST needs a DEPENDS keyword?
I don't think such a precise depends mechanism is really warranted in this
case, and to make it really easy for users I have advocated in another post
just making the test target depend on the all target
Alan W. Irwin wrote:
If you always remember to run "make" (or the equivalent "make all") before
"make test" then you have worked around the dependency issue I found, and
indeed you seem to have found an additional bug (a discrepancy between
running make test and ctest). which is not relevant to t
On Friday 16 March 2007 17:56:46 Brandon J. Van Every wrote:
> Kishore, Jonnalagadda (IE10) wrote:
> > But then, despite setting the value I had to put in
> > INCLUDE_DIRECTORIES(.)
>
> And I was brief because I don't know if there any caveats on how it can
> be used. Maybe you found a bug. Mayb
On 2007-03-16 11:14-0500 Matthew Woehlke wrote:
Bill Hoffman wrote:
I am not sure everyone would be happy if make test depend on all. I
don't think that the typical unix make check will build anything will it?
The idea was to have the standard:
make
make test
Shouldn't that be "make chec
On 2007-03-16 08:20-0400 Bill Hoffman wrote:
I am not sure everyone would be happy if make test depend on all. I don't
think that the typical unix make check will build anything will it?
I don't know about other projects, but all the three active projects
(PLplot, libLASi, and FreeEOS) I am
kitts wrote:
But then, despite setting the value I had to put in
INCLUDE_DIRECTORIES(.)
And I was brief because I don't know if there any caveats on how it can
be used. Maybe you found a bug. Maybe the behavior isn't consistent
across generators. Maybe the value isn't propagated
On Friday 16 Mar 2007 IST, Brandon J. Van Every wrote:
> Kishore, Jonnalagadda (IE10) wrote:
> >> -Original Message-
> >>
> >>
> >> CMAKE_INCLUDE_CURRENT_DIR is the same as
> >> INCLUDE_DIRECTORIES(${CMAKE_CURRENT_BINARY_DIR}
> >> ${CMAKE_CURRENT_SOURCE_DIR}) for all targets.
> >>
> >>
Hello, cmake-request.
You wrote 16 марта 2007 г., 15:22:41:
> Alexander Ivash wrote:
>>> What do you mean by termination? Does cmake crash?
>>>
>> Yes. Here some exception deatails:
>> AppName: cmake.exe AppVer: 0.0.0.0 ModName: msvcr80d.dll
>> ModVer: 8.0.50727.762
Kishore, Jonnalagadda (IE10) wrote:
-Original Message-
CMAKE_INCLUDE_CURRENT_DIR is the same as
INCLUDE_DIRECTORIES(${CMAKE_CURRENT_BINARY_DIR}
${CMAKE_CURRENT_SOURCE_DIR}) for all targets.
If you have a project that constantly needs to add the current source
directory and the cur
Bill Hoffman wrote:
I am not sure everyone would be happy if make test depend on all. I
don't think that the typical unix make check will build anything will
it? The idea was to have the standard:
make
make test
Shouldn't that be "make check"? :-)
(http://www.cmake.org/Bug/bug.php?op=show&
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Filipe Sousa
> Sent: Friday, March 16, 2007 2:33 AM
> To: cmake@cmake.org
> Subject: Re: [CMake] CMAKE_INCLUDE_CURRENT_DIR?
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Kishore, Jonnalagad
At the same time, can you add support for multiple platforms in a single
.vcproj file? :)
Otherwise you'll need to create a separate .vcproj for every Windows CE
platform you target. May or may not be a big deal depending on your
setup / environment.
Stephane
-Original Message-
From:
Dear list,
I am highly interested in adding the Windows CE / MSVC platform to
cmake (it hasn't been done yet, right ?). I browsed the cmake source
and it appeared that what I need to do is to add a
"WindowsCE-cl.cmake" and "WindowsCE-cl.cmake.in" in Modules/Platform.
Is that right ?
Hopefully I c
Yes, it does.
The current limitation is that it does not support generating a single
.vcproj for the Win32 and x64 targets; you'll need to run it twice, and
use separate output directories.
Hope this helps,
Stephane
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Yu
Alexander Ivash wrote:
What do you mean by termination? Does cmake crash?
Yes. Here some exception deatails:
AppName: cmake.exe AppVer: 0.0.0.0 ModName: msvcr80d.dll
ModVer: 8.0.50727.762Offset: 0003b130
Can you build a debug version of cmake and get a
I am not sure everyone would be happy if make test depend on all. I
don't think that the typical unix make check will build anything will
it? The idea was to have the standard:
make
make test
make install
I guess the downside would be extra depend checking when running tests
on large projec
Dear list,
I am highly interested in adding the Windows CE / MSVC platform to
cmake (it hasn't been done yet, right ?). I browsed the cmake source
and it appeared that what I need to do is to add a
"WindowsCE-cl.cmake" and "WindowsCE-cl.cmake.in" in Modules/Platform.
Is that right ?
Hopefully I c
Hello,
Does CMake support VS 2005 x64 build? I know there was a feature request
about that. Is there any progress ?
Thanks and best regards,
Cigdem Yuksel
Engineer/Technologist
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/lis
> What do you mean by termination? Does cmake crash?
Yes. Here some exception deatails:
AppName: cmake.exe AppVer: 0.0.0.0 ModName: msvcr80d.dll
ModVer: 8.0.50727.762Offset: 0003b130
> I tried your
> command line and it did not crash.
The problem was not in comman
On Thursday 15 March 2007 19:50:36 Jean-Sébastien Guay wrote:
> Hello Alan,
> files. So I investigated the particular methods that were not being
> found on link, and I noticed that they were defined as inline in the
> .cpp file, but not declared inline in the header file.
>
> I don't know enough a
Thank you for reply!.. I tried your way of passing -D options and see
the same errors.
>>
>> The following sample from cmakelists.txt causes termination of cmake
>> on win32. I run "cmake -D "CROSSCOMPILE=TRUE" -D "TOOL=diab" -D
>> "CPU=SimNT" -D "UGL_INCLUDE=D:/WindRiver/components/windml-4.0/h"
21 matches
Mail list logo
