On 8/2/2011 3:40 AM, Stephen Kelly wrote:
Brad King wrote:
I've now also tested with MSVC and MinGW on Windows. I couldn't seem to get
cmake to work on cygwin though.
I'll see if I can test on Mac too before pushing to the cmake repo.
One question I have is: Will the unit tests for this be run
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12381
==
Reported By:Sean McBride
Assigned To:
Hi,
FindDevIL.cmake module seems to be looking for il.h header instead of
IL/il.h. This way, user should be writing
#include il.h
instead of
#include IL/il.h
in his code. Note that the latter version is used with all examples in
DevIL library. Also libraries like OpenGL use the latter format.
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12382
==
Reported By:Gregory Crosswhite
Assigned To:
Hello,
I'm trying to understand how my C++ application can be compiled using CMake.
Actually, there is an include file (foo.h) which contains this line
boost::shared_ptrimp _p;
but which doesn't contain #include boost/shared_ptr.hpp.
I can't see any include or source file in my application
Hello,
I want to do the separation between .hpp and .inl in my Visual project.
Is there a command CMake to create sub folder in the project and
organize my files ?
Thanks
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
See source_group command
On Aug 2, 2011 12:51 PM, Julien Dardenne julien.darde...@technooliq.com
wrote:
**
Hello,
I want to do the separation between .hpp and .inl in my Visual project.
Is there a command CMake to create sub folder in the project and organize my
files ?
Thanks
Hello,
Have a look there:
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:file
especially the
file(MAKE_DIRECTORY [directory1 directory2 ...])
file command version
Regards,
Camille
De : Julien Dardenne julien.darde...@technooliq.com
À :
On Mon, Aug 1, 2011 at 8:34 PM, John R. Cary c...@txcorp.com wrote:
I believe I have followed what I have found on the web for
building a Win64 version of CMake. I have downloaded the
win32 version and used it to configure the cmake source.
I used the Visual Studio 9 2008 Win64 generator.
On Tue, Aug 2, 2011 at 7:00 AM, David Cole david.c...@kitware.com wrote:
On Mon, Aug 1, 2011 at 8:34 PM, John R. Cary c...@txcorp.com wrote:
I believe I have followed what I have found on the web for
building a Win64 version of CMake. I have downloaded the
win32 version and used it to
On Mon, Aug 1, 2011 at 5:59 PM, Sascha Zelzer
s.zel...@dkfz-heidelberg.de wrote:
Hi,
I played around with the ExternalProject unit tests and was able to
reproduce my problem with the current HEAD ExternalProjects.cmake file. It
boils down to *not* adding the UPDATE_COMMAND line:
1.) In
Thanks for your response. This will definitely decrease my headpain.
It turns out that I need vtk-5.0.0, but right now I am not sure
that I need the wrapping code. Am checking on this.
Would it make sense to just not call vtkLoadCMakeExtensions.cmake?
ThxJohn Cary
On 8/2/11 5:00 AM,
Try commenting out the one line that causes problems, then back up
from there, either commenting chunks out or adjusting CMake options
until those commands are not loaded.
On Tue, Aug 2, 2011 at 8:50 AM, John R. Cary c...@txcorp.com wrote:
Thanks for your response. This will definitely
On 8/2/2011 9:42 AM, David Cole wrote:
Try commenting out the one line that causes problems, then back up
from there, either commenting chunks out or adjusting CMake options
until those commands are not loaded.
That said, if CMake is built with the same options as you are building
VTK with,
On 08/01/2011 07:13 PM, The Novice Coder wrote:
The short version of what I'm trying to do:
Add some kind of definition to the cmake file that specifies a file,
that if modified, will cause the project to be regenerated.
Longer (more specific) version.
We (our small program team)
Within CTK,
Where we are specifying a specific SHA1, we could set UPDATE_COMMAND to be
Where we are specifying a branch like origin/master, this is were the
problem occurs. I guess we could also specify a given SHA1. This will
prevent the external project to be a moving target and will ensure
Previously with cmake 2.8.4 we were using these lines to compile an assembly
language file in our project:
if(UNIX)
enable_language(ASM)
# see if we are building 32-bit or 64-bit executables
file(WRITE ${CMAKE_BINARY_DIR}/check_32or64bit.cpp int main(int argc,
char *argv[]) { return 8 *
On Monday, August 01, 2011 07:12:15 pm Gregory Crosswhite wrote:
Hey everyone,
I am using CMake to build a package which has the normal unix layout,
i.e. programs are in bin/, libraries are in lib/, etc., and I would like
to simply copy all of the required shared non-system libraries into
On 8/2/11 9:28 AM, Clinton Stimpson wrote:
You shouldn't need to copy GetPrerequisites and BundleUtilities.
For Linux you can do:
set_target_properties( ... PROPERTIES INSTALL_RPATH \$ORIGIN/../lib)
To get/usr/lib/ to be treated as non-system libraries, you can implement
On 8/2/11 9:28 AM, Clinton Stimpson wrote:
You shouldn't need to copy GetPrerequisites and BundleUtilities.
For Linux you can do:
set_target_properties( ... PROPERTIES INSTALL_RPATH \$ORIGIN/../lib)
To get /usr/lib/ to be treated as non-system libraries, you can implement
On Tue, Aug 2, 2011 at 3:42 PM, Gregory Crosswhite
gcrosswh...@gmail.com wrote:
On 8/2/11 9:28 AM, Clinton Stimpson wrote:
You shouldn't need to copy GetPrerequisites and BundleUtilities.
For Linux you can do:
set_target_properties( ... PROPERTIES INSTALL_RPATH \$ORIGIN/../lib)
To get
On Tuesday, August 02, 2011 01:42:47 pm Gregory Crosswhite wrote:
On 8/2/11 9:28 AM, Clinton Stimpson wrote:
You shouldn't need to copy GetPrerequisites and BundleUtilities.
For Linux you can do:
set_target_properties( ... PROPERTIES INSTALL_RPATH \$ORIGIN/../lib)
To get /usr/lib/
On 8/2/11 12:47 PM, David Cole wrote:
The non .app dir problem should go away if you use the recently
released CMake 2.8.5. This bug was fixed in that version:
http://public.kitware.com/Bug/view.php?id=12034
Thank you very much for the heads up, but I have already been running
CMake 2.8.5
On 8/2/11 12:53 PM, Clinton Stimpson wrote:
On Mac, are you making a .app bundle, or are you doing a layout similar to
Linux, with bin/, lib/ layout, or something else?
The latter --- I was hoping to use a layout similar to Linux with bin/,
lib/, etc. since the program is console-based and so
On Tuesday, August 02, 2011 02:03:23 pm Gregory Crosswhite wrote:
On 8/2/11 12:53 PM, Clinton Stimpson wrote:
On Mac, are you making a .app bundle, or are you doing a layout similar
to Linux, with bin/, lib/ layout, or something else?
The latter --- I was hoping to use a layout similar to
Hi,
On Tuesday 02 August 2011, Glenn Coombs wrote:
Previously with cmake 2.8.4 we were using these lines to compile an
with 2.8.5 there was a major rework of the assembler support (and now it
finally does not say Assembler support is experimental anymore).
Sorry that this causes inconvenience
On 08/02/2011 01:28 PM, David Cole wrote:
Thanks for this info... I've reproduced the problem now, too. I'm not
sure what to do about it yet, but I can make it happen: that's the
first step toward a fix.
There should not be a need for an update step if you're snapped to
particular hash or
Hi,
I agree with JC and will move the CTK discussion to the ctk-developers list.
Thanks,
Sascha
On 08/02/2011 05:21 PM, Jean-Christophe Fillion-Robin wrote:
Within CTK,
Where we are specifying a specific SHA1, we could set UPDATE_COMMAND
to be
Where we are specifying a branch like
Am Dienstag, 2. August 2011, 21:55:16 schrieb Alexander Neundorf:
Hi,
until recently, I recommended to install Config.cmake files more or less
like this:
install(FILES FooConfig.cmake DESTINATION lib${LIB_SUFFIX}/cmake/Foo )
with LIB_SUFFIX being 64 on systems where this is required.
On Tuesday, August 02, 2011 05:09:04 pm Gregory Crosswhite wrote:
On 08/02/2011 03:10 PM, Clinton Stimpson wrote:
On Tuesday, August 02, 2011 03:38:01 pm Gregory Crosswhite wrote:
You need an @ONLY for configure_file() so it doesn't substitute the ${}
parts also.
Doh! Thanks for the
On 8/2/11 4:32 PM, Clinton Stimpson wrote:
There is no scanning the file system to find which libraries to fix up.
Any libraries used by executables will be considered in the set of libraries
to fix up, regardless of where they are installed (in bin/ or lib/). Any
libraries not found as a
On Aug 2, 2011, at 5:47 PM, Gregory Crosswhite wrote:
On 8/2/11 4:32 PM, Clinton Stimpson wrote:
There is no scanning the file system to find which libraries to fix up.
Any libraries used by executables will be considered in the set of libraries
to fix up, regardless of where they are
On Tue, Aug 2, 2011 at 8:05 PM, Clinton Stimpson clin...@elemtech.com wrote:
On Aug 2, 2011, at 5:47 PM, Gregory Crosswhite wrote:
On 8/2/11 4:32 PM, Clinton Stimpson wrote:
There is no scanning the file system to find which libraries to fix up.
Any libraries used by executables will be
On 08/02/2011 05:36 PM, David Cole wrote:
When you do not have a .app directory, and you are not copying into
the same directory with the executable, then the question in my mind
becomes what exactly is 'the bundle' at this point?
With a dir/bin, dir/lib typical Linux style layout, dir would
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 9f4a135dc1050d2f01f222d1ea418882a196b7b1 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 2c7b38afa6e941166501dfed47e6b22b1847b9ab (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via c6051b7abd093707ad3779a9a29cbf772355e8f5 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via be3ac14ac707b4d2973ca9854450b849c0968e83 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 39faba7e30151a6c884d2ec38932235223b9821d (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 2444d6f55eb0e66893c0e86b10e466ceaae32e31 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 996eb5036458338371acb22b7ac25e88d5f9f0f8 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 7ef2f53d02869c397ca1555781c3661a7519a9dc (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 86bae62bd1a3369a1487887392d22be39530a2bd (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 330577ce875568bc0906ac08cd6c2a638ab503eb (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 782488596062649703919066cd1a84f05fd24e18 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via abc85867169a92f189d6378e95d062f24aa1bd93 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via e9a6d86d91451468e4a4bf52e8cd23199362bffa (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 11ca173731a73b9635a0ebc2a16e116931e9de7a (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via bd54141d5d098899afa36c6326811eb2230e99cf (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 737be8f6f65007bcc8cd3fa6d72288264d05e1ba (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 6a117271545d40b7d9615e840ba89d959e0b758d (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 80ef23d83fbf534bb3488db69a284fedf2be17e4 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 74e4e16c8a194e53d5c3edac8503a45c4f2a (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via a94b306697605418e0ac2a54da2ebd538c9ac72d (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 14e54c4c449e2704799ab5283c6c6764472d5a0a (commit)
from
55 matches
Mail list logo
