Andreas Pakulat wrote:
On 25.09.09 16:07:21, Bill Hoffman wrote:
I am happy to announce that CMake 2.8.0 has entered the beta stage! You
can find the source and binaries here: http://www.cmake.org/files/v2.8/.
I am sure I am leaving something out, but here is the list of changes
that I came up
Mathieu Malaterre wrote:
Hi there,
I do not understand how regular expression are parsed to detect
error. When I look at page:
http://www.cdash.org/CDash/viewConfigure.php?buildid=437117
Clearly the error is hard to indentify. However if I open the
CMakeError.log file:
Determining if this
David Cole wrote:
Thanks for the info, I'll fix the project later. I believe however
that I
didn't see any warnings, which should now be posted if I understood
correctly? Or is that part of the OLD behaviour still working?
If you set the policty to OLD, you should just get the
James Bigler wrote:
Silly me. That wasn't a very helpful bug report.
I updated CMake from CVS last night at approximately 9 PM MDT.
I have XCode 3.0 installed.
OSX is version 10.5.8.
I also just verified that I have the same problem with CMake 2.8 RC 1.
James
On Tue, Sep 29, 2009 at 5:04
Orion Poplawski wrote:
On 09/25/2009 02:07 PM, Bill Hoffman wrote:
I am happy to announce that CMake 2.8.0 has entered the beta stage! You
can find the source and binaries here: http://www.cmake.org/files/v2.8/.
When building for Fedora:
98:
98: Total Test time (real) = 0.05 sec
98
Sean McBride wrote:
Hi all,
I've been setting up a nightly dashboard for CMake, VTK, and ITK on Mac
OS X 10.6.1 using ctest 2.8rc1. Several times now I've see a test
consume 100% CPU for a long time and yet ctest is not killing it and
timing out. Here's a test I killed myself from Activity
Alan W. Irwin wrote:
As part of the build of PLplot and for STRING_INDEX = 01, 02, ...,
I have created test targets x01c, x02c, with
add_executable(x${STRING_INDEX}c x${STRING_INDEX}c.c)
target_link_libraries(x${STRING_INDEX}c plplot${LIB_TAG})
where LIB_TAG is d, and plplotd is a target
Alan W. Irwin wrote:
On 2009-09-29 16:36-0400 Bill Hoffman wrote:
make -j N is only supported with the all target.
How difficult would it be to implement parallel build support for more than
just the all target? Note, if there is some limitation that makes it
impractical or inefficient
Chris Roberts wrote:
Hello,
I am trying to implement support for a new language compiler but I'm
having difficulty with link phase.
The problem is that I need to split the link step into two different
commands and filter the objects that are sent to each linker.
Currently cmake is generating
Dixon, Shane wrote:
Does CMake have the ability to report how long it took CTest to get the
result from the test program?
It seems like it might be a good option to have the response times next
to the pass/fail status so I know when a build improves performance.
It’s obviously keeping
:
So was anyone else able to reproduce this issue?
James
On Tue, Sep 29, 2009 at 10:07 AM, James Bigler
jamesbig...@gmail.com wrote:
On Tue, Sep 29, 2009 at 9:40 AM, Bill Hoffman
bill.hoff...@kitware.com
wrote:
James Bigler wrote:
Silly me. That wasn't a very helpful bug report.
I updated
Sean McBride wrote:
On 10/1/09 11:17 PM, James Bigler said:
Well, it worked just fine with CMake 2.4.6, so wouldn't this be a
regression?
I guess. Or possibly you were lucky it ever worked (as in, relying on
undefined behaviour that changed). I have no idea. :)
I just found it a little
James C. Sutherland wrote:
On Oct 2, 2009, at 8:20 AM, merean...@gmail.com merean...@gmail.com
wrote:
CMakeLists.txt
cmake_minimum_required(VERSION 2.6)
SET(TEST CACHE STRING test variable)
INSTALL(SCRIPT ${CMAKE_CURRENT_SOURCE_DIR}/install.cmake)
install.cmake
Sean McBride wrote:
On 10/2/09 10:40 AM, Bill Hoffman said:
We did change CMake. Before we used to hard code the build archs into
the file (i386, ppc, etc.). We now use a variable that Xcode uses,
something like $(DEFAULT_ARCH) different name, but you get the idea. If
that is not defined
CMake 2.8.0 RC 2 is now ready for people to try.
You can find the source and binaries here: http://www.cmake.org/files/v2.8/.
Here are the changes for the 2.8.0 branch so far:
Changes in CMake 2.8.0 RC 2
- Fix FindQt4 so that QtHelp depends on QtNetwork
- Add missing copyright notice to
Alan W. Irwin wrote:
\
As for your request to explain why the second and third results are
identical, I leave that to those who understand how and why CMake has been
implemented in the way it has. I am not in that group, which is why I
always
fall back to simple experiments like above to
James Bigler wrote:
On Fri, Oct 2, 2009 at 9:32 AM, Bill Hoffman bill.hoff...@kitware.com wrote:
Sean McBride wrote:
On 10/2/09 10:40 AM, Bill Hoffman said:
We did change CMake. Before we used to hard code the build archs into
the file (i386, ppc, etc.). We now use a variable that Xcode
michael kapelko wrote:
I tried MSYS and it didn't work. The same error arises:
Linking CXX shared library libLightfeather.dll
/bin/sh: C:/MinGW/bin/c++.exe: Bad file number
make[2]: *** [libLightfeather.dll] Error 126
make[1]: *** [CMakeFiles/Lightfeather.dir/all] Error 2
make: *** [all] Error
michael kapelko wrote:
version 2.6.4
_
Which generator are you using?
the msys one does not use link scripts, but the migw one does. You
might want to try the mingw one. Or if you want to edit CMake source,
you could try changing the msys one to use a link script:
michael kapelko wrote:
I've tried Unix Makefiles, MSYS Makefiles. Both produced Bad
argument number error during linkage.
I cannot use MinGW Makefiles within MSYS, because CMake complains,
that MinGW's make won't work when sh.exe is in the PATH. When I remove
sh.exe from the PATH, not a single
Yong Choo wrote:
We are in process of porting s/w and We are trying to assess the # of
compilation errors that we will be encountering.
The problem is that the way our cmake build env is setup, the build
stops at the first encounter with an error.
We would like to 'keep going' regardless of
michael kapelko wrote:
I tried to change cmGlobalMSYSGenerator and to use MinGW Makefiles in
MSYS the way you suggested. Nothing helped.
Well, you have hit a hard limit for the command line on windows... You
are going to have to break your code down into smaller bits...
One hack I can
Andrew Maclean wrote:
I am going to admit the possibility that I am doing something stupid.
If so please tell me what I am doing wrong!
In a nutshell:
Creating a windows package to install to a subdirectory does not work.
Also I don't think CPACK_NSIS_DISPLAY_NAME works.
In order to illustrate
Andrew Maclean wrote:
The only way that I can get this to work is to do this:
string(REPLACE / NATIVE_CMAKE_INSTALL_PATH ${INSTALL_DIRECTORY})
set(CPACK_PACKAGE_INSTALL_DIRECTORY ${NATIVE_CMAKE_INSTALL_PATH}
CACHE INTERNAL )
So, to avoid \\ hell with CPack, you can do what we do
j s wrote:
On 64-bit windows with CMAKE, how do you choose whether to use the 32
bit or 64 bit visual c++ compiler for the visual studio generator? I am
thinking about starting to cross compile both 64 bit and 32 bit version
of the software, but all I have right now is the 32 bit compiler.
Orion Poplawski wrote:
On 10/08/2009 05:04 PM, Orion Poplawski wrote:
On 10/02/2009 09:38 AM, Bill Hoffman wrote:
CMake 2.8.0 RC 2 is now ready for people to try.
You can find the source and binaries here:
http://www.cmake.org/files/v2.8/.
ctest -V -j2 fails here:
Tested on another system
Bill Hoffman wrote:
Orion Poplawski wrote:
On 10/08/2009 05:04 PM, Orion Poplawski wrote:
On 10/02/2009 09:38 AM, Bill Hoffman wrote:
CMake 2.8.0 RC 2 is now ready for people to try.
You can find the source and binaries here:
http://www.cmake.org/files/v2.8/.
ctest -V -j2 fails here
Pau Garcia i Quiles wrote:
Hello,
Any plans to publish a new edition of the book for CMake, CTest,
CPack, etc 2.8 ?
Yes, we are working on a new edition.
-Bill
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
Shepherd, Jason F wrote:
Hi all,
I'm currently using Cmake 2.8b. I'm trying to add a requirement (based
on another conditional statement) to find the LAPACK and BLAS packages
to VTK's Infovis capabilities. I've added the following lines to my
CMakeLists.txt
FIND_PACKAGE(BLAS REQUIRED)
Kelly (KT) Thompson wrote:
On Fri, Oct 9, 2009 at 6:15 AM, Sebas spas...@gmail.com
mailto:spas...@gmail.com wrote:
I send a example where happen explained before ( I have similar
struct in my Program). I include too the VS2008 project generate by
cmake. In the Fortran Project be
Orion Poplawski wrote:
On 10/08/2009 08:56 PM, Bill Hoffman wrote:
Bill Hoffman wrote:
Did you do an in-source build? That might be the problem, we almost
always test out of source.
That was it. Moving to out of tree worked.
I just verified that -j N1 fails with those tests when doing
CMake 2.8.0 RC 3 is now ready for people to try.
You can find the source and binaries here: http://www.cmake.org/files/v2.8/.
Here are the changes for the 2.8.0 branch so far:
Changes in CMake 2.8.0 RC 3
- CTest Added OS Platform (cpu architecture) detection support to
windows system
-
Romain CHANU wrote:
Hi,
I have included Bill in this conversation.
Bill, I think you are currently working on the development of CMake,
could you answer our questions regarding the integration between Eclipse
and CMake (cf. emails below)?
Alex has been doing most of the Eclipse support.
Alexander Neundorf wrote:
On Saturday 10 October 2009, Bill Hoffman wrote:
CMake 2.8.0 RC 3 is now ready for people to try.
You can find the source and binaries here:
http://www.cmake.org/files/v2.8/.
Here are the changes for the 2.8.0 branch so far:
Changes in CMake 2.8.0 RC 3
- Avoid non
Alexander Neundorf wrote:
- Create INTERPROCEDURAL_OPTIMIZATION build feature
I stumbled about this one, as it broke our build (we were using the -ipo flag
for compiling, which didn't work anymore).
After setting the new INTERPROCEDURAL_OPTIMIZATION property to TRUE it worked
again.
Is
K. Noel Belcourt wrote:
Hi,
Is there an easy way to have CMake emit the compile line only if a
compile error occurs? We prefer to build with VERBOSE output off and
were looking for a cleaner way to emit diagnostics.
Anyone know if this is possible?
This is not possible with CMake right
Vladimir Lebedev-Schmidthof wrote:
No I didn't. I just did and all compiled and linked successfully.
Sorry for stupid questions then, I will remember to clean
cmake-generated files in future.
Thank you very much.
--
You should use out of source builds in the future... :)
-Bill
Timi Tuohenmaa wrote:
Hi,
FindJNI script throws some errors (and probably does not work if Java
is installed in some way that it's path is not told in Windows
registers).
I did write a bug report about this, but I made it minor bug so no-one
seems to care.
Bill Spotz wrote:
Hi,
I am a Trilinos developer, so I recently upgraded to CMake version 2.8
so that I could test the Trilinos release 10 tarball.
I am seeing certain unit tests fail that were working before (in the
Trilinos release 10 repository) and this is the current state of my
Murray Cumming wrote:
I'm trying to use CMake for the first time, as an experiment, with
little a Qt-based project. It also uses an additional library, via
pkg-config.
So far Qt's include files don't seem to be found, and I wonder how I can
cause moc to be used to generate some of the .cc
James C. Sutherland wrote:
I am using configure_file to copy files during the build process. I
have a nested directory structure, that can be represented as:
/rootdir
CMakeLists.txt
/test
CMakeLists.txt
When processing rootdir/test/CMakeLists.txt, I have the
Adriano Gagliardi wrote:
Dear All,
Is it possible to specify within your CMakeLists.txt file where to place the
CMakeCache.txt and cmake_install.cmake files? I'd preferably have them
within the CMakeFiles directory.
No, this is not possible. I would suggest out of source builds.
-Bill
James Bigler wrote:
Has the requirements to configure_file changed? From the 2.6.4 docs:
configure_file
Copy a file to another location and modify its contents.
configure_file(InputFile OutputFile
[COPYONLY] [ESCAPE_QUOTES] [...@only])
The Input and
Dixon, Shane wrote:
If linux has valgrind which is an open source memory checker, is there
any equivalent on Windows? I noticed ctest supports purify, but it
looks like that's only a pay solution. Am I out of luck trying to find
a memory checker that's open source on Windows?
As far as I
Miguel A. Figueroa-Villanueva wrote:
On Fri, Oct 9, 2009 at 9:13 PM, Bill Hoffman wrote:
CMake 2.8.0 RC 3 is now ready for people to try.
You can find the source and binaries here: http://www.cmake.org/files/v2.8/.
I just downloaded the CMake 2.8rc3 and had a problem with ctest. For
some
Andreas Pakulat wrote:
Hi,
in kdevelop4 we're running cmake to prepare a builddirectory from a source
dir. This worked just fine on linux, however we're running into a problem
when executing on Windows for the NMake-Generator.
It seems this generator absolutely needs a shell (i.e. cmd.exe) as
Andreas Pakulat wrote:
On 26.10.09 11:21:07, Bill Hoffman wrote:
Andreas Pakulat wrote:
Hi,
in kdevelop4 we're running cmake to prepare a builddirectory from a source
dir. This worked just fine on linux, however we're running into a problem
when executing on Windows for the NMake-Generator
Robert Dailey wrote:
Hello,
I'm using the latest RC build of CMake 2.8 and I noticed a new
annoyance. Please follow these steps:
1. Create a CMakeList.txt that sets up a project with any number of
source files in it (4 should do fine).
2. On Windows, run the cmake-gui tool to
Robert Dailey wrote:
Thanks for the info. Speaking of the nightly build, why is the nightly
version 2.7 and the RC is 2.8? Shouldn't the nightly always be greater
or the same version as the RC builds? I'm confused.
Keep looking:
http://www.cmake.org/files/vCVS/?C=M;O=D
The Nightly is
Kevin Burge wrote:
I neglected to mention that the same cmake files do not do this on the
same release of cmake on Linux, Solaris or AIX
I am pretty sure this is the same issue as the ZERO_CHECK problem that
has been on the list. Can you try the nightly version 2.9 Oct 27 and
see if it
CMake 2.8.0 RC 4 is now ready for people to try.
You can find the source and binaries here: http://www.cmake.org/files/v2.8/.
Here are the changes for the 2.8.0 branch so far:
Changes in CMake 2.8.0 RC 4
- Fix try_compile when file cannot be found
- Add new module to test manifest installation
In CVS CMake and in the new 2.8 RC 4, there is a new module called:
CMakeVerifyManifest.cmake.
To run it, cd into the binary install directory for your project and run
cmake -P /path/to/CMakeVerifyManifest.cmake. It will check dll and exe
files for embedded manifests and make sure they match
L.M. de Vries wrote:
Hi,
Just confirming that this problem is solved with RC4.
Yes, it should be.
-Bill
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep
Timi Tuohenmaa wrote:
Hi,
I wish that fix for bug #9687 should be in final 2.8.0 too (at least
it is not mentioned in this).
Without it the whole Codeblocks with NMake is too much broken.
I am pretty sure that fix is in the release, but I did not mention it...
Can you try?
-Bill
Mathieu Malaterre wrote:
# ok we found jni.h, now derive other location from it:
get_filename_component(jni_path ${JAVA_INCLUDE_PATH} PATH)
FIND_PATH(JAVA_INCLUDE_PATH2 jni_md.h
${jni_path}
${jni_path}/win32
${jni_path}/linux
${jni_path}/freebsd
)
FIND_PATH(JAVA_AWT_INCLUDE_PATH
Modestas Vainius wrote:
Hello,
On ketvirtadienis 29 Spalis 2009 14:50:14 Mathieu Malaterre wrote:
On Thu, Oct 29, 2009 at 1:35 PM, Bill Hoffman bill.hoff...@kitware.com
wrote:
Mathieu Malaterre wrote:
# ok we found jni.h, now derive other location from it:
get_filename_component(jni_path
Modestas Vainius wrote:
P.S. Bill, when do you expect 2.8.0 final to be ready?
Hopefully soon. I am pretty much in regression fix only mode now.
-Bill
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
Will Dicharry wrote:
Is there a 2.8.0 release branch where I can make that change?
Make the change in head, and I will merge it into the next RC.
-Bill
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
Dixon, Shane wrote:
Are you running from the command-line or from the cmake-gui? If you're
running from the command-line, you need to be sure to run it from the
visual studio command prompt because it's picky about the environment.
When I generated visual studio 2008 projects in CMake 2.6, I
Sarbak, Joseph wrote:
Hello Bill and Shane,
Thanks for offering your help. Below is a listing of my directory where
I have the compilers installed, my PATH=, and also two of the cached
variables Bill asked about. I don't know how to get two (MAKECOMMAND,
and CMAKE_BUILD_TOOL) of those
Kelly (KT) Thompson wrote:
Hi,
I am trying to use Intel ifort on Linux to compile source code that uses
the extension .F95. By default, ifort will not compile files with this
extension. To allow the compilation, the name of the source file must
be preceded by -Tf (treat the next option as
shreyas krishnan wrote:
Thanks for the info. I am wondering if the paths were fixed manually,
would the makefile be portable. I will make sure the same compiler in
my case VC++ 08 is available on the other system.
The makefiles and the IDE can actually invoke CMake again once the
generation
jago jagoc wrote:
Hi,
I am some problem using INCLUDE_DIRECTORIES macro, i am using Cmake
2.6 - path 0 and Visual studio 2005.
In my Cmakelist.txt
...
SET(MYINCLUDE_DIR ../3rdParty/include CACHE STRING My include dir
You may add additional search paths here. Use ; to separate multiple
paths.)
jago jagoc wrote:
jago jagoc wrote:
Hi,
I am some problem using INCLUDE_DIRECTORIES macro, i am using Cmake
2.6 - path 0 and Visual studio 2005.
In my Cmakelist.txt
...
SET(MYINCLUDE_DIR ../3rdParty/include CACHE STRING My include dir
You may add additional search paths here. Use ; to separate
tech user wrote:
Hi John
sadly RHEL5 comes with qt 3.3 installed. :-(
qt-3.3.6-23.el5
We did got errors while runing ./configure --qt-gui
Remove your build/source tree, and reconfigure with an out of source
build, and it should be fine. CMake has an issue where you can not
bootstrap
Steven Wilson wrote:
Consider the following:
foo.cpp
#include iostream
int main()
{
std::cout foo std::endl;
return 0;
}
CMakeLists.txt
cmake_minimum_required(VERSION 2.6.4)
add_executable(foo foo.cpp)
set(BUILD_FOO ON PARENT_SCOPE)
With CMake built from the CMake-2-8 branch
Mathieu Malaterre wrote:
Hi there,
I'd like to know if this is possible to execute a cmake custom
target from my nightly ctest script.
Eg. In cmake
...
ADD_CUSTOM_COMMAND(
OUTPUT bla.txt
COMMAND echo bla bla.txt
VERBATIM
)
ADD_CUSTOM_TARGET(BLA DEPENDS
jago jagoc wrote:
Hi Bill,
Sorry if i reply the issues but it's strange that the
INCLUDE_DIRECTORIES add the project dir to all its parameter.
Is there a way to include some dir with INCLUDE_DIRECTORIES macro
without the project directory before?
I would like to add only a relative path
Alexander Neundorf wrote:
On Tuesday 03 November 2009, Bill Hoffman wrote:
Mathieu Malaterre wrote:
Hi there,
I'd like to know if this is possible to execute a cmake custom
target from my nightly ctest script.
Eg. In cmake
...
ADD_CUSTOM_COMMAND(
OUTPUT bla.txt
COMMAND echo bla
CMake 2.8.0 RC 5 is now ready for people to try. This is getting very
close to the final 2.8.0. Only regressions will be addressed, no new
features, so please give it a try. Thanks.
You can find the source and binaries here: http://www.cmake.org/files/v2.8/.
Here are the changes for the
James Bigler wrote:
I updated to CVS top of tree and tried to compile on my Mac. I got the
following error:
Linking CXX executable ../bin/ccmake
Undefined symbols:
_lzmadec_init, referenced from:
_lzma_bidder_init in
libcmlibarchive.a(archive_read_support_compression_xz.c.o)
th@gmx.de wrote:
What version of ctest? What OS?
I am actually working on Windows XP with ctest version 2.6-patch 4
I changed over to learn the windows batch a bit and I created a short script to
do the work, for some things I planed to integrate into ctest.
The rest works like a charm
John Drescher wrote:
-- Forwarded message --
From: Wen Shi ws...@sfu.ca
Date: Sat, Nov 7, 2009 at 2:19 AM
Subject: Re: [Insight-users] Problem with CMakelist
To: John Drescher dresche...@gmail.com
Hi john,
Thank you for your reply.
But actually I first used
Daniel Dunbar wrote:
Hi,
I've been looking at the CMake generated Xcode project files and I'm
wondering if the dependency hacks (XCODE_DEPEND_HELPER.make) are
absolutely necessary in newer versions of Xcode. That file has some
comment about avoiding a bug in Xcode 1.5 -- is it possible to
Daniel Dunbar wrote:
Hi Bill,
Thanks for the reply.
The uses I'm seeing aren't on external targets, they are for internal
libraries which are built during the build. Is this the same problem?
Pretty much the same problem. A lot of it has to do with static
libraries, if you link a target to
Steven Wilson wrote:
On Mon, Nov 9, 2009 at 11:36 AM, Eric Noulard eric.noul...@gmail.com
mailto:eric.noul...@gmail.com wrote:
2009/11/9 Steven Wilson steven.wesley.wil...@gmail.com
mailto:steven.wesley.wil...@gmail.com:
What CVS tag is used for the 2.8.0 release?
I guess
CMake 2.8.0 RC 6 is now ready for people to try. This is getting very
close to the final 2.8.0. I think this is the last one. Please let me
know if you find any serious regressions. I hope to release 2.8.0 final
this week. Thanks.
You can find the source and binaries here:
Jeroen Dierckx wrote:
I noticed that libraries are put into the link flags. They don't show up
in the Linked Libraries list of the target's info. Could it be that
everything works correctly if we could libraries there? I think XCode
does some extra logic in that case, as opposed to
CMake 2.8.0 RC 7 is now ready for people to try. Due to a few missed
files and a bug in ctest that was not fixed on the branch, I have made
an RC 7. Please let me know if you find any serious regressions. I
still plan to release 2.8.0 final this week. Thanks.
You can find the source and
Jed Brown wrote:
Mark Moll wrote:
Add -F /opt/local/Library/Frameworks to your compilation flags or
add this line to your .bash_profile:
You should never add the -F to the CMake flags, just use the full path
to the framework dir in either an include or a link library and CMake
will add the
Kelly T. Kirk (CISD/CIV) wrote:
Hugh Sorby wrote:
Hi,
I am using CMake 2.6 and I would like to be able to decompress bz2
files. Is it possible to add bz2 compression to the tar command (or
even better is it already there?). I was hoping to do something like
cmake -E tar xjf
James Bigler wrote:
CMake then chokes on the PACKAGE_NAME due to the \O which should be
\\O. I set the DISPLAY_NAME and INSTALL_DIRECTORY, but the PACKAGE_NAME
is set by the cpack_set_if_not_set and sends my string through an extra
processing step.
I can certainly add my own entry for
Bill Hoffman wrote:
# if the user has set CPACK_NSIS_DISPLAY_NAME
# remember
if(DEFINED CPACK_NSIS_DISPLAY_NAME)
SET(CPACK_NSIS_DISPLAY_NAME_SET TRUE)
endif()
cpack_set_if_not_set(CPACK_NSIS_DISPLAY_NAME
${CPACK_PACKAGE_INSTALL_DIRECTORY})
# if the user has set CPACK_NSIS_DISPLAY
James Bigler wrote:
It looks good from the code inspection, but I'll have to test it when I
get a copy of either the RC or the nightly tomorrow. I don't have Qt
compiled on my machine to build CMake-gui.
You should be able to just move the CPack.cmake into the rc7 directory
and give it a
aaron_wri...@selinc.com wrote:
I've tried this on several machines and CMake always seems to think the
box is x64 even though it clearly says it's x86. I can fix the problem
by deleting CMakeCache.txt and running CMake again, which is weird. I'm
trying to automate the whole thing in a night
Richard Wackerbarth wrote:
Aaron,
Perhaps I have it wrong, but I think that the problem is that you are using
CMakeCache.txt that was created on a different machine.
CMakeCache.txt acts as a configuration file that overrides the registry,
environmental variables, and everything else that has
aaron_wri...@selinc.com wrote:
I have the windows SDK installed. It came with Visual Studio. I run
everything from perl, so in my script, I set the environment to:
$ENV{VSINSTALLDIR} = C:\\Program Files\\Microsoft Visual
Studio 9.0;
$ENV{VCINSTALLDIR} = C:\\Program
Tyler Roscoe wrote:
On Fri, Nov 13, 2009 at 01:01:15PM +0100, Aslund wrote:
CMake Warning at plugin/CMakeLists.txt:15 (ADD_LIBRARY):
Cannot generate a safe linker search path for target Rob01Ex1 because
files
in some directories may conflict with libraries in implicit directories:
link
Bill Lorensen wrote:
Bill,
Is there some way this can be added to the cmake test suite? Remember,
If it's not tested, it's broken.
Yup, I can add something for this. I did add it to a test before
sending the patch to the list. I just have not committed the new test.
-Bill
aaron_wri...@selinc.com wrote:
Bill,
I think you were right. I took a hard look at my SDK paths and
changed a capital I to a lower-case i and everything seems better.
Thanks for help.
On a side note, perhaps assuming x64 when x86 fails is a bad
algorithm, or at least
On behalf of myself, Ken, Brad, Dave, Alex and the rest of the
CMake team, we are pleased to announce that CMake 2.8.0 is
available for download at:
http://www.cmake.org/cmake/resources/software.html
Here are the changes for CMake 2.8.0:
Changes in CMake 2.8.0 Release
- CPack: Honor
Michael Jackson wrote:
On Nov 13, 2009, at 7:23 PM, Clinton Stimpson wrote:
On Friday 13 November 2009 05:05:36 pm Michael Jackson wrote:
OS X classic dylib problems. My Dylibs have the full path as their
install_name. When I do a make install I have scripts run over
those libraries to fix
Maik Beckmann wrote:
2009/11/14 Bill Lorensen bill.loren...@gmail.com:
IN itk this is what we typically do in ctest scripts.
After
CTEST_CONFIGURE (BUILD ${CTEST_BINARY_DIRECTORY})
place
CTEST_READ_CUSTOM_FILES(${CTEST_BINARY_DIRECTORY})
Sweet! This solves the CTestCustom.cmake issue with
Tyler Roscoe wrote:
On Sat, Nov 14, 2009 at 07:01:23PM -0500, David Manura wrote:
CMAKE_SHARED_LIBRARY_PREFIX is blank on MSVC, unlike on most platforms
(MinGW included):
I don't know how to solve your problem but none of the Windows libraries
I've seen use the convention of putting lib at
Emmanuel Blot wrote:
Hi All,
I've just upgraded my CMake installation to 2.8.0, as my collegues
reported me some compilation errors with the new release of CMake
(they use Debian/unstable).
Before I'm able to reproduce the same error they got, I got another
error, on Mac OS X hosts.
It seems
Maik Beckmann wrote:
2009/11/14 Bill Lorensen bill.loren...@gmail.com:
IN itk this is what we typically do in ctest scripts.
After
CTEST_CONFIGURE (BUILD ${CTEST_BINARY_DIRECTORY})
place
CTEST_READ_CUSTOM_FILES(${CTEST_BINARY_DIRECTORY})
Sweet! This solves the CTestCustom.cmake issue with
Maik Beckmann wrote:
2009/11/16 Maik Beckmann beckmann.m...@googlemail.com:
2009/11/16 Bill Hoffman bill.hoff...@kitware.com:
http://my.cdash.org/viewNotes.php?buildid=38044
If nothing is checked out, it will checkout the code, then read the config
file after that.
Checking your script now
Bill Hoffman wrote:
Maik Beckmann wrote:
2009/11/16 Maik Beckmann beckmann.m...@googlemail.com:
2009/11/16 Bill Hoffman bill.hoff...@kitware.com:
http://my.cdash.org/viewNotes.php?buildid=38044
If nothing is checked out, it will checkout the code, then read the
config
file after
Eric M. LaFranchi wrote:
Unable to find a cmake port for the HP-NonStop platform, I am working
though the details of porting using cmake-2.8.0 source.
What is HP-NonStop?
A few issues, so far:
1. After the initial part of the bootstrap process, I changed
CMakeCache.txt to use the
Celil Rufat wrote:
On a Windows 7 machine I cannot read any registry values that contain a
semicolon.
For example if you have 7-zip, running the following
SET(MYPATH [HKEY_LOCAL_MACHINE\\SOFTWARE\\7-Zip;Path])
MESSAGE(MYPATH = ${MYPATH})
results in
MYPATH =
901 - 1000 of 2920 matches
Mail list logo
