Re: [CMake] Using ExternalProject_Add when CMakeFiles.txt is not in the root directory.
Hello,
David Cole just said the solution in another post.
You can split the project into two, with the first one being just the download
step, the second is the configuration and build. This should allow you to
configure the paths for your project correctly.
I need to do this for my project too. Thanks for the question to get me paying
attention here, and finding the answer is another post :)
Brad
On Jul 14, 2015, at 5:14 PM, Klaim - Joël Lamotte mjkl...@gmail.com wrote:
I am attempting to use ExternalDependencies_Add with the last Protobuf
version (v3.0.0) which is in alpha3 (I'm using the master branch actually)[1].
If you don't already know: contrary to previous Protobuf version, v3.x
provides
cmake scripts (and also makes CMake's FindProtobuf module unusuable if you
build Protobuf using CMake BTW).
I am having trouble figuring out how to ExternalProject_add work in this case:
the CMakeFiles.txt is not in the root directory of Protobuf sources, it is in
./cmake/ [2]
So at build time, after download, I obviously get:
CUSTOMBUILD : CMake error : The source directory blahblah/install_protobuf
does not appear to contain CMakeLists.txt.
I tried several approaches using this as a base:
ExternalProject_Add( install_protobuf
PREFIX ${NETRUSH_DEPENDENCIES_DIR}/protobuf
GIT_REPOSITORY https://github.com/google/protobuf.git
GIT_TAG master
CMAKE_CACHE_ARGS
-DBUILD_TESTING:bool=FALSE
)
I tried setting SOURCE_DIR but failed to make it work mainly because I'm
not sure what value to set exactly, and
SOURCE_DIR cmake
Does not seem to work.
I was wondering if there is some args I could pass to CMake using CMAKE_ARGS
but from the cmake[3] page in the doc I don't see anything that match
exactly, or
I might be misunderstanding something.
I found this recommandation from Miklos Espak from 8th February 2015:
Specify a patch command that creates a toplevel cmake list with one
'add_subdirectory(A)' line.
It seems to work, but it also means that the repository is modified, which is
something
I want to avoid. Also it's really a hack for passing the right working
directory to cmake.
Is there a simpler way to do it that I missed?
Thanks for your time.
Joël Lamotte
[1] https://github.com/google/protobuf
[2] https://github.com/google/protobuf/tree/master/cmake
[3] http://www.cmake.org/cmake/help/v3.3/manual/cmake.1.html#manual:cmake(1)
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CTest + Catch Framework
Hello, This looks a little like google test. For a project I just created a CMake macro which grepped through the test files for the test cases and adds them one by one. Certainly features could be added to better support text fixtures. Hope this gives you some inspiration: https://github.com/SimpleITK/SimpleITK/blob/7aeb952d25c0142e66087edce89e708db2d59a1a/Testing/Unit/CMakeLists.txt#L270-L310 Brad On Jan 27, 2015, at 8:18 AM, David Cole via CMake cmake@cmake.org wrote: It's only a chicken and egg problem if you constrain yourself artificially. When you define a new unit test source file, there are two things you need to do: (1) add it to its executable (2) write an add_test line that invokes that specific unit test You could possibly encapsulate those actions into an add_unit_test macro so that it only seems like you have one thing to do, but certainly, it's possible. You must be doing #1 already, so you just have to make sure #2 always happens whenever #1 happens. Both eggs. D On Mon, Jan 26, 2015 at 4:05 PM, Robert Dailey rcdailey.li...@gmail.com wrote: I believe so, but then you run into the chicken and egg problem: I need to fully build all unit tests in order to know all the test cases, but I need to define the tests at the generation phase (before build). I'm just not sure how to handle this. The best i can think of is to generate 1 test executable per CPP file that we write in our unit tests (generally 1 CPP file per class that is unit tested). Any ideas? On Mon, Jan 26, 2015 at 10:05 AM, David Cole dlrd...@aol.com wrote: Can you run a command that executes one test case at a time, or do you have to run all 50 when you execute the tests for a library? ctest just runs whatever you give it with add_test -- if you want to filter a collection of unit tests to run only a single unit test, then the unit test framework you're using would have to support that. Does Catch allow you to run the tests individually? On Mon, Jan 26, 2015 at 12:30 AM, Robert Dailey rcdailey.li...@gmail.com wrote: Hi, I'm using Catch as my unit test framework: https://github.com/philsquared/Catch Is it possible for CTest to report each TEST_CASE block as an individual test? My understanding is that CTest will only treat each executable as a test. However, my test structure is as follows: 1 library 1 test project Each test project has 1 test CPP file per each class in the library. This way I implement tests for classes in a corresponding CPP file. Each CPP file contains multiple test cases (defined by TEST_CASE macro). The resulting output of `ctest -T Test` shows only 1 test, even though that may be around 50 test cases. I'd like CMake to show the pass/fail status of each one. Is this possible? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Loading Plugins
Hello, Yes, this can be done with ITK's object factory mechanism. I would study how it's done with ITK's ImageIO plugin mechanism[1], then figure out how to adapt the same framework for your interface. Brad [1] http://www.itk.org/Wiki/Plugin_IO_mechanisms On Oct 31, 2014, at 2:20 PM, Aaron Boxer boxe...@gmail.com wrote: Hello! I have a C CMake project, and I would like to add the following feature: 1) define an interface for a second dynamic library 2) look in a specified folder at runtime, and try to load this library 3) if loading fails, then get notified of this fact, so that I can use statically linked fall-back routines in the parent project. Is this possible? Any ideas or advice would be greatly appreciated. Thanks, Aaron -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] [ITK-dev] find_package issues with ITK and VTK (and SlicerExecution Model)
Brad,
Do you have a suggestion on how to conditionally include a module if it's
available? e.g. Use ITKDeprecated if ITK was configure with it?
Thanks,
Brad
On Sep 30, 2014, at 10:48 AM, Brad King brad.k...@kitware.com wrote:
On 09/30/2014 10:14 AM, Williams, Norman K wrote:
find_package(VTK REQUIRED)
find_package(ITK REQUIRED)
You can’t real compile anything that needs VTK, because down in
the ITK deployment stuff, it calls find_package(VTK) like this:
[snip]
Which blows away the larger list of include directories and libraries
One may use the itk_module_config and vtk_module_config macros
from the *ModuleAPI.cmake modules that come with the respective
packages to compute the list of libraries and include dirs for
a given list of components. All ITKConfig and VTKConfig do with
the list of components is:
itk_module_config(ITK ${ITK_MODULES_REQUESTED})
# sets ITK_LIBRARIES, ITK_INCLUDE_DIRS, etc.
and
vtk_module_config(VTK ${VTK_MODULES_REQUESTED})
# sets VTK_LIBRARIES, VTK_INCLUDE_DIRS, etc.
One can invoke these directly:
itk_module_config(ITK ${MY_LIST_OF_ITK_COMPONENTS})
vtk_module_config(VTK ${MY_LIST_OF_VTK_COMPONENTS})
at any time after the find_package calls. One could even use
a different prefix:
itk_module_config(MyITK ${MY_LIST_OF_ITK_COMPONENTS})
# sets MyITK_LIBRARIES, MyITK_INCLUDE_DIRS, etc.
In the long run the plan is to stop recommending use of component
lists at find_package time and instead use imported targets and
usage requirements:
http://www.cmake.org/cmake/help/v3.0/manual/cmake-buildsystem.7.html#build-specification-and-usage-requirements
but that will have to wait until we can require CMake 3.0.
-Brad
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Kitware offers ITK Training Courses, for more information visit:
http://kitware.com/products/protraining.php
Please keep messages on-topic and check the ITK FAQ at:
http://www.itk.org/Wiki/ITK_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/insight-developers
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
[CMake] Install CMake3.0 as alternate
Hello, Is there a way I can configure CMake when I build it so it's executable with have a 3 or 3.0 suffix, so that I can easily have multiple version of cmake installed into /usr/local? I am looking for something similar to python's altinstall or gcc's program-suffix option. Thanks, Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Building Matlab Mex extensions that link to ITK?
Kent,
It appears that you are trying to link of all of ITK. SimpleITK ITK took the
approach of producing a library that fully encapsulates ITK. So that a single
shared library could be produced and not depend on ITK. While you could use
SimpleITK's library and try to use the infrastructure to customize if for you
needs. I doubt that is what you need... ( But it'd be very cool IMO ).
What you may consider is compiling ITK as static and creating a facade
interface which only exposes your code and methods you need. This facade
interface would be compiled into a self contained shared library. So you only
need to link the mex stuff to this library and not all of ITK. Hence just
simplify the process by encapsulating ITK.
If you want any further info just let me know.
Brad
On Nov 19, 2013, at 12:59 PM, Williams, Norman K
norman-k-willi...@uiowa.edu wrote:
Has anyone else come up with an elegant solution for this?
If I want to call ITK from a Matlab MEX extension written in C++, I run
into problems with telling it the libraries with which to link.
The ITK_LIBRARIES variable is a list of imported library targets which
CMake converts to actual library paths when it links a library or
executable.
But to compile a MEX file, we're using a custom command along the lines of
add_custom_command(OUTPUT ${MEX_PREFIX}.${MATLAB_MEX_EXT}
COMMAND ${MATLAB_MEX_PATH} -cxx
${CMAKE_CXX_FLAGS_Release} ${MEX_SRC_PATH}
${ITK_INCLUDES} ${ITK_LIBRARIES}
-I${Teem_INCLUDE_DIR} -L${Teem_LIBRARY_DIR} -lteem
${ZLIB_LIBRARY}
DEPENDS ${MEX_SRC_PATH}
IMPLICIT_DEPENDS C ${MEX_SRC_PATH}
COMMENT BUILDING MEX_FILE: ${MEX_SRC_PATH} )
But that doesn't work because CMake gives the target names in
ITK_LIBRARIES instead of the actual libraries.
I tried this:
find_package(ITK NO_MODULE REQUIRED)
include(${ITK_USE_FILE})
set(ITK_LOCAL_LIBS)
foreach(lib ${ITK_LIBRARIES})
get_target_property(_lib ${lib} IMPORTED_LOCATION)
list(APPEND ITK_LOCAL_LIBS ${_lib})endforeach()
But all the IMPORTED_LOCATION for ITK libraries is _lib-NOTFOUND
--
Kent Williams norman-k-willi...@uiowa.edu
Notice: This UI Health Care e-mail (including attachments) is covered by the
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential
and may be legally privileged. If you are not the intended recipient, you
are hereby notified that any retention, dissemination, distribution, or
copying of this communication is strictly prohibited. Please reply to the
sender that you have received the message in error, then delete it. Thank
you.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] C# and cmake ?
Hello Gerhard, With the SimpleITK project I am working on we are using C#, SWIG and a lot of C++ ( along with a variety of other languages). We are using Swig to generate C# libraries, and compile a large number of C# executables to test our interface. We have quite a bit of CMake code, but I hope that you'll be able to wade through it to find the bits you may need. Here is a summary of some of the interesting bits that you may find useful: CMake Find and Use files: https://github.com/SimpleITK/SimpleITK/blob/master/CMake/FindCSharp.cmake https://github.com/SimpleITK/SimpleITK/blob/master/CMake/UseCSharp.cmake https://github.com/SimpleITK/SimpleITK/blob/master/CMake/FindMono.cmake https://github.com/SimpleITK/SimpleITK/blob/master/CMake/UseMono.cmake Here is macro we use for testing: https://github.com/SimpleITK/SimpleITK/blob/master/Testing/Unit/CMakeLists.txt#L326 And here is the code that we use to run SWIG and generate the managed library: https://github.com/SimpleITK/SimpleITK/blob/master/Wrapping/CMakeLists.txt#L206 Most of the CMake code has been contributed by another developer, so I am not an expert of C#. While this is a rather complicated build process, it may give an indication of what would be needed for cmake to build the C# targets. Hope this helps, Brad On Aug 22, 2012, at 7:03 AM, Gerhard den Hollander wrote: We have a large code base, that consists of a large number of C++ file and a smaller number of C# files. Most fo the C++ code is being build using CMake, the C# code is build using the msbuild tools. I know that currently there is no C# support planned in CMake, but reading through the google results, it sounds like people have had various degrees of success using custom_command(..) or other CMake tricks to kick of C# builds using msbuild/devenv. For those who have succesfully build mixed code projects (so C# and C/C++ ), would you mind explainign how this is done ? Preferably with some example CMake files ? Thanks -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake Bradley Lowekamp Medical Science and Computing for Office of High Performance Computing and Communications National Library of Medicine blowek...@mail.nih.gov -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Running Python unit tests importing modules built in CMake
Hello, For testing python another alternative is to create a python virtual environment and install you python package into that. Here is an example of how I have done that: https://github.com/SimpleITK/SimpleITK/blob/master/Wrapping/CMakeLists.txt#L97 Brad On May 2, 2012, at 9:26 PM, David Cole wrote: Are you using add_test to add the tests in the CMakeLists file? If so, you can set the test ENVIRONMENT property to set PYTHONPATH when ctest executes the test. See property doc here: http://cmake.org/cmake/help/v2.8.8/cmake.html#prop_test:ENVIRONMENT On Wed, May 2, 2012 at 5:17 PM, Lori A. Pritchett-Sheats lpri...@lanl.gov wrote: I'm building Python modules using SWIG and CMake, and have run into a problem running Python unit tests for these built modules. I can not find a slick way to set the Python module search path when running the test. The usual trick of setting sys.path in the scripts will not work here because I don't know the location of the build directory. I've tried updating PYTHONPATH in my CMakeList.txt file but that change isn't picked up when the test is executed. I could create the unit test modules at build time using CONFIGURE_FILE replacing @CMAKE_CURRENT_BINARY_DIR@ in a sys.path line, but that seems heavy-handed. Has anyone else run into this problem and found better a solution? -- Lori A. Pritchett-Sheats, PhD. CCS-2, Computational Physics and Methods Office: 505-665-6675 Fax: 505-665-4972 Los Alamos National Laboratory P.O. Box 1663 MS D413 Los Alamos, NM 87544 -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake Bradley Lowekamp Medical Science and Computing for Office of High Performance Computing and Communications National Library of Medicine blowek...@mail.nih.gov -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Zero coverage being reported on gcc/Linux builds.
Great!
These look like the important lines to fix my coverage issue with Superbuilds:
# HACK Unfortunately ctest_coverage ignores the BUILD argument, try to
force it...
file(READ ${slicer_build_dir}/CMakeFiles/TargetDirectories.txt
slicer_build_coverage_dirs)
file(APPEND ${CTEST_BINARY_DIRECTORY}/CMakeFiles/TargetDirectories.txt
${slicer_build_coverage_dirs})
Thanks,
Brad
On Apr 25, 2012, at 12:45 PM, Jean-Christophe Fillion-Robin wrote:
Hi Brad,
Consider looking at
https://github.com/Slicer/Slicer/blob/master/CMake/SlicerDashboardDriverScript.cmake#L246
Hth
Jc
On Tue, Apr 24, 2012 at 9:13 AM, Bradley Lowekamp blowek...@mail.nih.gov
wrote:
Hello,
Are both of these project using SuperBuilds?
I know with SimpleITK I was unable to get coverage to work in the SuperBuild
structure. To get coverage we are doing the project, with its self not being
an ExternalProject. However, valgrind works just fine in the Superbuild
structure. I didn't see nightly build scripts attached to the ANTS or BRAIN
project so I am only guessing here.
Brad
On Apr 24, 2012, at 7:32 AM, David Cole wrote:
Ugh. You're probably doing everything right, and there's just a bug of some
sort. Unfortunately, debugging these things is neither easy nor fun.
First, look for Coverage*.log files in the Testing/ subdirectories of your
build tree. Are there any errors mentioned in there?
Next, verify that there are some *.gcda files in the build tree:
find . -name *.gcda
There is a known/reported issue with the coverage not reporting correctly
right now for gcc 4.7, but this is the first problem I've heard of with an
earlier gcc...
http://public.kitware.com/Bug/view.php?id=13121
On Mon, Apr 23, 2012 at 5:18 PM, Kent Williams nkwmailingli...@gmail.com
wrote:
cmake: 2.8.6
gcc/g++: 4.4.6-3
Red Hate Enterprise Linux 6.2
I follow the instructions here: http://www.cmake.org/Wiki/CTest/Coverage
And I have 2 different dashboards that report zero coverage:
http://testing.psychiatry.uiowa.edu/CDash/index.php?project=BRAINSStandalone
http://testing.psychiatry.uiowa.edu/CDash/index.php?project=ANTS
I don't know what's going on because I remember coverage working, and
it's obviously doing something for other projects, e.g. ITK:
http://public.kitware.com/dashboard.php?name=itk
Call me an idiot, but I can follow instructions, and following the
instructions I can find isn't doing the trick.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Bradley Lowekamp
Medical Science and Computing for
Office of High Performance Computing and Communications
National Library of Medicine
blowek...@mail.nih.gov
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
+1 919 869 8849
Bradley Lowekamp
Medical Science and Computing for
Office of High Performance Computing and Communications
National Library of Medicine
blowek...@mail.nih.gov
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Zero coverage being reported on gcc/Linux builds.
Hello, Are both of these project using SuperBuilds? I know with SimpleITK I was unable to get coverage to work in the SuperBuild structure. To get coverage we are doing the project, with its self not being an ExternalProject. However, valgrind works just fine in the Superbuild structure. I didn't see nightly build scripts attached to the ANTS or BRAIN project so I am only guessing here. Brad On Apr 24, 2012, at 7:32 AM, David Cole wrote: Ugh. You're probably doing everything right, and there's just a bug of some sort. Unfortunately, debugging these things is neither easy nor fun. First, look for Coverage*.log files in the Testing/ subdirectories of your build tree. Are there any errors mentioned in there? Next, verify that there are some *.gcda files in the build tree: find . -name *.gcda There is a known/reported issue with the coverage not reporting correctly right now for gcc 4.7, but this is the first problem I've heard of with an earlier gcc... http://public.kitware.com/Bug/view.php?id=13121 On Mon, Apr 23, 2012 at 5:18 PM, Kent Williams nkwmailingli...@gmail.com wrote: cmake: 2.8.6 gcc/g++: 4.4.6-3 Red Hate Enterprise Linux 6.2 I follow the instructions here: http://www.cmake.org/Wiki/CTest/Coverage And I have 2 different dashboards that report zero coverage: http://testing.psychiatry.uiowa.edu/CDash/index.php?project=BRAINSStandalone http://testing.psychiatry.uiowa.edu/CDash/index.php?project=ANTS I don't know what's going on because I remember coverage working, and it's obviously doing something for other projects, e.g. ITK: http://public.kitware.com/dashboard.php?name=itk Call me an idiot, but I can follow instructions, and following the instructions I can find isn't doing the trick. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake Bradley Lowekamp Medical Science and Computing for Office of High Performance Computing and Communications National Library of Medicine blowek...@mail.nih.gov -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Problem after upgrading to OSX 10.6.3!
Hello, The down arrow (and other arrow keys) is no longer working after I patched to OSX 10.6.3 with ccmake. This is very weird! Other applications seems fine. I have tried 3 upgraded machines, all failing to get curser to move with the down arrow to move to the next variable (2.8 local build, ~2.9.20100222 local build, 2.8 released binary). I tried 2 that were 10.6.2 and then worked fine (2.8 local build)! I then tried using Terminal on 10.6.3, but sshing into a 10.6.2. This time the down arrow worked! Also we just built 2.8.1 release, and the same thing is occurring... Brad Bradley Lowekamp Lockheed Martin Contractor for Office of High Performance Computing and Communications National Library of Medicine blowek...@mail.nih.gov ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problem after upgrading to OSX 10.6.3!
Hello, Fortunately the emacs bindings still work: C-p (previous line) C-n (next line) C-f (forward) C-b (back) Brad On Mar 31, 2010, at 2:03 PM, Lowekamp, Bradley (NIH/NLM/LHC) [C] wrote: Hello, The down arrow (and other arrow keys) is no longer working after I patched to OSX 10.6.3 with ccmake. This is very weird! Other applications seems fine. I have tried 3 upgraded machines, all failing to get curser to move with the down arrow to move to the next variable (2.8 local build, ~2.9.20100222 local build, 2.8 released binary). I tried 2 that were 10.6.2 and then worked fine (2.8 local build)! I then tried using Terminal on 10.6.3, but sshing into a 10.6.2. This time the down arrow worked! Also we just built 2.8.1 release, and the same thing is occurring... Brad Bradley Lowekamp Lockheed Martin Contractor for Office of High Performance Computing and Communications National Library of Medicine blowek...@mail.nih.gov ATT1..txt Bradley Lowekamp Lockheed Martin Contractor for Office of High Performance Computing and Communications National Library of Medicine blowek...@mail.nih.gov ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Problem with QtTest Bundle Utility Example?
) QtCore.framework/Versions/4/QtCore (compatibility version 4.6.0, current version 4.6.2) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 103.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.0.0) Any thoughts or suggestions, before I dive too deep into GetPrerequisites.cmake? Thanks, Brad Bradley Lowekamp Lockheed Martin Contractor for Office of High Performance Computing and Communications National Library of Medicine blowek...@mail.nih.gov ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problem with QtTest Bundle Utility Example?
Thanks for the prompt answer. This looks like a quick fix.
The other problem I narrowed down (the actual reason the QTest.app failed to
launch) is that the Cocoa build requires Resources that are not copied. So it's
exiting with the following error:
Qt internal error: qt_menu.nib could not be loaded. The .nib file should be
placed in QtGui.framework/Versions/Current/Resources/ or in the resources
directory of your application bundle.
Abort trap
Which makes me really wonder if this bundle utility is ready for prime time?
Brad
On Mar 12, 2010, at 3:43 PM, Michael Jackson wrote:
I had to over-load the gp_item_default_embedded_path_override CMake
function with the following:
# gp_item_default_embedded_path item default_embedded_path_var
#
# Return the path that others should refer to the item by when the item
# is embedded inside a bundle.
#
# Override on a per-project basis by providing a project-specific
# gp_item_default_embedded_path_override function.
#
function(gp_item_default_embedded_path_override item
default_embedded_path_var)
#
# The assumption here is that all executables in the bundle will be
# in same-level-directories inside the bundle. The parent directory
# of an executable inside the bundle should be MacOS or a sibling of
# MacOS and all embedded paths returned from here will begin with
# @executable_path/../ and will work from all executables in all
# such same-level-directories inside the bundle.
#
# By default, embed things right next to the main bundle executable:
#
set(path @executable_path/../../Contents/MacOS)
set(overridden 0)
# For Qt Based Plugins for the image formats, the plugins MUST
reside in
# the PlugIns/imageformats directory. Since THIS particular
project ONLY has
# the Qt Frameworks AND the plugins the below regex will suffice to
separate
# them from each other. On other projects we could use better logic
to
# put things where they go. Maybe using some configured CMake
List of libraries
# then looking through each list for the currect library being
fixed up.
# Embed .dylibs right next to the main bundle executable:
#
if(item MATCHES \\.dylib$)
set(path @executable_path/../PlugIns/imageformats)
set(overridden 1)
endif(item MATCHES \\.dylib$)
# Embed .so right next to the main bundle executable:
#
if(item MATCHES \\.so$)
set(path @executable_path/../Plugins/imageformats)
set(overridden 1)
endif(item MATCHES \\.so$)
# Embed frameworks in the embedded Frameworks directory (sibling
of MacOS):
#
if(NOT overridden)
if(item MATCHES [^/]+\\.framework/)
set(path @executable_path/../Frameworks)
set(overridden 1)
endif(item MATCHES [^/]+\\.framework/)
endif(NOT overridden)
set(${default_embedded_path_var} ${path} PARENT_SCOPE)
endfunction(gp_item_default_embedded_path_override)
Which is a complete hack (as it does not take into account other types
of plugins) but worked for my limited Application bundle.
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton, Ohio
On Mar 12, 2010, at 3:20 PM, Bradley Lowekamp wrote:
Hello,
I am trying run the QtTest-Package-Example from:
http://www.vtk.org/Wiki/BundleUtilitiesExample
and I am getting some errors on install.
I am running CMake 2.8, with Qt 4.6.2 Cocoa universal, on OSX 10.6.2.
During the fixup_bundle phase I am getting some error message and
some undesired behavior. It appears the qt plugin libraries are
problematic. Here is snipits of the output:
- Install configuration:
-- Installing: ~/Downloads/QtTest/./install/./QtTest.app
-- Installing: ~/Downloads/QtTest/./install/./QtTest.app/Contents
-- Installing: ~/Downloads/QtTest/./install/./QtTest.app/Contents/
Info.plist
-- Installing: ~/Downloads/QtTest/./install/./QtTest.app/Contents/
MacOS
-- Installing: ~/Downloads/QtTest/./install/./QtTest.app/Contents/
MacOS/QtTest
-- Installing: ~/Downloads/QtTest/./install/./QtTest.app/Contents/
Resources
-- Installing: ~/Downloads/QtTest/./install/./QtTest.app/Contents/
Resources/QtTest.icns
-- Installing: ~/Downloads/QtTest/./install/QtTest.app/Contents/
MacOS/plugins/imageformats
-- Installing: ~/Downloads/QtTest/./install/QtTest.app/Contents/
MacOS/plugins/imageformats/libqgif.dylib
-- Installing: ~/Downloads/QtTest/./install/QtTest.app/Contents/
MacOS/plugins/imageformats/libqico.dylib
-- Installing: ~/Downloads/QtTest/./install/QtTest.app/Contents/
MacOS/plugins/imageformats/libqjpeg.dylib
-- Installing: ~/Downloads/QtTest/./install/QtTest.app/Contents/
MacOS/plugins/imageformats/libqmng.dylib
-- Installing: ~/Downloads/QtTest/./install/QtTest.app/Contents/
MacOS/plugins/imageformats/libqsvg.dylib
-- Installing
Re: [CMake] Intel Compiler with OSX 10.6
What I don't understand is how the different files in the Platform's directory work. There appease to be an OS, compiler, and OS-compiler. As the intel compiler icc and icpc tries to emulate gcc, g++ respectfully on both the mac and linux, I would think that it may make since for there to be a icc.cmake file which takes care of them both. Is there documentation (or readable source code) which could help me understand how things in this directory work? Thanks, Brad On Dec 1, 2009, at 4:34 PM, Michael Jackson wrote: I think I wrote part of that file. Didn't realize I was putting any OS X 10.4 specific items in there. Any ways, I don't have access to ICC anymore so you will probably have to experiment with some settings and then update the darwin-icc.cmake files. Sorry I can not be of any more help. _ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Softwarewww.bluequartz.net Principal Software Engineer Dayton, Ohio On Dec 1, 2009, at 3:46 PM, Bradley Lowekamp wrote: Hello, It appear the following file is out of date: CMake/Modules/Platform/Darwin-icc.cmake I have just starting using the Intel Compiler on my apple. It appear that this file is very 10.4 specific, in that it does not set a lot of variable unless we are running 10.4. Specifically I noticed that I am not getting any optimization or debug compiler flags. I built a quick experimental build, which makes me think that things are functioning: http://www.cdash.org/CDash/buildSummary.php?buildid=483919 I am not familiar with these platform configuration files, nor the details of the differences of OS X compilers as I have always just let cmake handle it :) Any help would be appreciated. Brad Bradley Lowekamp Lockheed Martin Contractor for Office of High Performance Computing and Communications National Library of Medicine blowek...@mail.nih.gov ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Intel Compiler with OSX 10.6
Hello, It appear the following file is out of date: CMake/Modules/Platform/Darwin-icc.cmake I have just starting using the Intel Compiler on my apple. It appear that this file is very 10.4 specific, in that it does not set a lot of variable unless we are running 10.4. Specifically I noticed that I am not getting any optimization or debug compiler flags. I built a quick experimental build, which makes me think that things are functioning: http://www.cdash.org/CDash/buildSummary.php?buildid=483919 I am not familiar with these platform configuration files, nor the details of the differences of OS X compilers as I have always just let cmake handle it :) Any help would be appreciated. Brad Bradley Lowekamp Lockheed Martin Contractor for Office of High Performance Computing and Communications National Library of Medicine blowek...@mail.nih.gov ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
