RE: [CMake] CMake and Lua => DSL!?
Hello everyone, Sorry for the quick interruption, but somehow I have the feeling this discussion will start again and again and again, if it has ever appeared to end. Here are my two cents... IMHO there might be a misunderstanding concerning Kitware's CMake strategy: It is a domain specific language (DSL) for -- as this might indicate -- one specific purpose and therefore, by intention, not a general purpose (scripting) language; thus it concentrates correctly on its (single & powerful) core task/challenge. An estimated set of 7% of CMake's language commands covers about 97% of the usual cases. (Note that I have not even thought about thinking about this numbers.) Please accept this as an almost completely serious "feed to a never ending (?) discussion", Reinhold ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] exporting variables upwards
Hi Mattias, AFAIK there are 2 possibilities: (a) Using PARENT_SCOPE flag in SET of variable definition (b) Using GLOBAL scope for properties, cf. DEFINE_PROPERTY, GET_PROPERTY, SET_PROPERTY HTH Reinhold > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Mattias Holm > Sent: Monday, May 12, 2008 8:23 AM > To: cmake@cmake.org > Subject: [CMake] exporting variables upwards > > > Hi, > > I have a project structured as follows: > > xyz/ > CMakeLists.txt > src/ >CMakeLists.txt > rsrc/ >CMakeLists.txt > include/ >CMakeLists.txt > > > Now, if I in the rsrc directory locate a bunch of files and > set these > as variables, they will not be seen by the other CMakeLists, > is there > any way to overcome this? I.e so that the rsrc/CMakeLists can > set the > variable TEXTURES (and also properties on the files in that > variable) > that will be picked up by the src/CMakeList and added to a target in > that file. > > > Thanks, > Mattias > ___ > CMake mailing list > CMake@cmake.org > http://www.cmake.org/mailman/listinfo/cmake > ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] [ctest] junit xml output
Hi Maik and David,
Indeed a great idea -- I would be very much interested into it, in
particularly into junit xml output due to being "Ant-focused".
Note that we are currently implementing our C++ unit tests with cppunit,
and are then wrapping each cppunit test case into a ctest call for the
sake of security in our Ant-based CI on the buildserver.
This is another reason why I prefer junit xml output, because it is easy
(or maybe more correct: here I know how easy it is) to merge several
independent junit xml reports (cf. CI and isolation and wrapping each
cppunit test case into a ctest call).
Regards,
Reinhold
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of David Cole
Sent: Monday, May 19, 2008 1:02 PM
To: Maik Beckmann
Cc: cmake@cmake.org
Subject: Re: [CMake] [ctest] junit xml output
That's a great idea! Are cppunit and nunit output formats similar enough
to junit that they could all be done at once...?
Feel free to submit a patch implementing this as a feature request in
the bug tracker... or to create a CMake Wiki page with details on what
output format would be useful for this feature.
How many others out there reading this list would be interested?
On Mon, May 19, 2008 at 7:22 AM, Maik Beckmann
<[EMAIL PROTECTED]> wrote:
Hi,
I thinking about working on ant's junit xml format as a secondary output
format of ctest. This way it would be much more convenient to integrate
ctest results into one of the java centric/compatible dashboards.
The idea came to my mind when considering hudson
(https://hudson.dev.java.net/) as a lightweight continuous integration
system
for one-person usage.
An option may be distributing a ctest_to_junit.xsl file, but teaching it
to
ctest makes it much more easy to use.
What do you people think?
-- Maik
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] [ctest] junit xml output
> I think the xslt road is the best bet. A c++ code solution > would result in a > much higher complexity and most likely to a much higher > memory footprint. > > The xslt processor can be treated similar to the other tools > like cvs and svn, > which gives ctest the chance to do some error checking. +1 Reinhold ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] CMake with wxWidgets on Linux
Hello Brian, I think for recent wxWidgets versions the best references for CMake based project building are by Jorgen Bodde and Jerry Fath based on initial work from Klaas Holwerda (please correct me if i am wrong), see: - http://www.wxwidgets.org/wiki/index.php/CMake, - http://wastebucket.solidsteel.nl/cms/modules/wiwimod/index.php?page=wxTreeMult iCtrl&back=WiwiHome - http://www.fath.us/downloads/wxcmake.zip Maybe one of these modules should find its place into the standard CMake installation at some time? If I am not wrong (again), the currently bundled modules are a little bit outdated. HTH Reinhold >= Original Message From "William A. Hoffman" <[EMAIL PROTECTED]> = >At 07:10 PM 5/27/2006, Brian Eastwood wrote: >>Hi All, >> >>I've been using CMake for a few years on Windows and recently switched over to Linux. I have been having some problems getting a basic hello world program running using wxWidgets, and figured someone here probably know what I am doing wrong. >Part of my confusion is the large number of cmake files that could be used to configure wxWidgets. My CMakeLists file is copied below. The program hworld.cxx is basically Robert Roebling's hello world tutorial from >http://www.wxwidgets.org/hello.htm >> >>I have no problems running cmake or compiling the project, but get a segmentation fault when I try running the program...there is no other output. (I'm assuming the application can't find a shared library, but I don't know which one that would >be.) >> >>I am running Fedora Core 5 and installed wxGTK, wxGTK-devel and compat-wxGTK2-devel (among others) from the fedora extras rpm repository. Are there other packages I should have installed? >> >>Thanks in advance for any suggestions. >>Cheers, >>Brian > >If you get a seg-fault it is not a missing library. I suggest you run gdb on >the program and figure out where it is crashing. One possible source of trouble >could be mis-matched header files and libraries. > >-Bill > >___ >CMake mailing list >CMake@cmake.org >http://www.cmake.org/mailman/listinfo/cmake ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] ctest -- test case specific timeouts?
Hello, According to http://www.cmake.org/pipermail/cmake/2007-January/012713.html test case specific timeouts should be supported via set_tests_properties in CMake 2.4.7. Unfortunately, this does not seem to work for me. Note that I don't want to use Dart, but just local CTest. Also, I want to explicitly avoid the global DART_TESTING_TIMEOUT (which is working as expected). Please correct me if I am wrong, but as a result of the ENABLE_TESTING() ADD_TEST and SET_TESTS_PROPERTIES calls in my CMakeLists.txt a DartTestfile (see below) is generated that is then used by CTest; and CTest does not use any other information. ... ADD_TEST(ClassFilterTest "CTestCppUnitMain" "ClassFilterTest") SET_TESTS_PROPERTIES(ClassFilterTest PROPERTIES TIMEOUT 5) So my failing expectation is that the ClassFilterTest is killed in case it takes longer than 5 seconds, but it isn't. Thanks, Reinhold ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
