Re: [CMake] CTest extra tests
> On Mar 20, 2018, at 9:45 AM, Bill Hoffman <bill.hoff...@kitware.com> wrote:
>
> Must be coming from some macro, cmake does not automatically add any tests.
> You could run cmake --trace and look at the output and find out where the
> add_test call is coming from.
Thanks, that was it!
The create_single_source_cgal_program() macro was the culprit.
Thanks for the pointer to cmake --trace
>
> On Sun, Mar 18, 2018 at 5:39 PM, Adam Getchell <adam.getch...@gmail.com
> <mailto:adam.getch...@gmail.com>> wrote:
> Hello all,
>
> I’m running into unexpected behavior when using CTest.
>
> First, I define the list of tests that I want to run in my CMakeLists.txt:
>
> https://github.com/acgetchell/CDT-plusplus/blob/develop/CMakeLists.txt#L151
> <https://github.com/acgetchell/CDT-plusplus/blob/develop/CMakeLists.txt#L151>
>
> However, it generates two extra tests:
>
> ┌─[adam][hapkido][±][develop {1} ✓][~/CDT-plusplus/build]
> └─▪ ctest -N
> Test project /Users/adam/CDT-plusplus/build
> Test #1: cdt-gv
> Test #2: build_target_cdt-gv
> Test #3: CDT-Usage
> Test #4: CDT-3Donly
> Test #5: CDT-Simplices
> Test #6: CDT-Timeslices
> Test #7: CDT-3Dtriangle
> Test #8: CDT-MinimalS3
> Test #9: CDT-S3Runs
> Test #10: CDT-unit-tests
>
> Total Tests: 10
>
> I’d like to get rid of these first two autogenerated tests, because #1 fails.
> Where/how are these being generated/defined?
>
> I’m aware that I can just filter using ctest -E, but I’d like to make it easy
> for the other contributors (and my CI) by making `ctest` just work.
>
> Thanks for any pointers.
>
> Cheers,
> Adam
> --
> Adam Getchell
> https://keybase.io/adamgetchell <https://keybase.io/adamgetchell>
>
> --
>
> Powered by www.kitware.com <http://www.kitware.com/>
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ <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
> <http://cmake.org/cmake/help/support.html>
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> <http://cmake.org/cmake/help/consulting.html>
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> <http://cmake.org/cmake/help/training.html>
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> <http://www.kitware.com/opensource/opensource.html>
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
> <https://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:
https://cmake.org/mailman/listinfo/cmake
[CMake] CTest extra tests
Hello all,
I’m running into unexpected behavior when using CTest.
First, I define the list of tests that I want to run in my CMakeLists.txt:
https://github.com/acgetchell/CDT-plusplus/blob/develop/CMakeLists.txt#L151
<https://github.com/acgetchell/CDT-plusplus/blob/develop/CMakeLists.txt#L151>
However, it generates two extra tests:
┌─[adam][hapkido][±][develop {1} ✓][~/CDT-plusplus/build]
└─▪ ctest -N
Test project /Users/adam/CDT-plusplus/build
Test #1: cdt-gv
Test #2: build_target_cdt-gv
Test #3: CDT-Usage
Test #4: CDT-3Donly
Test #5: CDT-Simplices
Test #6: CDT-Timeslices
Test #7: CDT-3Dtriangle
Test #8: CDT-MinimalS3
Test #9: CDT-S3Runs
Test #10: CDT-unit-tests
Total Tests: 10
I’d like to get rid of these first two autogenerated tests, because #1 fails.
Where/how are these being generated/defined?
I’m aware that I can just filter using ctest -E, but I’d like to make it easy
for the other contributors (and my CI) by making `ctest` just work.
Thanks for any pointers.
Cheers,
Adam
--
Adam Getchell
https://keybase.io/adamgetchell
--
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:
https://cmake.org/mailman/listinfo/cmake
Re: [CMake] cmake install
Thanks for the catch, sudo cmake --build . --target install &> install.log worked. Yes, I plan to use a package manager like Conan or conda rather than the horrible tangle of scripts I have now for Travis and Appveyor, just have a few other things to do first. ;-) -- Adam Getchell https://keybase.io/adamgetchell > On Sep 10, 2017, at 5:42 AM, Michael Jackson <mike.jack...@bluequartz.net> > wrote: > > You should explicitly set the installation location of your package using > –DCMAKE_INSTALL_PREFIX=/xxx///xxx during the initial invocation of > cmake. > > This should be set to a location you KNOW you have normal write access to. > Once this is set then you will no longer need to use “sudo” to run the > commands and all _should_ work correctly. This is what we do on our dashboard > builds. > > -- > Mike Jackson > > > From: CMake <cmake-boun...@cmake.org> on behalf of Adam Getchell > <adam.getch...@gmail.com> > Date: Friday, September 8, 2017 at 9:20 PM > To: Craig Scott <craig.sc...@crascit.com> > Cc: CMake <cmake@cmake.org> > Subject: Re: [CMake] cmake install > > >> On Sep 8, 2017, at 6:11 PM, Craig Scott <craig.sc...@crascit.com >> <mailto:craig.sc...@crascit.com>> wrote: >>> >>> I tried: >>> >>> # cmake -G Ninja . >>> # cmake --build . >>> # cmake --build . --target install >> >> This should be correct. Did this not work for you? > > No. > > https://travis-ci.org/acgetchell/CDT-plusplus/jobs/273498700 > <https://travis-ci.org/acgetchell/CDT-plusplus/jobs/273498700> > > Thanks for your help. > >> >> >>> If its somewhere in the manual, I’d appreciate pointers. >> >> Which part were you looking for? The use of --target is documented as part >> of the Build Tool Mode >> <https://cmake.org/cmake/help/git-master/manual/cmake.1.html#build-tool-mode> >> section, but it seems you've already figured out that part. There's nothing >> technically special about the install target as far as I'm aware, you should >> be able to refer to it as a build target like you've done above. >> >> >> Craig Scott >> Melbourne, Australia >> https://crascit.com <https://crascit.com/> > -- > Adam Getchell > https://keybase.io/adamgetchell <https://keybase.io/adamgetchell> > > -- Powered by www.kitware.com <http://www.kitware.com/> Please keep messages > on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ > <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 > <http://cmake.org/cmake/help/support.html> CMake Consulting: > http://cmake.org/cmake/help/consulting.html > <http://cmake.org/cmake/help/consulting.html> CMake Training Courses: > http://cmake.org/cmake/help/training.html > <http://cmake.org/cmake/help/training.html> Visit other Kitware open-source > projects at http://www.kitware.com/opensource/opensource.html > <http://www.kitware.com/opensource/opensource.html> Follow this link to > subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake > <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] cmake install
> On Sep 8, 2017, at 6:11 PM, Craig Scott <craig.sc...@crascit.com> wrote: > > I tried: > > # cmake -G Ninja . > # cmake --build . > # cmake --build . --target install > > This should be correct. Did this not work for you? No. https://travis-ci.org/acgetchell/CDT-plusplus/jobs/273498700 Thanks for your help. > > > If its somewhere in the manual, I’d appreciate pointers. > > Which part were you looking for? The use of --target is documented as part of > the Build Tool Mode > <https://cmake.org/cmake/help/git-master/manual/cmake.1.html#build-tool-mode> > section, but it seems you've already figured out that part. There's nothing > technically special about the install target as far as I'm aware, you should > be able to refer to it as a build target like you've done above. > > > Craig Scott > Melbourne, Australia > https://crascit.com <https://crascit.com/> -- Adam Getchell https://keybase.io/adamgetchell -- 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] cmake install
Hello all, If I want to use CMake to invoke my build system, I can use: # cmake -- build . What’s the syntax for invoking the build system installer from cmake, i.e. the equivalent of: # cmake -G Ninja . # ninja # ninja install I tried: # cmake -G Ninja . # cmake --build . # cmake --build . --target install If its somewhere in the manual, I’d appreciate pointers. Thanks, Adam -- Adam Getchell https://keybase.io/adamgetchell -- 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] CMake 3.9.0 Windows zip file shows wrong version
Yeah, that was it, lol. -- Adam Getchell https://keybase.io/adamgetchell > On Aug 8, 2017, at 1:33 AM, David Cole <dlrd...@aol.com> wrote: > > I suspect you are running a different cmake, not the one you've unzipped. > > Type "where cmake" instead of "cmake --version" and Windows will list > the directories where it finds an executable named cmake. The first > one it lists is the one it is running when you type "cmake > --version"... > > If you want to force the one you've downloaded to run instead of that > one, you could **prepend** to the PATH instead of appending to it. > > > HTH, > David C. > > > > On Mon, Aug 7, 2017 at 9:07 PM, Adam Getchell <adam.getch...@gmail.com> wrote: >> Hi all, >> >> The CMake 3.9.0 Windows zip file gives the wrong version. Here’s a snippet >> from my AppVeyor logs [1]: >> >> set CMAKE_URL="https://cmake.org/files/v3.9/cmake-3.9.0-win64-x64.zip; >> appveyor DownloadFile %CMAKE_URL% -FileName cmake.zip >> Downloading cmake.zip (25,944,520 bytes)...100% >> 7z x cmake.zip -oC:\projects\dev >> 7-Zip [64] 16.04 : Copyright (c) 1999-2016 Igor Pavlov : 2016-10-04 >> Scanning the drive for archives: >> 1 file, 25944520 bytes (25 MiB) >> Extracting archive: cmake.zip >> -- >> Path = cmake.zip >> Type = zip >> Physical Size = 25944520 >> Everything is Ok >> Folders: 90 >> Files: 4922 >> Size: 66584952 >> Compressed: 25944520 >> set PATH=%PATH%;C:\projects\dev\cmake\bin >> cmake --version >> cmake version 3.8.2 >> CMake suite maintained and supported by Kitware (kitware.com/cmake). >> >> [1] https://ci.appveyor.com/project/acgetchell/cdt-plusplus >> -- >> Adam Getchell >> https://keybase.io/adamgetchell >> >> >> -- >> >> 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
[CMake] CMake 3.9.0 Windows zip file shows wrong version
Hi all, The CMake 3.9.0 Windows zip file gives the wrong version. Here’s a snippet from my AppVeyor logs [1]: set CMAKE_URL="https://cmake.org/files/v3.9/cmake-3.9.0-win64-x64.zip; <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L15>appveyor DownloadFile %CMAKE_URL% -FileName cmake.zip <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L16>Downloading cmake.zip (25,944,520 bytes)...100% <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L17>7z x cmake.zip -oC:\projects\dev <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L18> <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L19>7-Zip [64] 16.04 : Copyright (c) 1999-2016 Igor Pavlov : 2016-10-04 <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L20> <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L21>Scanning the drive for archives: <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L22>1 file, 25944520 bytes (25 MiB) <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L23> <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L24>Extracting archive: cmake.zip <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L25>-- <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L26>Path = cmake.zip <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L27>Type = zip <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L28>Physical Size = 25944520 <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L29> <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L30>Everything is Ok <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L31> <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L32>Folders: 90 <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L33>Files: 4922 <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L34>Size: 66584952 <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L35>Compressed: 25944520 <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L36>set PATH=%PATH%;C:\projects\dev\cmake\bin <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L37>cmake --version <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L38>cmake version 3.8.2 <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L39> <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L40>CMake suite maintained and supported by Kitware (kitware.com/cmake). <https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.108#L41> [1] https://ci.appveyor.com/project/acgetchell/cdt-plusplus -- Adam Getchell https://keybase.io/adamgetchell -- 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] Setting build type
Hello all, You were correct, when CGAL is built it overrides CMAKE_BUILD_TYPE, as documented here: http://doc.cgal.org/latest/Manual/installation.html The solution is to invoke: cmake -DCGAL_DONT_OVERRIDE_CMAKE_FLAGS=True -DCMAKE_BUILD_TYPE=Debug .. Thanks for your help! Adam On Sun, Mar 1, 2015 at 1:41 PM, Mark Abraham mark.j.abra...@gmail.com wrote: Hi, Looks like one of your find_package calls is setting the build type variable, which it should not... Mark On 27/02/2015 5:47 pm, Adam Getchell adam.getch...@gmail.com wrote: Thanks for the help! It still runs Release mode: Here's my project: https://github.com/acgetchell/CDT-plusplus ┌─[*adam*][Hapkido][*±*][master *✗*][~/CDT-plusplus] └─▪ tree . |.git | |config | |description | |HEAD | |hooks | | |applypatch-msg.sample | | |commit-msg.sample | | |post-update.sample | | |pre-applypatch.sample | | |pre-commit.sample | | |pre-push.sample | | |pre-rebase.sample | | |prepare-commit-msg.sample | | |update.sample | |index | |info | | |exclude | |logs | | |HEAD | | |refs | | | |heads | | | | |master | | | |remotes | | | | |origin | | | | | |HEAD | |objects | | |info | | |pack | | | |pack-a9db5eb5c90025a8ca13bddf15822cb0e57cbead.idx | | | |pack-a9db5eb5c90025a8ca13bddf15822cb0e57cbead.pack | |packed-refs | |refs | | |heads | | | |master | | |remotes | | | |origin | | | | |HEAD | | |tags |.gitignore |.travis-linux.yml |.travis-macosx.yml |.travis.yml |build.sh |CMakeLists.txt |Doxyfile |LICENSE |README.md |scan-build.sh |src | |cdt.cpp | |Delaunay.h | |docopt | | |docopt.cpp | | |docopt.h | | |docopt_private.h | | |docopt_util.h | | |docopt_value.h | | |examples | | | |naval_fate.cpp | | |LICENSE-Boost-1.0 | | |LICENSE-MIT | | |main.cpp | | |README.rst | | |run_testcase.cpp | | |run_tests.py | | |testcases.docopt | |grid_d.cpp | |grid_d.h | |periodic_3_complex.h | |periodic_3_triangulations.h | |Point.h | |S3Action.h | |S3ErgodicMoves.h | |S3Triangulation.h | |sphere_d.h | |utilities.h |unittests | |.gitignore | |main.cpp | |PointTest.cpp | |S3BulkActionTest.cpp | |S3ErgodicMovesTest.cpp | |S3TetrahedronTest.cpp | |SdTriangulationTest.cpp | |SphereTest.cpp | |Triangulated2SphereTest.cpp | |VertexTest.cpp ┌─[*adam*][Hapkido][*±*][master *✗*][~/CDT-plusplus] └─▪ mkdir build-d ┌─[*adam*][Hapkido][*±*][master *✗*][~/CDT-plusplus] └─▪ cd build-d ┌─[*adam*][Hapkido][*±*][master *✗*][~/CDT-plusplus/build-d] └─▪ cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=out .. -- The C compiler identification is AppleClang 6.0.0.656 -- The CXX compiler identification is AppleClang 6.0.0.656 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Build type: Release -- USING CXXFLAGS = ' -O3 -DNDEBUG' -- USING EXEFLAGS = ' -Wl,-dylib_file,/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib ' -- Targetting Unix Makefiles -- Using /usr/bin/c++ compiler. -- DARWIN_VERSION=14 -- Mac Leopard detected -- Requested component: Core -- Requested component: MPFR -- Requested component: GMP -- Found Eigen3: /usr/local/include/eigen3 (found suitable version 3.2.4, minimum required is 3.1.0) -- Found Intel TBB -- Configuring done -- Generating done -- Build files have been written to: /Users/adam/CDT-plusplus/build-d ┌─[*adam*][Hapkido][*±*][master *✗*][~/CDT-plusplus/build-d] On Wed, Feb 25, 2015 at 1:37 AM, J Decker d3c...@gmail.com wrote: mkdir build-d cd build-d cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=out ../your/source/procject cmake --build . cd .. mkdir build-r cd build-r cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=out ../your/source/procject cmake --build . --target install cd .. On Wed, Feb 25, 2015 at 1:16 AM, Adam Getchell adam.getch...@gmail.com wrote: Thanks for your reply. I'm not sure I follow your answer. I do delete the directory each time I build, but I'm still not understanding how you're building release or debug versions to begin with. I'm just automatically getting Release, unless I edit CMakeCache.txt
Re: [CMake] Setting build type
Thanks for the help! It still runs Release mode: Here's my project: https://github.com/acgetchell/CDT-plusplus ┌─[*adam*][Hapkido][*±*][master *✗*][~/CDT-plusplus] └─▪ tree . |.git | |config | |description | |HEAD | |hooks | | |applypatch-msg.sample | | |commit-msg.sample | | |post-update.sample | | |pre-applypatch.sample | | |pre-commit.sample | | |pre-push.sample | | |pre-rebase.sample | | |prepare-commit-msg.sample | | |update.sample | |index | |info | | |exclude | |logs | | |HEAD | | |refs | | | |heads | | | | |master | | | |remotes | | | | |origin | | | | | |HEAD | |objects | | |info | | |pack | | | |pack-a9db5eb5c90025a8ca13bddf15822cb0e57cbead.idx | | | |pack-a9db5eb5c90025a8ca13bddf15822cb0e57cbead.pack | |packed-refs | |refs | | |heads | | | |master | | |remotes | | | |origin | | | | |HEAD | | |tags |.gitignore |.travis-linux.yml |.travis-macosx.yml |.travis.yml |build.sh |CMakeLists.txt |Doxyfile |LICENSE |README.md |scan-build.sh |src | |cdt.cpp | |Delaunay.h | |docopt | | |docopt.cpp | | |docopt.h | | |docopt_private.h | | |docopt_util.h | | |docopt_value.h | | |examples | | | |naval_fate.cpp | | |LICENSE-Boost-1.0 | | |LICENSE-MIT | | |main.cpp | | |README.rst | | |run_testcase.cpp | | |run_tests.py | | |testcases.docopt | |grid_d.cpp | |grid_d.h | |periodic_3_complex.h | |periodic_3_triangulations.h | |Point.h | |S3Action.h | |S3ErgodicMoves.h | |S3Triangulation.h | |sphere_d.h | |utilities.h |unittests | |.gitignore | |main.cpp | |PointTest.cpp | |S3BulkActionTest.cpp | |S3ErgodicMovesTest.cpp | |S3TetrahedronTest.cpp | |SdTriangulationTest.cpp | |SphereTest.cpp | |Triangulated2SphereTest.cpp | |VertexTest.cpp ┌─[*adam*][Hapkido][*±*][master *✗*][~/CDT-plusplus] └─▪ mkdir build-d ┌─[*adam*][Hapkido][*±*][master *✗*][~/CDT-plusplus] └─▪ cd build-d ┌─[*adam*][Hapkido][*±*][master *✗*][~/CDT-plusplus/build-d] └─▪ cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=out .. -- The C compiler identification is AppleClang 6.0.0.656 -- The CXX compiler identification is AppleClang 6.0.0.656 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Build type: Release -- USING CXXFLAGS = ' -O3 -DNDEBUG' -- USING EXEFLAGS = ' -Wl,-dylib_file,/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib ' -- Targetting Unix Makefiles -- Using /usr/bin/c++ compiler. -- DARWIN_VERSION=14 -- Mac Leopard detected -- Requested component: Core -- Requested component: MPFR -- Requested component: GMP -- Found Eigen3: /usr/local/include/eigen3 (found suitable version 3.2.4, minimum required is 3.1.0) -- Found Intel TBB -- Configuring done -- Generating done -- Build files have been written to: /Users/adam/CDT-plusplus/build-d ┌─[*adam*][Hapkido][*±*][master *✗*][~/CDT-plusplus/build-d] On Wed, Feb 25, 2015 at 1:37 AM, J Decker d3c...@gmail.com wrote: mkdir build-d cd build-d cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=out ../your/source/procject cmake --build . cd .. mkdir build-r cd build-r cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=out ../your/source/procject cmake --build . --target install cd .. On Wed, Feb 25, 2015 at 1:16 AM, Adam Getchell adam.getch...@gmail.com wrote: Thanks for your reply. I'm not sure I follow your answer. I do delete the directory each time I build, but I'm still not understanding how you're building release or debug versions to begin with. I'm just automatically getting Release, unless I edit CMakeCache.txt after I've built once. I just checked CGAL_CreateSingleSourceCGALProgram.cmake which is invoked in my CMakeLists.txt, but I do not see it setting the build type to Release. https://github.com/acgetchell/CDT-plusplus/blob/master/CMakeLists.txt On Tue, Feb 24, 2015 at 12:20 PM, J Decker d3c...@gmail.com wrote: I use a different directory to build release and debug versions if you didn't delete, then when it goes to build partial things, the .obj files will still be newer than the .c files and will cause mixed release-debug builds which generally results in bizarre crashes. Once chosen, can't change the build type of a build; although if you could
Re: [CMake] Setting build type
Thanks for your reply.
I'm not sure I follow your answer. I do delete the directory each time I
build, but I'm still not understanding how you're building release or debug
versions to begin with.
I'm just automatically getting Release, unless I edit CMakeCache.txt after
I've built once.
I just checked CGAL_CreateSingleSourceCGALProgram.cmake which is invoked in
my CMakeLists.txt, but I do not see it setting the build type to Release.
https://github.com/acgetchell/CDT-plusplus/blob/master/CMakeLists.txt
On Tue, Feb 24, 2015 at 12:20 PM, J Decker d3c...@gmail.com wrote:
I use a different directory to build release and debug versions
if you didn't delete, then when it goes to build partial things, the .obj
files will still be newer than the .c files and will cause mixed
release-debug builds which generally results in bizarre crashes.
Once chosen, can't change the build type of a build; although if you could
it should do a clean also.
On Tue, Feb 24, 2015 at 11:42 AM, Adam Getchell adam.getch...@gmail.com
wrote:
Hello all,
I've browsed this thread:
http://www.cmake.org/pipermail/cmake/2008-September/023808.html
But it doesn't work. My project is set to Release regardless, whether I
do:
project( CDT-plusplus_ )
set(CMAKE_BUILD_TYPE RelWithDebInfo)
Or:
#
# If the user specifies -DCMAKE_BUILD_TYPE on the command line, take
their definition
# and dump it in the cache along with proper documentation, otherwise set
CMAKE_BUILD_TYPE
# to Debug prior to calling PROJECT()
#
IF(DEFINED CMAKE_BUILD_TYPE)
SET(CMAKE_BUILD_TYPE ${CMAKE_BUILD_TYPE} CACHE STRING Choose the type
of
build, options are: None(CMAKE_CXX_FLAGS or CMAKE_C_FLAGS used) Debug
Release RelWithDebInfo MinSizeRel.)
ELSE()
SET(CMAKE_BUILD_TYPE Debug CACHE STRING Choose the type of build,
options are: None(CMAKE_CXX_FLAGS or CMAKE_C_FLAGS used) Debug Release
RelWithDebInfo MinSizeRel.)
ENDIF()
project( CDT-plusplus_ )
The only way I can change the build type is by going into my build
directory and editing CMakeCache.txt. However, I use an out of source
build, so my build directory is generated automatically by scripts such as:
https://github.com/acgetchell/CDT-plusplus/blob/master/scan-build.sh
What's the correct method for being able to set the type of build via the
command line?
--
Adam Getchell
about.me/adamgetchell
Invincibility is in oneself, vulnerability in the opponent. -- Sun Tzu
--
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
--
Adam Getchell
about.me/adamgetchell
Invincibility is in oneself, vulnerability in the opponent. -- Sun Tzu
--
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] Setting build type
Hello all,
I've browsed this thread:
http://www.cmake.org/pipermail/cmake/2008-September/023808.html
But it doesn't work. My project is set to Release regardless, whether I do:
project( CDT-plusplus_ )
set(CMAKE_BUILD_TYPE RelWithDebInfo)
Or:
#
# If the user specifies -DCMAKE_BUILD_TYPE on the command line, take their
definition
# and dump it in the cache along with proper documentation, otherwise set
CMAKE_BUILD_TYPE
# to Debug prior to calling PROJECT()
#
IF(DEFINED CMAKE_BUILD_TYPE)
SET(CMAKE_BUILD_TYPE ${CMAKE_BUILD_TYPE} CACHE STRING Choose the type of
build, options are: None(CMAKE_CXX_FLAGS or CMAKE_C_FLAGS used) Debug
Release RelWithDebInfo MinSizeRel.)
ELSE()
SET(CMAKE_BUILD_TYPE Debug CACHE STRING Choose the type of build,
options are: None(CMAKE_CXX_FLAGS or CMAKE_C_FLAGS used) Debug Release
RelWithDebInfo MinSizeRel.)
ENDIF()
project( CDT-plusplus_ )
The only way I can change the build type is by going into my build
directory and editing CMakeCache.txt. However, I use an out of source
build, so my build directory is generated automatically by scripts such as:
https://github.com/acgetchell/CDT-plusplus/blob/master/scan-build.sh
What's the correct method for being able to set the type of build via the
command line?
--
Adam Getchell
about.me/adamgetchell
Invincibility is in oneself, vulnerability in the opponent. -- Sun Tzu
--
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] Correct settings to add docopt.cpp to target list
It turns out that CGAL's CGAL_CreateSingleSourceCGALProgram.cmake module handles this nicely: create_single_source_cgal_program( src/cdt-docopt.cpp src/docopt/docopt.cpp) does the trick. Thanks for your consideration! On Thu, Dec 4, 2014 at 10:54 PM, Adam Getchell adam.getch...@gmail.com wrote: I should note that I'm doing an out of source build, and that for my project the following line works: ┌─[*adam*][Hapkido][*±*][docopt *✓*][~/CDT-plusplus/build] └─▪ clang++ --std=c++11 --stdlib=libc++ -I ../src/docopt ../src/docopt/docopt.cpp ../src/cdt-docopt.cpp -o cdt_docopt On Thu, Dec 4, 2014 at 9:30 PM, Adam Getchell adam.getch...@gmail.com wrote: Hello all, I’m trying to use the docopt.cpp parser for my project[1]: https://github.com/docopt/docopt.cpp The usual invocation to build works: ┌─[*adam*][Hapkido][*±*][docopt *✗*][~/CDT-plusplus/src/docopt] └─▪ clang++ --std=c++11 --stdlib=libc++ -I . docopt.cpp examples/naval_fate.cpp -o naval_fate So, I want to add docopt.cpp and have the compiler look for header files in the same directory, and add that to my executable. So far, what I’ve attempted is to add the lines: include_directories (BEFORE src/docopt) add_library(docopt.cpp src/docopt/docopt.cpp”) My program uses CGAL[2], and all of those library headers are incorporated using the create_single_source_cgal_program function in the CGAL_CreateSingleSourceCGALProgram.cmake module. The error messages I’m getting correspond to the ones I get when docopt.cpp is not included: ┌─[*adam*][Hapkido][*±*][docopt *✗*][~/CDT-plusplus/src/docopt] └─▪ clang++ --std=c++11 --stdlib=libc++ -I . examples/naval_fate.cpp -o naval_fate Undefined symbols for architecture x86_64: docopt::docopt(std::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorchar const, std::__1::vectorstd::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorchar , std::__1::allocatorstd::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorcharconst, bool, std::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorchar const, bool), referenced from: _main in naval_fate-780283.o docopt::operator(std::__1::basic_ostreamchar, std::__1::char_traitschar , docopt::value const), referenced from: _main in naval_fate-780283.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Compare to: ┌─[*adam*][Hapkido][*±*][docopt *✗*][~/CDT-plusplus] └─▪ ./build.sh -- The C compiler identification is AppleClang 6.0.0.654 -- The CXX compiler identification is AppleClang 6.0.0.654 -- Check for working C compiler using: Ninja -- Check for working C compiler using: Ninja -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler using: Ninja -- Check for working CXX compiler using: Ninja -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Build type: Release -- USING CXXFLAGS = ' -O3 -DNDEBUG' -- USING EXEFLAGS = ' -Wl,-dylib_file,/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib ' -- Targetting Ninja -- Using /usr/bin/c++ compiler. -- DARWIN_VERSION=14 -- Mac Leopard detected -- Requested component: Core -- Requested component: MPFR -- Requested component: GMP -- Found Eigen3: /usr/local/include/eigen3 (found suitable version 3.2.2, minimum required is 3.1.0) -- Configuring done -- Generating done -- Build files have been written to: /Users/adam/CDT-plusplus/build [10/13] Linking CXX executable cdt-docopt FAILED: : /usr/bin/c++ -O3 -DNDEBUG -Wl,-search_paths_first -Wl,-headerpad_max_install_names -Wl,-dylib_file,/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib CMakeFiles/cdt-docopt.dir/src/cdt-docopt.cpp.o -o cdt-docopt -L/Users/adam/gmock-1.7.0/lib/.libs -L/Users/adam/gmock-1.7.0/gtest/lib/.libs /usr/local/lib/libmpfr.dylib /usr/local/lib/libgmp.dylib /usr/local/lib/libCGAL_Core.dylib /usr/local/lib/libCGAL.dylib /usr/local/lib/libboost_thread-mt.dylib /usr/local/lib/libboost_system-mt.dylib /usr/local/lib/libCGAL_Core.dylib /usr/local/lib/libCGAL.dylib /usr/local/lib/libboost_thread-mt.dylib /usr/local/lib/libboost_system-mt.dylib -Wl,-rpath,/Users/adam/gmock-1.7.0/lib/.libs -Wl,-rpath,/Users/adam/gmock-1.7.0/gtest/lib/.libs : Undefined symbols for architecture x86_64: docopt::docopt(std::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorchar const, std::__1::vectorstd::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorchar , std::__1::allocatorstd::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorcharconst, bool, std::__1
[CMake] Correct settings to add docopt.cpp to target list
://www.cgal.org https://www.cgal.org/ Adam Getchell about.me/adamgetchell -- 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] Correct settings to add docopt.cpp to target list
I should note that I'm doing an out of source build, and that for my project the following line works: ┌─[*adam*][Hapkido][*±*][docopt *✓*][~/CDT-plusplus/build] └─▪ clang++ --std=c++11 --stdlib=libc++ -I ../src/docopt ../src/docopt/docopt.cpp ../src/cdt-docopt.cpp -o cdt_docopt On Thu, Dec 4, 2014 at 9:30 PM, Adam Getchell adam.getch...@gmail.com wrote: Hello all, I’m trying to use the docopt.cpp parser for my project[1]: https://github.com/docopt/docopt.cpp The usual invocation to build works: ┌─[*adam*][Hapkido][*±*][docopt *✗*][~/CDT-plusplus/src/docopt] └─▪ clang++ --std=c++11 --stdlib=libc++ -I . docopt.cpp examples/naval_fate.cpp -o naval_fate So, I want to add docopt.cpp and have the compiler look for header files in the same directory, and add that to my executable. So far, what I’ve attempted is to add the lines: include_directories (BEFORE src/docopt) add_library(docopt.cpp src/docopt/docopt.cpp”) My program uses CGAL[2], and all of those library headers are incorporated using the create_single_source_cgal_program function in the CGAL_CreateSingleSourceCGALProgram.cmake module. The error messages I’m getting correspond to the ones I get when docopt.cpp is not included: ┌─[*adam*][Hapkido][*±*][docopt *✗*][~/CDT-plusplus/src/docopt] └─▪ clang++ --std=c++11 --stdlib=libc++ -I . examples/naval_fate.cpp -o naval_fate Undefined symbols for architecture x86_64: docopt::docopt(std::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorchar const, std::__1::vectorstd::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorchar , std::__1::allocatorstd::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorcharconst, bool, std::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorchar const, bool), referenced from: _main in naval_fate-780283.o docopt::operator(std::__1::basic_ostreamchar, std::__1::char_traitschar , docopt::value const), referenced from: _main in naval_fate-780283.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Compare to: ┌─[*adam*][Hapkido][*±*][docopt *✗*][~/CDT-plusplus] └─▪ ./build.sh -- The C compiler identification is AppleClang 6.0.0.654 -- The CXX compiler identification is AppleClang 6.0.0.654 -- Check for working C compiler using: Ninja -- Check for working C compiler using: Ninja -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler using: Ninja -- Check for working CXX compiler using: Ninja -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Build type: Release -- USING CXXFLAGS = ' -O3 -DNDEBUG' -- USING EXEFLAGS = ' -Wl,-dylib_file,/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib ' -- Targetting Ninja -- Using /usr/bin/c++ compiler. -- DARWIN_VERSION=14 -- Mac Leopard detected -- Requested component: Core -- Requested component: MPFR -- Requested component: GMP -- Found Eigen3: /usr/local/include/eigen3 (found suitable version 3.2.2, minimum required is 3.1.0) -- Configuring done -- Generating done -- Build files have been written to: /Users/adam/CDT-plusplus/build [10/13] Linking CXX executable cdt-docopt FAILED: : /usr/bin/c++ -O3 -DNDEBUG -Wl,-search_paths_first -Wl,-headerpad_max_install_names -Wl,-dylib_file,/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib CMakeFiles/cdt-docopt.dir/src/cdt-docopt.cpp.o -o cdt-docopt -L/Users/adam/gmock-1.7.0/lib/.libs -L/Users/adam/gmock-1.7.0/gtest/lib/.libs /usr/local/lib/libmpfr.dylib /usr/local/lib/libgmp.dylib /usr/local/lib/libCGAL_Core.dylib /usr/local/lib/libCGAL.dylib /usr/local/lib/libboost_thread-mt.dylib /usr/local/lib/libboost_system-mt.dylib /usr/local/lib/libCGAL_Core.dylib /usr/local/lib/libCGAL.dylib /usr/local/lib/libboost_thread-mt.dylib /usr/local/lib/libboost_system-mt.dylib -Wl,-rpath,/Users/adam/gmock-1.7.0/lib/.libs -Wl,-rpath,/Users/adam/gmock-1.7.0/gtest/lib/.libs : Undefined symbols for architecture x86_64: docopt::docopt(std::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorchar const, std::__1::vectorstd::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorchar , std::__1::allocatorstd::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorcharconst, bool, std::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorchar const, bool), referenced from: _main in cdt-docopt.cpp.o docopt::operator(std::__1::basic_ostreamchar, std::__1::char_traitschar , docopt::value const), referenced from: _main in cdt-docopt.cpp.o ld: symbol(s
[CMake] How to sign up project for public CDASH
Hello all, I’m following the directions posted here: http://www.cmake.org/Wiki/CMake_Testing_With_CTest I’d like to get my dashboard up on the public one: http://open.cdash.org/index.php?project=PublicDashboard I’ve obtained an account on CTest. How do I register my project? Thanks, Adam Getchell -- 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
