Firstly remember that Windows is but one (small) platform, UnitTest++ run on Linux/Unix(all flavours I've tried) and Windows.
For what it's worth, we use CMake on some of our multiplatform products (running on Windows/AIX/Linux) and it is excellent. Unittest++ is pretty small fortunately (and I'm guessing it'll stay that way for all the obvious reasons), but frankly, I think it's idiotic not to use CMake on multi-platform projects of medium size or larger. CMake is a million times easier to use than the GNU autoconfigure chain, and has the benefit of supporting Windows too. Even KDE is using CMake these days. The "layer of complexity" is merely a point of view - just because you understand CMake, doesn't mean it doesn't add value to someone else. We DON'T use the current vcproj files because we run on a whole range of MS compilers, and needed a different vcproj file depending on which compiler I'm using today is irritating. I for one would be happy if CMake support (possibly via a contrib or extras directory) was added to UnitTest++ - it's pretty simple to do it without removing the current vcproj files, thereby catering for all of us. From: Graham Reeds [mailto:graham.re...@gmail.com] Sent: 17 August 2010 23:56 PM To: UnitTest++ development and use Subject: Re: [unittest-cpp-devel] cmake? I am not flaming you. Just explaining that CMake doesn't add anything to UnitTest++ - just adds a layer of complexity. GR. On 17 August 2010 19:21, Simmons, Aaron <asimm...@rosettastone.com> wrote: Well, take it or leave it. I'm just trying to contribute back to a piece of software I like-I didn't expect to get flamed. From: Graham Reeds [mailto:graham.re...@gmail.com] Sent: Tuesday, August 17, 2010 12:19 To: UnitTest++ development and use Subject: Re: [unittest-cpp-devel] cmake? This may sound dumb, but: what does AMOP have to do with UnitTest++? AMOP uses CMake for building. It may be that AMOP has a bug in their cmake script (gasp). If AMOP does have a bug in their cmake script then I am not going to debug it. I want to use a tool now, not after I have debugged it. I get paid for working on our software, not debugging a third party product whose value is dubious. I don't want to spend a couple of hours to debug it, just to find that what I want to do with it isn't possible. This goes for any software, not just AMOP. Have you tried my cmake file with UnitTest++? No, because UnitTest++ comes with vcproj files which is what I want. GR From: Graham Reeds [mailto:graham.re...@gmail.com] Sent: Tuesday, August 17, 2010 11:57 To: UnitTest++ development and use Subject: Re: [unittest-cpp-devel] cmake? Just tried building AMOP via CMake 2.8.1. Failed miserably, no project files created. So no, I would not be happy if UnitTest++ moved to CMake. I guess I won't be using AMOP. GR On 17 August 2010 18:10, Graham Reeds <graham.re...@gmail.com> wrote: I've just actually commented on this on the AMOP wiki page less than 10 minutes ago: I am not particularly enamoured by having to download a transitory piece of software which will be used once. GR. On 17 August 2010 17:32, Simmons, Aaron <asimm...@rosettastone.com> wrote: I've noticed that UnitTest++ is going through a lot of trouble to maintain build scripts for each platform (a Makefile, two versions of MSVC project files, etc). Have you considered CMake? It's a makefile builder that abstracts the platform-specific parts of build systems (sort of like Autoconf, but more cross-platform). It can build makefiles, nmake files, MSVC project files (v6 thru v10), and even Eclipse and XCode project files. In my own project it made a huge difference in the pain involved in supporting multiple platforms. Anyway, I just started using UnitTest++ in my project (so far I think it's the best unit testing framework for C/C++!) and had to integrate it with our CMake build scripts. Since I went through the trouble of getting UnitTest++ to work with CMake, I thought you might be able to make use of it. Below is CMakeLists.txt: cmake_minimum_required(VERSION 2.8.1) project(UnitTest++) # get the main sources file(GLOB SRCS RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} src/*.cpp src/*.h) source_group("" FILES ${SRCS}) # get platform specific sources if (WIN32) set(PLAT_DIR Win32) else() set(PLAT_DIR Posix) endif(WIN32) file(GLOB PLAT_SRCS RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} src/${PLAT_DIR}/*.cpp src/${PLAT_DIR}/*.h) source_group(${PLAT_DIR} FILES ${PLAT_SRCS}) # create the lib add_library(UnitTestPP STATIC ${SRCS} ${PLAT_SRCS}) set_target_properties(UnitTestPP PROPERTIES OUTPUT_NAME UnitTest++) include_directories(src) # build the test runner file(GLOB TEST_SRCS RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} src/tests/*.cpp src/tests/*.h) source_group( "" FILES ${TEST_SRCS}) add_executable(TestUnitTestPP ${TEST_SRCS}) set_target_properties(TestUnitTestPP PROPERTIES OUTPUT_NAME TestUnitTest++) target_link_libraries(TestUnitTestPP UnitTestPP) # turn on testing enable_testing() add_custom_target(check COMMAND ${CMAKE_CTEST_COMMAND} -V) # add the test runner as a test add_test(NAME TestUnitTestPP COMMAND TestUnitTest++ ${CONFIG_PATH} ${CONFIG_TASKS_PATH} ${SOUND_LOG_PATH}) add_dependencies(check TestUnitTestPP) ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ unittest-cpp-devel mailing list unittest-cpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ unittest-cpp-devel mailing list unittest-cpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ unittest-cpp-devel mailing list unittest-cpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ unittest-cpp-devel mailing list unittest-cpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
