Tim Kientzle wrote:
I'm having trouble with a custom target that
depends on another custom target defined in a
subdirectory. Here's a much-simplified version
of what I'm trying to do:
Turns out the subdirectory is a red herring.
Here's a much simpler demonstration of the bug:
$ cat
Hi all,
Would it be worthwhile to add Python as a valid language to the
project() method? Or is it better to use the currently available
FindPython-like scripts.
My reason for asking is that oftentimes you'd like to byte-compile
Python source and install these byte-compiled files along with the
Hello James,
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.
Regards,
Arjen
On 2009-08-18
Zitat von Marcel Loose lo...@astron.nl:
Would it be worthwhile to add Python as a valid language to the
project() method? Or is it better to use the currently available
FindPython-like scripts.
My reason for asking is that oftentimes you'd like to byte-compile
Python source and install these
Ah thanks,
I didn't know that byte code is incompatible between Python releases.
That's definitely a pitfall ;-). I agree that, in that case, it's better
to let the installer handle byte compilation. So, in short, I can do
with the existing FindPython* scripts, I guess?
Thanks for your prompt
If you cache the svn creds on a Mac over an ssh connection, (instead of in
the Mac GUI) then they are stored as on Linux, in a file under the
~/.subversion directory. And then you will not be prompted for future
connections as the same user to the same repository...
(If you already have cached
Speaking of the existing FindPython* scripts they do not support v3.0 yet.
Is there a need to maintain support for picking 2.x if two versions of
python are installed?
On Wed, Aug 19, 2009 at 4:15 AM, Marcel Loose lo...@astron.nl wrote:
Ah thanks,
I didn't know that byte code is incompatible
On 19.08.09 08:34:26, Philip Lowman wrote:
Speaking of the existing FindPython* scripts they do not support v3.0 yet.
Is there a need to maintain support for picking 2.x if two versions of
python are installed?
As Py2 and Py3 are basically incompatible IMHO A separate FindPython3 would
be
Hi Philip,
I guess Python 2.x will be around for some time, before Python 3 really
becomes mainstream. So I think it should be possible to select a 2.x
version, even if 3.x is available.
Best regards,
Marcel Loose.
On Wed, 2009-08-19 at 08:34 -0400, Philip Lowman wrote:
Speaking of the
Hi,
if I execute 'make clean', then all object files of the whole project are
removed.
Now I would like to clean only object files belonging to one target/library, to
force rebuilding this library.
How can I do this?
Best Regards,
Joerg
___
Powered
Another similar approach to try and diagnose the problem would be to
have CMake generate plain Makefiles
http://www.cmake.org/Wiki/CMake:Eclipse_UNIX_Tutorial
Use Option 2 from that tutorial.
You should be able to build your project from the terminal with
Make and from Eclipse. Both
Make sure you reply to the list so others can help you.
On Wed, Aug 19, 2009 at 10:11:02AM +0200, Arnaud Devalkeneer wrote:
In order to undestand how cmake works, I made a simple test.
I simplified the mechanism only using one single file as output and one
single .cdl file as the dependency.
Putting this back on the list.
On Wed, Aug 19, 2009 at 01:55:14PM +0200, Arnaud Devalkeneer wrote:
I just understood the cmake behaviour.
In fact cmake seems to compare last modified times for output and
dependencies.
If the dependencies are younger than the output, the command is triggered.
Tim Kientzle wrote:
Tim Kientzle wrote:
I'm having trouble with a custom target that
depends on another custom target defined in a
subdirectory. Here's a much-simplified version
of what I'm trying to do:
Turns out the subdirectory is a red herring.
Here's a much simpler demonstration of the
You're using incorrect arguments as DEPENDS. Things that follow DEPENDS
should be full path file names... not cmake target names.
HTH,
David
On Wed, Aug 19, 2009 at 11:47 AM, Tim Kientzle kient...@freebsd.org wrote:
Tim Kientzle wrote:
Tim Kientzle wrote:
I'm having trouble with a custom
On Wed, Aug 19, 2009 at 03:12:39PM +0200, Jörg Förstner wrote:
if I execute 'make clean', then all object files of the whole project are
removed.
Now I would like to clean only object files belonging to one target/library,
to force rebuilding this library.
How can I do this?
If you add
Jörg Förstner wrote:
Hi,
if I execute 'make clean', then all object files of the whole project
are removed.
Now I would like to clean only object files belonging to one
target/library, to force rebuilding this library.
How can I do this?
Best Regards,
Joerg
If you are using CMake to
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 can use this to do library-specific
cleaning, provided
Background:
* I am moving from Visual Studio 2008 projects to Cmake in
preparation
for porting our software to Linux.
* We have debug and release versions of 3rdparty libraries to
link
against in two separate paths but under the same name.
On 19. Aug, 2009, at 20:42, aaron.mead...@thomsonreuters.com aaron.mead...@thomsonreuters.com
wrote:
Background:
* I am moving from Visual Studio 2008 projects to Cmake in
preparation
for porting our software to Linux.
* We have debug and release versions of
2009/8/19 aaron.mead...@thomsonreuters.com:
Background:
* I am moving from Visual Studio 2008 projects to Cmake in
preparation
for porting our software to Linux.
* We have debug and release versions of 3rdparty libraries to
link
against in two separate
I had seen that option, which is for a specific library, I was hoping to just
be able to selectively set the library path for a particular configuration.
The current configuration relies heavily on #pragma
comment(lib,libraryname.lib) to automatically build the library link list.
That's
aaron.mead...@thomsonreuters.com wrote:
I had seen that option, which is for a specific library, I was hoping to
just be able to selectively set the library path for a particular
configuration. The current configuration relies heavily on #pragma
comment(lib,libraryname.lib) to automatically
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
C compiler on this system is: cc
C++ compiler on this system is: xlC
Makefile
Hi All,
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.
I've tested it on a number of Unix and Linux systems, including desktops
and clusters, but it would be helpful if someone with
guys i got a recent version of cmake and tried to compile it on HP-UX 11.23
itanium;
basically i saw some -Aa flags, which are used by aCC compiler, and of
course being ignored.
is there any way to pass to the configure script the compiler being used?
aaron.mead...@thomsonreuters.com wrote:
If I understand correctly, you are talking about linking to build
artifacts.
Assuming the above is correct, that wouldn't work for the case I have.
The libraries I'm linking to are not part of the project. (and many
aren't even built by my group.)
No,
Hi Michael. that option is what I am already doing, which is why I am
confused. 'make' from the terminal works great, 'make' from eclipse craps out.
I tried running eclipse from the terminal, and it didnt help.
I noticed something else strange
here is the output from eclipse once I have
Couple more questions just to be clear.
Did you choose to build a Makefile based Eclipse project when you
created your project? If you just selected a C++ project then
eclipse is trying to create its own makefiles for your project.
Are you using an out of source build for your project? For
On Tue, Aug 18, 2009 at 11:05 AM, Pau Garcia i Quiles
pgqui...@elpauer.orgwrote:
On Tue, Aug 18, 2009 at 4:47 PM, James C.
Sutherlandjames.sutherl...@utah.edu wrote:
The new boost libraries (as of version 1.40) will not have all of the
extra
information like compiler info and boost version
Yep, Makefile based project. the project originally came with a Makefile that
didnt do incremental builds, which was driving me nuts, so I figured I would
replace that Makefile with one created by CMake. I just overwrote the
original Makefile with one produced by CMake.
In your example
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 run custom test code without using CTest):
# CMakeLists.txt
32 matches
Mail list logo
