Re: [cmake-developers] Non-All platform test
On 12/13/2010 5:19 PM, Eric Noulard wrote: Hi All, I'm willing to improve CPack test coverage and even if my first try did make the CMake dashboard half red I intend to continue until its bigger and greener :-] Now I have a "test design" problem. Many CPack generator are not available on all platforms RPM, rpm based linux distro only (or debian base with rpm installed) DEB, debian based linux distro NSIS, Windows and sometimes Linux PackageMaker, MacOS ... Moreover the behavior of each generator may be different for the same project. How shall design the test for those? Shall check some system name pattern with an associated list of working CPack generator (or parse cpack help output for getting supposedly working ones) ? Are there some platform specific tests inside the CMake tree now? Is there any "design guidelines" for this kind of tests ? I would just do ad-hoc platform and find_program checks. I am pretty sure the NSIS stuff does not work on linux. So, just look for the tool that cpack will be using, and if found, enable the test. -Bill ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] User vs CMake include mismatch handling
On Tue, Dec 14, 2010 at 4:45 PM, Alexander Neundorf wrote: > On Tuesday 23 November 2010, Alexander Neundorf wrote: >> On Tuesday 23 November 2010, Brad King wrote: >> > On 11/23/2010 03:31 PM, Alexander Neundorf wrote: >> > > On Monday 22 November 2010, Brad King wrote: >> > >> On 11/22/2010 04:06 PM, Alexander Neundorf wrote: >> > >>> On Monday 22 November 2010, Brad King wrote: >> > (1) Improve documentation of CMAKE_USER_MAKE_RULES_OVERRIDE[_C] >> > variables (2) Add the Custom-<*> file inclusion, document it >> > > >> > > Could you take care of (1) ? >> > >> > Sure, but not until at least next week. The changes don't need to be >> > done in this order anyway. >> >> Ok :-) >> I'll start with the CMAKE_POLICY_DEFAULT_CMP stuff you suggested. > > I merged this now into next on stage. > It contains: > - the new policy CMP0017 > - the feature to set the default via CMAKE_POLICY_DEFAULT_CMP > - a basic test > - some documentation > > Please have a look at it. > > Alex > ___ > cmake-developers mailing list > cmake-developers@cmake.org > http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers > I assume it is the topic named "PreferCMakeModulesByCMakeModulesWithPolicy-NoTrailingWhitespaceCommit" whose head commit is presently http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a924ee511a33963fdce693b77982131df481df8f Correct? Thanks a lot for your persistence on this topic... I know it's been around for a while now. Cheers, David ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] User vs CMake include mismatch handling
On Tuesday 23 November 2010, Alexander Neundorf wrote: > On Tuesday 23 November 2010, Brad King wrote: > > On 11/23/2010 03:31 PM, Alexander Neundorf wrote: > > > On Monday 22 November 2010, Brad King wrote: > > >> On 11/22/2010 04:06 PM, Alexander Neundorf wrote: > > >>> On Monday 22 November 2010, Brad King wrote: > > (1) Improve documentation of CMAKE_USER_MAKE_RULES_OVERRIDE[_C] > > variables (2) Add the Custom-<*> file inclusion, document it > > > > > > Could you take care of (1) ? > > > > Sure, but not until at least next week. The changes don't need to be > > done in this order anyway. > > Ok :-) > I'll start with the CMAKE_POLICY_DEFAULT_CMP stuff you suggested. I merged this now into next on stage. It contains: - the new policy CMP0017 - the feature to set the default via CMAKE_POLICY_DEFAULT_CMP - a basic test - some documentation Please have a look at it. Alex ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
