Hi,
>> I am wondering if there is a way to disable checking that the ELSE and
>> ENDIF arguments need to the the same as the initial IF. For example,
> [...]
> This is the default in CMake 2.6, you don't need to specify the statement in
> the endif.
Thanks!
I'm running on Cmake 2.4.8, and I was
On 2008-05-23 22:43-0400 Bill Hoffman wrote:
This is the default in CMake 2.6, you don't need to specify the statement in
the endif.
If you do specify something, is it checked?
e.g., will CMake-2.6.0 continue to find badly nested if statements
like
if(whatever0)
if(whatever1)
endif(whatever0
Eduardo Alberto Hernández Muñoz wrote:
Hi list,
I am wondering if there is a way to disable checking that the ELSE and
ENDIF arguments need to the the same as the initial IF. For example,
instead of
IF ( HUNGRY )
MESSAGE ( "Go get some food!" )
ENDIF ( HUNGRY )
you can type
IF
Hi,
I'm working on some software[0] that includes things built with CMake.
The process for building our project is semi-automated and to fully
automate it, we'd love to be able to verify your package releases.
As it stands, we can't verify that the software on your website is
correctly downloade
Hi list,
I am wondering if there is a way to disable checking that the ELSE and
ENDIF arguments need to the the same as the initial IF. For example,
instead of
IF ( HUNGRY )
MESSAGE ( "Go get some food!" )
ENDIF ( HUNGRY )
you can type
IF ( HUNGRY )
MESSAGE ( "Go get some
Bill,
On Friday 23 May 2008 09:27:54 Bill Hoffman wrote:
> But that would only work if they are using the IDE, nmake and make
> builds would still not work. Another approach is to use a forwarding
> executable. Have a wrapper program that sets PATH as needed to run
> things, and then execs the p
David,
On Friday 23 May 2008 09:14:11 David Cole wrote:
> If you want to write reg values with cmake, you can execute cmake as a
> sub-process with -E command line args (for example, using
> EXECUTE_PROCESS(COMMAND ${CMAKE_COMMAND} in your CMakeLists.txt file)
>
> Use the write_regv -E sub-co
KSpam wrote:
Bill,
On Friday 23 May 2008 06:14:27 Bill Hoffman wrote:
So, there is not much CMake can do for you. The only thing you can do
on windows is make sure that .exe and .dll files are all in the same
directory. Windows always looks first in the directory of the .exe for
any .dll file
Bill,
On Friday 23 May 2008 06:14:27 Bill Hoffman wrote:
> So, there is not much CMake can do for you. The only thing you can do
> on windows is make sure that .exe and .dll files are all in the same
> directory. Windows always looks first in the directory of the .exe for
> any .dll files it nee
If you want to write reg values with cmake, you can execute cmake as a
sub-process with -E command line args (for example, using
EXECUTE_PROCESS(COMMAND ${CMAKE_COMMAND} in your CMakeLists.txt file)
Use the write_regv -E sub-command:
cmake -E
CMake Error: cmake version 2.6-patch 0
Usage: cma
Arjen,
On Thursday 22 May 2008 23:35:33 Arjen Markus wrote:
> Having CMake set the necessary registry entries would not help with
> binary distributions of your product. I do not whether that is relevant
> to you, but in general that would be a problem:
> - Your clients may have the libraries inst
kent williams wrote:
http://public.kitware.com/Bug/view.php?id=7084
I made the simplest possible library project, and then messed it up
based on our build system just enough to reproduce the error. ;-)
Now obviously, what is done in this project -- Calling Cmake from make
to batch-configure pro
Blezek, Daniel J., Ph.D. wrote:
I'd like to build and install Insight (though the toolkit is not
important) using GCC. Then I want to build applications using GCC, the
Intel compiler, and IBM's XLC compiler. All should be able to use the
GCC-build libraries. However, CMAKE prohibits this w
http://public.kitware.com/Bug/view.php?id=7084
I made the simplest possible library project, and then messed it up
based on our build system just enough to reproduce the error. ;-)
Now obviously, what is done in this project -- Calling Cmake from make
to batch-configure projects -- might be off-l
> Also, to embellish on my last email, I used the dependencywalker
> utility to discover that the MSVCR80.dll could not be found. I don't
> really know where to look for it either. (VS Newbie)..
>
That is because it is hidden in cryptic folders off your windows install:
C:\WINXP\WinSxS\x86_Microso
Well my last email was wrong about 2003.net. I forgot to tell CMake to
use the 2003.net generator and so got a wrong message. After clearing
everything out and trying again, this time using a VS2003.Net command
prompt and telling cmake to use the Visual Studio 2003.Net generator I
can get a valid p
c135 is the "unable to locate dll" exception, not c0150004...
I could not find what c0150004 means using google, although apparently it
occurs frequently to people with Vista when it tries to do automatic
updating :-P
I suspect if you can run it under the debugger, you might be able to ca
kent williams wrote:
There seems to be something unique about our build system that is
causing this problem, and I am beginning to suspect what it is: It
calls cmake to do a command-line configure even if the build directory
is already configured.
This is kind of ridiculous to do, I know, but fo
Mike Jackson wrote:
Here ya go.. Hope this helps.
OK, so the error log has this:
Determining the endianes of the system passed. The system is big
endianTest produced following output:
Microsoft (R) Visual Studio Version 8.0.50727.42.
Copyright (C) Microsoft Corp 1984-2005. All rights reser
There seems to be something unique about our build system that is
causing this problem, and I am beginning to suspect what it is: It
calls cmake to do a command-line configure even if the build directory
is already configured.
This is kind of ridiculous to do, I know, but for one thing, the
config
I'm getting these results with cmake version 2.6-patch 0
On Fri, May 23, 2008 at 8:50 AM, Bill Hoffman <[EMAIL PROTECTED]> wrote:
>
> Also, what version of CMake are we talking about here? There were bugs in
> some versions of CMake with the -D and the cache. Perhaps it works when you
> use the
Mike Jackson wrote:
Not sure which list to ask on first so I'll try this one.
My Setup is Visual Studio 2005 Pro, CMake 2.4.8 on windows XP. I have
NO admin privs (USAF computer) and NO write access to the C: drive. VS
is installed on C: but everything else "user" related is on the D:
drive incl
Hi,
I'd like to build and install Insight (though the toolkit is not
important) using GCC. Then I want to build applications using GCC, the
Intel compiler, and IBM's XLC compiler. All should be able to use the
GCC-build libraries. However, CMAKE prohibits this with the
CMake_import_build_sett
Alan W. Irwin wrote:
On 2008-05-22 16:36-0500 kent williams wrote:
I'll ask this again.
We use a build system that for better or worse, invokes cmake from a
Makefile to configure ITK, VTK, KWWidgets etc.
In other words we have a command invoked from gnu make that looks like
this:
cmake /sc
So, there is not much CMake can do for you. The only thing you can do
on windows is make sure that .exe and .dll files are all in the same
directory. Windows always looks first in the directory of the .exe for
any .dll files it needs. CMake can put the files in the same directory.
That is w
Quoting Aleix <[EMAIL PROTECTED]>:
Hi list,
With the time, at work, I've been developing some finders
(find_package-called script).
I can see 2 issues here:
- Everytime I need to use another library, I have to develop another finder
(which might have been developed by someone else in another p
Am Freitag 23 Mai 2008 10:15:59 schrieb Alan W. Irwin:
> Thanks, Maik, for your additional response. For now, I have only skimmed
> what you said and don't completely understand the implications, yet, but my
> first impression is it looks like something special for fortran *.mod files
> is done in
Thanks, Maik, for your additional response. For now, I have only skimmed
what you said and don't completely understand the implications, yet, but my
first impression is it looks like something special for fortran *.mod files
is done in the C++ code rather than something more general that would wo
Am Freitag 23 Mai 2008 09:54:21 schrieb Aleix:
> Hi list,
>
> With the time, at work, I've been developing some finders
> (find_package-called script).
>
> I can see 2 issues here:
> - Everytime I need to use another library, I have to develop another finder
> (which might have been developed by so
Hi list,
With the time, at work, I've been developing some finders
(find_package-called script).
I can see 2 issues here:
- Everytime I need to use another library, I have to develop another finder
(which might have been developed by someone else in another place in the
world).
- Other people mig
Am Freitag 23 Mai 2008 08:57:21 schrieb Alan W. Irwin:
> On 2008-05-23 07:07+0200 Maik Beckmann wrote:
> >
> > All target directories, Fortran or not, contain a cmake_clean.cmake,
> > i.e. CMakeFiles/foolib.dir/cmake_clean.cmake
> > which in turn contains
> > {{{
> > #...
> > # Per-language clean
31 matches
Mail list logo
