On Wed, 2009-08-19 at 11:02 -0700, Tyler Roscoe wrote:
On Wed, Aug 19, 2009 at 11:54:18AM -0600, Timothy M. Shead wrote:
If you are using CMake to generate makefiles, you can run make clean
in a subdirectory of your build tree, and make will only remove the
files for that directory - you
On Wed, 2009-08-19 at 21:20 -0700, Tim Kientzle wrote:
David Cole wrote:
You're using incorrect arguments as DEPENDS. Things that follow DEPENDS
should be full path file names... not cmake target names.
Okay, I think I finally figured out how to do what I need (which is,
of course, to
Hi Steve,
Unless you're using make's -j option, there should not be any
concurrency issues. Check the command line and your MAKEFLAGS variable.
Best regards,
Marcel Loose.
On Wed, 2009-08-19 at 17:31 -0700, Steve Mathers wrote:
Hi Michael. that option is what I am already doing, which is why
John R. Cary wrote:
I am trying to build cmake on a Blue Gene P.
Configuration starts with
login1.surveyor$ ./bootstrap
-
CMake 2.6-4, Copyright (c) 2007 Kitware, Inc., Insight Consortium
[snip]
Brad King wrote:
John R. Cary wrote:
I am trying to build cmake on a Blue Gene P.
Configuration starts with
login1.surveyor$ ./bootstrap
-
CMake 2.6-4, Copyright (c) 2007 Kitware, Inc., Insight Consortium
[snip]
Bill Hoffman wrote:
So, it must be that the library is built with no soname. Brad will be
back in a few days, and should have a better idea of how to fix it.
This is probably the problem. You can confirm this by running
readelf -d /home/kchang/sandbox/thost/thostmduserapi.so |grep SONAME
John R. Cary wrote:
env CC=xlc_r CXX=xlC_r
[snip]
-- The C compiler identification is GNU
Be sure to create a fresh build tree when changing compilers.
CMake cached the 'cc' (gnu) compiler it found the first time
and did not pay attention to the environment later.
Brad King wrote:
Be sure to create a fresh build tree when changing compilers.
CMake cached the 'cc' (gnu) compiler it found the first time
and did not pay attention to the environment later.
Got it. Now 'rm -rf' on the build tree.
which is basically Linux.
Building a project with pgcc/pgCC.
All flags are empty:
CMAKE_CXX_COMPILER
/opt/pgi/8.0.4/linux86-64/8.0-4/bin/pgCC
CMAKE_CXX_FLAGS
CMAKE_CXX_FLAGS_DEBUG
Message du 18/08/09 22:56
De : Bill Hoffman
A : lokmane.abbas-turki
Copie à :
Objet : Re: [CMake] .vfproj with cmake
OK, can you try this.
1. Run cmake --debug-trycompile
2. Do not load the project into the IDE.
3. Edit the cmTryCompileExec.vfproj file created by CMake,
Arjen Markus wrote:
I do not think this is going to work: object files created with g77
and gfortran are not compatible as far as I know.
What constructs are they? F90/95 has one or two deleted features
but most compilers will simply accept them, perhaps grudgingly.
[snip]
How can this be
John R. Cary wrote:
which is basically Linux.
Building a project with pgcc/pgCC.
All flags are empty:
CMAKE_CXX_COMPILER
/opt/pgi/8.0.4/linux86-64/8.0-4/bin/pgCC
CMAKE_CXX_FLAGS
CMAKE_CXX_FLAGS_DEBUG
Will Dicharry wrote:
Sorry for the month of delay, but I've addressed Mike Jackson's concerns
below and I think I'm close to having the HDF5 find module ready for
submission.
Excellent. I have a few comments from quickly glancing at them, but
I don't have time for thorough testing. Overall
Brad King wrote:
Will Dicharry wrote:
Sorry for the month of delay, but I've addressed Mike Jackson's concerns
below and I think I'm close to having the HDF5 find module ready for
submission.
Excellent. I have a few comments from quickly glancing at them, but
I don't have time for thorough
Will Dicharry wrote:
What is the convention for keeping a macro out of the public interface?
Leave it out of the documentation and name it with a '_hdf5_' prefix
(starting in '_').
-Brad
___
Powered by www.kitware.com
Visit other Kitware open-source
I am a real newbie here (exploring cmake) so my words should be taken
with a grain of salt. But we find (in our current autotools
setup), that it is good to have a flag that tells one whether the hdf5 was
compiled with --enable-parallel.
John Cary
Will Dicharry wrote:
Brad King wrote:
Will
John R. Cary wrote:
I am a real newbie here (exploring cmake) so my words should be taken
with a grain of salt. But we find (in our current autotools
setup), that it is good to have a flag that tells one whether the hdf5 was
compiled with --enable-parallel.
I agree that would be useful. I
Will Dicharry wrote:
John R. Cary wrote:
I am a real newbie here (exploring cmake) so my words should be taken
with a grain of salt. But we find (in our current autotools
setup), that it is good to have a flag that tells one whether the hdf5
was
compiled with --enable-parallel.
I agree
John R. Cary wrote:
Brad King wrote:
John, how do autotools detect this?
hdf5par=`grep HAVE_PARALLEL 1 $HDF5_INCDIR/H5config.h`
I suppose there are other ways, but we have been doing this through
several versions of hdf5.
Great, thanks John.
Will, you should be able to use the
Brad King wrote:
John R. Cary wrote:
Brad King wrote:
John, how do autotools detect this?
hdf5par=`grep HAVE_PARALLEL 1 $HDF5_INCDIR/H5config.h`
I suppose there are other ways, but we have been doing this through
several versions of hdf5.
Great, thanks John.
Will, you should be able to
Responses inline...
I'm reposting this to the CMake mailing list so someone can correct me
if I'm wrong, it looks like your message went only to me.
John R. Cary wrote:
Will Dicharry wrote:
John R. Cary wrote:
which is basically Linux.
Building a project with pgcc/pgCC.
All flags are
Brad King wrote:
John R. Cary wrote:
Brad King wrote:
John, how do autotools detect this?
hdf5par=`grep HAVE_PARALLEL 1 $HDF5_INCDIR/H5config.h`
I suppose there are other ways, but we have been doing this through
several versions of hdf5.
Great, thanks John.
Will, you should be able to
Will Dicharry wrote:
Brad King wrote:
John R. Cary wrote:
Brad King wrote:
John, how do autotools detect this?
hdf5par=`grep HAVE_PARALLEL 1 $HDF5_INCDIR/H5config.h`
I suppose there are other ways, but we have been doing this through
several versions of hdf5.
Great, thanks John.
Will,
On Thu, Aug 6, 2009 at 3:12 PM, Marcus D. Hanwellmar...@cryos.org wrote:
James Bigler wrote:
On Thu, Aug 6, 2009 at 12:10 PM, Bill Hoffman
bill.hoff...@kitware.com mailto:bill.hoff...@kitware.com wrote:
James Bigler wrote:
Well, I was using VS 2005 64 bit with SP 1. I wonder
On Thu, Aug 20, 2009 at 1:51 PM, Mike Jackson
mike.jack...@bluequartz.netwrote:
On Thu, Aug 6, 2009 at 3:12 PM, Marcus D. Hanwellmar...@cryos.org wrote:
James Bigler wrote:
On Thu, Aug 6, 2009 at 12:10 PM, Bill Hoffman
bill.hoff...@kitware.com mailto:bill.hoff...@kitware.com wrote:
On Thu, Aug 6, 2009 at 2:07 PM, Clinton Stimpsonclin...@elemtech.com wrote:
Bill Hoffman wrote:
James Bigler wrote:
I've just been bitten hard by this issue (many hours of frustration while
attempting to run a demo application that should have Just Worked (TM) ).
According to this page:
On Thu, Aug 20, 2009 at 4:06 PM, James Biglerjamesbig...@gmail.com wrote:
On Thu, Aug 20, 2009 at 1:51 PM, Mike Jackson mike.jack...@bluequartz.net
wrote:
On Thu, Aug 6, 2009 at 3:12 PM, Marcus D. Hanwellmar...@cryos.org wrote:
James Bigler wrote:
On Thu, Aug 6, 2009 at 12:10 PM, Bill
OK, I see the difference between the build directory and the build location
now, even though in my project structure I inherited, they are the same
directory - MMP
If I add the -C (path to makefile) option, I still get the error.
Im not moving the makefile. My cmake file and the resulting
Hi All,
I need to use a pre-compiled header.
I think that I recall that CMake is not yet equipped to handle this.
I found thought a Google search that SET_SOURCE_FILES_PROPERTIES might
be the way to go.
Has anyone implemented PCH and have an example, advice, etc?
Thanks!
-Jason
On Thu, Aug 20, 2009 at 5:25 PM, MLmailingli...@mailnewsrss.com wrote:
Hi All,
I need to use a pre-compiled header.
I think that I recall that CMake is not yet equipped to handle this.
I found thought a Google search that SET_SOURCE_FILES_PROPERTIES might be
the way to go.
Has anyone
Hold on there...
The Express editions are not meant to build redistributable binaries.
They're meant for personal use: i.e. -- each user compiles his own code. I'm
pretty sure it's a violation of the Express edition license agreement to
build binaries for other people. You need at least the
On Thu, Aug 20, 2009 at 5:25 PM, MLmailingli...@mailnewsrss.com wrote:
Hi All,
I need to use a pre-compiled header.
I think that I recall that CMake is not yet equipped to handle this.
I found thought a Google search that SET_SOURCE_FILES_PROPERTIES might be
the way to go.
Has anyone
John,
Awesome, thanks for both of the e-mails.
-Jason
On Aug 20, 2009, at 2:29 PM, John Drescher wrote:
On Thu, Aug 20, 2009 at 5:25 PM, MLmailingli...@mailnewsrss.com
wrote:
Hi All,
I need to use a pre-compiled header.
I think that I recall that CMake is not yet equipped to handle
I don't believe that to be the case with Visual Express 2008. I don't know
how previous editions work.
**
*Can I use Express Editions for commercial use?*
1.
Yes, there are no licensing restrictions for applications built using
Visual Studio Express Editions.
Thanks for the info That's what I get for expressing what I think are
facts from my flawed human memory. (Perhaps it was a fact with Express 2005
editions when I first read the licenses long ago...)
Sorry for the blip,
David
On Thu, Aug 20, 2009 at 5:40 PM, j s j.s4...@gmail.com wrote:
I
So I created the proper paths within the VCExpress installation and
placed the downloaded vcredist_x86.exe file in there. CMake found it.
NSIS found it and included it. I ran my new installer on a clean XP
SP3 machine. Verified the vcredist.exe actually ran also. Tried to
launch an application and
Did you try the dependency walker (available via google) to see if there may
be any dll's you need to have in the same directory as the binary?
Regards,
Juan
On Thu, Aug 20, 2009 at 5:03 PM, Mike Jackson
mike.jack...@bluequartz.netwrote:
So I created the proper paths within the VCExpress
Yep. First thing I have tried, and have been using all day. I think I
may have tracked part of the problem down to a few things.
1: vcredist_x86.exe - There are multiple versions of this (all with
the same file name). You have to make sure you download the correct
version. I have VCExpress 2008
OK. Turns out it was ITK being compiled in Debug mode and then trying
to link against it with a Release build.
On to some comments that might help others:
VCExpress 2008 SP1 does NOT come with VCRedist_x86.exe. You will need
to download the correct version.
VCExpress 2008:
39 matches
Mail list logo
