2010/7/5 Bill Hoffman bill.hoff...@kitware.com:
So, although not perfect, I prefer to close the bug when it is checked in to
next. My reason is that we have wa too many bugs open as it is. I
don't want to have to wait on the reporter to close it, as often times they
have lost interest
2010/8/3 Eric Noulard eric.noul...@gmail.com:
2010/8/3 David Cole david.c...@kitware.com:
On Mon, Aug 2, 2010 at 6:57 PM, Eric Noulard eric.noul...@gmail.com wrote:
2. may always be an option because it was the behavior we had before the
component support and ALL CPack generator may handle
Hi all,
I want to fuse two (or more) consecutive git commit in a single commit
in order to simplify my local history before pushing to remote.
What I mean is that git log contains let say 5 commits.
I want to fuse together commit 3 and 4 which would make
my total history depth to 4 (instead of 5
2010/8/3 Eric Noulard eric.noul...@gmail.com:
2010/8/3 David Cole david.c...@kitware.com:
On Mon, Aug 2, 2010 at 6:57 PM, Eric Noulard eric.noul...@gmail.com wrote:
2. may always be an option because it was the behavior we had before the
component support and ALL CPack generator may handle
2010/8/6 Clinton Stimpson clin...@elemtech.com:
On Thursday, August 05, 2010 04:46:01 pm Eric Noulard wrote:
2010/8/3 Eric Noulard eric.noul...@gmail.com:
2010/8/3 David Cole david.c...@kitware.com:
On Mon, Aug 2, 2010 at 6:57 PM, Eric Noulard eric.noul...@gmail.com
wrote:
2. may always
2010/8/6 Alexander Neundorf neund...@kde.org:
On Friday 06 August 2010, Eric Noulard wrote:
2010/8/6 Alexander Neundorf neund...@kde.org:
On Friday 06 August 2010, Eric Noulard wrote:
...
I think I missed the fact that you did not used component GROUPS
at all in the first place
Hi All,
After some discussion with Brad concerning the inclusion
of my patch proposal from component
(http://public.kitware.com/Bug/view.php?id=10736)
I decided to propose some CPack internal API redesign
that will ease the development of component support for
all CPack generators including
2010/8/12 Brad King brad.k...@kitware.com:
Hi Eric,
On 08/11/2010 05:47 PM, David Cole wrote:
The warnings Brad fixed showed up on the Continuous dashboard for CMake
here:
http://www.cdash.org/CDash/index.php?project=CMakedate=2010-08-11#Continuous
-wrapper stage if you want.
May not be tonight because it's getting late :-]
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
From 1c97d10c332d2bad205d3170b6bd170de83a6f0c Mon Sep 17 00:00:00 2001
From: Eric NOULARD eric.noul...@gmail.com
Date: Thu, 12
2010/9/20 Bill Hoffman bill.hoff...@kitware.com:
What do you think?
Seems to be covered:
(but I am guessing the install is not actually being called in that case...)
Ok then may be I can try to make install called, after
I found the test which is triggering this coverage.
2010/9/20 Eric Noulard eric.noul...@gmail.com:
2010/9/20 Bill Hoffman bill.hoff...@kitware.com:
What do you think?
Seems to be covered:
(but I am guessing the install is not actually being called in that case...)
Ok then may be I can try to make install called, after
I found the test
2010/9/20 Eric Noulard eric.noul...@gmail.com:
I pushed a working fix to stage fixAbsoluteDestHandlingRegression
including the CMake coding standard wrt to if {}.
I did NOT request the merge to next.
I'll wait until I'll try to craft the corresponding new test.
Should be tomorrow
Changing subject in order to re-classify the discussion.
2010/9/28 Brad King brad.k...@kitware.com:
On 09/28/2010 05:20 PM, Alexander Neundorf wrote:
On Tuesday 28 September 2010, Alexander Neundorf wrote:
Is this intended this way ?
The attached tiny patch seems to make
2010/10/12 Alexander Neundorf neund...@kde.org:
On Tuesday 12 October 2010, Marcus D. Hanwell wrote:
2010/10/12 Alexander Neundorf neund...@kde.org
It has its own copy of FindPackageHandleStandardArgs.cmake, which is used
in some of the Find modules. Avogadro is a dependency of Kalzium (KDE
2010/10/27 Alexander Neundorf neund...@kde.org:
On Wednesday 27 October 2010, David Cole wrote:
Yes, the rc3 was announced last week.
Are you sure ?
I can't find it in my emails, also neither here:
http://public.kitware.com/pipermail/cmake-developers/2010-October/date.html
nor here:
2010/11/14 Alexander Neundorf neund...@kde.org:
Hi,
the AddASM_NASMSupport branch (#10069) in staging is now good enough to be
merged into next (or master ?).
How does that happen ?
Should I simply ignore staging and merge my local branch into next and push
this ?
I don't know for
2010/12/9 David Cole david.c...@kitware.com:
Hello CMake users and devs,
(And now for something completely different...)
Controversial questions:
- Should we eliminate the bug tracker entirely and just do all
discussion and patches on the mailing list? (Why have two sources of
2011/1/4 David Cole david.c...@kitware.com:
We are aiming for doing RC1 on next Wed., Jan. 12, 2011.
That means all changes to be included must be merged to next by the
dashboard's nightly start time on Monday evening, Jan. 10, 2011 (by
01:00:00 UTC time)...
So... if you have changes that
2011/1/20 David Cole david.c...@kitware.com:
Moving to the CMake developer's list, as requested by this bug comment:
http://public.kitware.com/Bug/view.php?id=11693#c24958
Comments or thoughts on the topic are welcome...
Please reply here with any further discussion before adding more info
Hi there,
I cannot push to stage? or print staged branch:
$ ssh g...@cmake.org stage cmake print
is lasting forever.
any know trouble or is it on my side?
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
2011/1/30 Marcus D. Hanwell marcus.hanw...@kitware.com:
On Sun, Jan 30, 2011 at 7:37 AM, Eric Noulard eric.noul...@gmail.com wrote:
Hi there,
I cannot push to stage? or print staged branch:
$ ssh g...@cmake.org stage cmake print
is lasting forever.
any know trouble or is it on my side
2011/1/31 David Cole david.c...@kitware.com:
When you are logged in to Mantis, there should be a Monitor button right
under where you see a link to the patch that you attached...
Is there no Monitor button there?
(You may already be monitoring it if you attached a patch. I'm pretty sure
that
2011/1/31 Eric Noulard eric.noul...@gmail.com:
2011/1/31 Brad King brad.k...@kitware.com:
On 01/31/2011 03:07 AM, Eric Noulard wrote:
If not what could be the cause of this problem?
CMake 2.6's foreach does not support the IN LISTS syntax:
Ok, I see...
I'll fix this later today.
Just
2011/2/4 Michael Wild them...@gmail.com:
You could actually add a backlog status by customising the configuration:
http://manual.mantisbt.org/manual.customizing.mantis.customizing.status.values.php
This would be IMHO much less confusing and also much easier to use when
searching/filtering.
2011/2/5 Alexander Neundorf neund...@kde.org:
Hi,
in general we keep cmake as backward compatible as possible, so no builds are
broken.
In a local branch I have a version of cmake with a small improvement to the
graphviz support in cmake.
It turns the variable GRAPHVIZ_IGNORE_TARGETS from
2011/2/8 Brad King brad.k...@kitware.com:
On 02/06/2011 03:58 PM, Eric Noulard wrote:
if there is one RC left before 2.8.4 it would be nice to include this
patchset.
Does this fix a regression from a previous release?
No this is not a regression fix.
Just a wish to have ArchiveGenerator
2011/2/13 Alexander Neundorf neund...@kde.org:
On Monday 07 February 2011, Alexander Neundorf wrote:
On Sunday 06 February 2011, Eric Noulard wrote:
2011/2/5 Alexander Neundorf neund...@kde.org:
Hi,
in general we keep cmake as backward compatible as possible, so no
builds
2011/2/23 Eric Noulard eric.noul...@gmail.com:
2011/2/23 Clinton Stimpson clin...@elemtech.com:
I've having problems with these tests too.
If they fail once, they will keep failing until some files generated by the
failed test are cleaned up.
Some files should be, the package files located
2011/3/4 Rolf Eike Beer e...@sf-mail.de:
Hi All,
I know that some new CPackRPM tests are failing
http://www.cdash.org/CDash/testDetails.php?test=86188713build=889597
the reason is the build path used contains space which cannot be handled
by rpmbuild...
I'll fix that tonight and avoid
Hi All,
As of CPack 2.8.4 the component support has been added to
ArchiveGenerator and RPM
(and NSIS and PackageMaker continue to support component packaging)
As explained here;
http://www.cmake.org/Wiki/CMake:Component_Install_With_CPack#CPack_Generator_specific_behavior
Currently NSIS and
My Last commit seems to have broken the CMake.CheckSourceTree test.
However I do not understand the issue shown here:
http://www.cdash.org/CDash/testDetails.php?test=87068196build=898608
What's wrong with my commit?
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
Hi All,
NCISome recently activayed CPackRPM tests
are failing on a SLES 10 x86_64 machine:
http://www.cdash.org/CDash/viewTest.php?onlyfailedbuildid=898471
would anybody here be able to run this test on a similar host
using 'next' branch for me?
I do not currently have access to such system and
2011/3/11 Rolf Eike Beer e...@sf-mail.de:
NCISome recently activayed CPackRPM tests
are failing on a SLES 10 x86_64 machine:
http://www.cdash.org/CDash/viewTest.php?onlyfailedbuildid=898471
would anybody here be able to run this test on a similar host
using 'next' branch for me?
I do not
2011/3/11 Eric Noulard eric.noul...@gmail.com:
2011/3/11 Rolf Eike Beer e...@sf-mail.de:
I can check on an openSUSE 11.0 tomorrow.
http://www.cdash.org/CDash/viewTest.php?onlyfailedbuildid=900169
If you want some quick changes come to #cmake on Freenode where I usually
hang around (Dakon
2011/3/12 Rolf Eike Beer e...@sf-mail.de:
Am Samstag 12 März 2011, 14:21:33 schrieb Eric Noulard:
2011/3/11 Eric Noulard eric.noul...@gmail.com:
2011/3/11 Rolf Eike Beer e...@sf-mail.de:
I can check on an openSUSE 11.0 tomorrow.
http://www.cdash.org/CDash/viewTest.php?onlyfailedbuildid
2011/3/13 Eric Noulard eric.noul...@gmail.com:
I'll try to [blindly] fix this with a SUSE specific test *in the test
itself* and not in CPack RPM.
I did push forward the stage CPackRPM-TestWithMoreTraces and merge it to next.
This last commit should make the CPackRPM test work on SUSE 64bits
2011/3/13 Rolf Eike Beer e...@sf-mail.de:
Am Sonntag 13 März 2011, 21:19:41 schrieb Eric Noulard:
2011/3/13 Eric Noulard eric.noul...@gmail.com:
I'll try to [blindly] fix this with a SUSE specific test *in the test
itself* and not in CPack RPM.
I did push forward the stage CPackRPM
2011/3/18 Bill Hoffman bill.hoff...@kitware.com:
The commits that went in this day:
http://www.cdash.org/CDash/viewChanges.php?project=CMakedate=2011-03-12
Caused memory leaks to show up here:
http://www.cdash.org/CDash/viewDynamicAnalysisFile.php?id=1142597
May be for me.
I'll have a
2011/3/18 Bill Hoffman bill.hoff...@kitware.com:
On 3/18/2011 11:00 AM, Eric Noulard wrote:
2011/3/18 Bill Hoffmanbill.hoff...@kitware.com:
The commits that went in this day:
http://www.cdash.org/CDash/viewChanges.php?project=CMakedate=2011-03-12
Caused memory leaks to show up here
2011/3/18 Bill Hoffman bill.hoff...@kitware.com:
On 3/18/2011 3:52 PM, Eric Noulard wrote:
Yes but this could be a real symptom a memory corruption.
What is the simplest way for me to run the same valgrind test locally?
Which ctest one line command, may use for that?
That said
2011/3/18 Eric Noulard eric.noul...@gmail.com:
2011/3/18 Bill Hoffman bill.hoff...@kitware.com:
On 3/18/2011 3:52 PM, Eric Noulard wrote:
Yes but this could be a real symptom a memory corruption.
What is the simplest way for me to run the same valgrind test locally?
Which ctest one line
2011/3/18 Eric Noulard eric.noul...@gmail.com:
2011/3/18 Eric Noulard eric.noul...@gmail.com:
2011/3/18 Bill Hoffman bill.hoff...@kitware.com:
On 3/18/2011 3:52 PM, Eric Noulard wrote:
Yes but this could be a real symptom a memory corruption.
What is the simplest way for me to run the same
2011/3/20 Bill Hoffman bill.hoff...@kitware.com:
On 3/19/2011 6:18 AM, Eric Noulard wrote:
I did just pushed the fix to stage.
I did change the cmCPackGenerator::ReadListFile return status in order
to return false if the list file read ends-up with an ERROR or
FATAL_ERROR.
I think
http://www.cdash.org/CDash/testDetails.php?test=88344080build=911504
My [too] naïve patch for automatic lib64 handling on Linux x86_64 has broken
[at least] SimpleInstall test.
I did push forward the branch in order to avoid automatic handling of lib64
the feature is still there but not
2011/5/20 Will Dicharry wdicha...@stellarscience.com:
Hi,
From the documentation at http://www.cmake.org/Wiki/CMake/Git#Topic_Stage
and at http://public.kitware.com/Wiki/Git/Workflow/Stage it's not clear to
me if I need to do anything after merging my topic branch into stage/next in
order to
2011/6/4 Alexander Neundorf neund...@kde.org:
Hi,
KDE is getting more modular, so instead of a few huge modules there will be
much more independent libraries.
We'll try to make all those libraries install proper FooConfig.cmake files.
Currently most of these libraries install already
2011/6/4 Alexander Neundorf neund...@kde.org:
Hi,
again from the KDE sprint...
We have around 150 cmake modules in kdelibs...
Several libraries are not before kdelibs, so they don't have access to
those.
So, what we came up with is that create a new package which just contains our
cmake
2011/6/4 Alexander Neundorf neund...@kde.org:
Hi,
again from the KDE sprint...
1) We have a macro
macro_optional_find_package().
The purpose is to be able to build without a specific package even if that
package is installed and would actually be found by the find_package() call.
2011/6/6 Alexander Neundorf neund...@kde.org:
On Sunday, June 05, 2011 11:50:50 PM Eric Noulard wrote:
2011/6/4 Alexander Neundorf neund...@kde.org:
Hi,
again from the KDE sprint...
1) We have a macro
macro_optional_find_package().
The purpose is to be able to build without
2011/6/6 Alexander Neundorf neund...@kde.org:
On Sunday, June 05, 2011 11:21:43 PM Eric Noulard wrote:
2011/6/4 Alexander Neundorf neund...@kde.org:
Hi,
KDE is getting more modular, so instead of a few huge modules there
will be much more independent libraries.
We'll try to make all
2011/6/7 Alexander Neundorf neund...@kde.org:
On Monday, June 06, 2011 03:26:03 PM Brad King wrote:
On 06/04/2011 06:30 AM, Alexander Neundorf wrote:
[...]
What do you think about adding the keyword OPTIONAL to add_subdirectory ?
Both have been proven useful, the one for find_package()
2011/6/7 Eric Noulard eric.noul...@gmail.com:
2011/6/7 Alexander Neundorf neund...@kde.org:
On Monday, June 06, 2011 03:26:03 PM Brad King wrote:
On 06/04/2011 06:30 AM, Alexander Neundorf wrote:
[...]
What do you think about adding the keyword OPTIONAL to add_subdirectory ?
Both have
2011/6/7 Werner Mahr wer...@vollstreckernet.de:
Hi,
after reading some stuff about integration of KDE-stuff into cmake, I
want to know your oppinion about manpages. At least on unix-based
systems it's an essential function of a build-environment to allow
installation of the docs.
My
2011/6/7 Michael Wild them...@gmail.com:
On 06/07/2011 07:40 PM, Werner Mahr wrote:
Michael Wild wrote:
[...]
I don't think that writing
stuff like this in many different projects is a good idea, that's why I
proposed to include it native in cmake.
ADD_EXECUTABLE(app, sources)
2011/6/14 Alan W. Irwin ir...@beluga.phys.uvic.ca:
On 2011-06-14 10:37+0800 feng.zhou wrote:
Hi
I cannot find insall packet in download list,only Solaris spack packet can
be found.How to solve this question ,thanks
Try building cmake from the source code using the bootstrap method
(i.e.
2011/7/6 Alexander Neundorf neund...@kde.org:
On Wednesday 06 July 2011, Eric Noulard wrote:
So, just go ahead with adding it as CHECK_CXX_SYMBOL_EXISTS() or
CHECK_SYMBOL_EXISTS_CXX() and if the macro name has no language in it, it
is implicitely C ?
I would rather go with a backward
2011/7/29 J Decker d3c...@gmail.com:
Any reason that environment variables can't be used as cmake
variables? Like of course any cmake variable in a script would
override the environment, but if it's not otherwise found, checking in
the environemnt would make scripts prettier.
set
Hi All,
Is target date for 2.8.6 fixed or is there any room left for late bug fix merge:
if there is some more room I may work on testing this contribution tonight
http://public.kitware.com/Bug/view.php?id=12063
If not I'll wait the release in order to avoid stage pollution.
--
Erk
Membre de
2011/9/20 David Cole david.c...@kitware.com:
Go ahead and push to the stage and merge to next when it's ready.
We're considering several topics for inclusion in the final release.
Done:
Merge topic 'CPackDeb-fakeroot' into next
49da3bd CPackDeb fix #10325 automagically use fakeroot for DEB
2011/10/7 Stephen Kelly steve...@gmail.com:
Stephen Kelly wrote:
Stephen Kelly wrote:
such that kwtyle is run as a pre-commit hook.
The instructions don't seem to work:
Oops, they do work. I had missed the part about creating a new repo in my
hooks dir.
:/
Not finding some conf
2011/11/1 Alexander Neundorf neund...@kde.org:
On Tuesday 01 November 2011, Eric Noulard wrote:
2011/11/1 Alexander Neundorf neund...@kde.org:
...
and I'd be very happy if this could be solved.
Me too.
I'll dig a little bit on the Eclipse side again, but generating 2
files in the source
2011/11/4 Rolf Eike Beer e...@sf-mail.de:
Am Freitag, 4. November 2011, 17:43:38 schrieb David Cole:
That wiki page says Authorized developers may push directly to the
official repository. But that is not all CMake developers... that is
Brad and I after we review your changes in next, pushed
Hi all,
I'm did do some work in order to enhance CPack builtin documentation
support.
see:
http://www.cmake.org/Bug/view.php?id=10067
this is located in stage branch ImproveCPackDoc.
I think the first two commits of this branch are ready for master
so I did merge it to next.
Those basically
2011/11/17 Brad King brad.k...@kitware.com:
On 11/15/2011 2:43 PM, Eric Noulard wrote:
The idea is to add extra CMake comment markup, i.e.
# CPACK_PACKAGE_NAME - The name of the package (or application). If
# not specified, defaults to the project name.
becomes:
##variable
List was dropped intentionally
-- Forwarded message --
From: Eric Noulard eric.noul...@gmail.com
Date: 2011/12/11
Subject: Re: [cmake-developers] Adding macro
cmake_print_variables(var1 var2 ... varN) ?
To: neund...@kde.org
2011/12/11 Alexander Neundorf neund...@kde.org:
Hi
2011/12/11 Eric Noulard eric.noul...@gmail.com:
List was dropped intentionally
Just realized I wrote the opposite of what I meant ...
-- Forwarded message --
From: Eric Noulard eric.noul...@gmail.com
Date: 2011/12/11
Subject: Re: [cmake-developers] Adding macro
Hi,
Now that 2.8.7 is out I'd like to continue my work on CPack
documentation improvement.
My branch on stage is: ImproveCPackDoc
I did merge it to next on nov 13:
22236e48938b942a8b9d95d73d447fa5e54e19a0
see http://public.kitware.com/Bug/view.php?id=10067 as well.
This topic has never been
2012/1/3 Brad King brad.k...@kitware.com:
On 1/2/2012 7:43 PM, Eric Noulard wrote:
I try to push forward the feature request:
http://public.kitware.com/Bug/view.php?id=10067
[snip]
Anybody have some time to try this?
I'd like to have some feedback before going on.
The branch is stage
2012/1/3 Eric Noulard eric.noul...@gmail.com:
2012/1/3 Brad King brad.k...@kitware.com:
On 1/2/2012 7:43 PM, Eric Noulard wrote:
I try to push forward the feature request:
http://public.kitware.com/Bug/view.php?id=10067
[snip]
Anybody have some time to try this?
I'd like to have some
2012/1/3 Brad King brad.k...@kitware.com:
On 1/3/2012 11:03 AM, Eric Noulard wrote:
stage/ImproveCPackDoc-part1
contains changes that do not add features but document existing ones.
This one looks good. Please merge to next.
It does not merge without conflict:
d2c9626 Document
2012/1/3 Brad King brad.k...@kitware.com:
On 1/3/2012 11:45 AM, Eric Noulard wrote:
this is due to the fact I did already merge it
(the beginning of the old stage/ImproveCPackDoc)
to next before 2.8.7 in the hope that it would be included in 2.8.7:
http://public.kitware.com/Bug/view.php?id
2012/1/3 Eric Noulard eric.noul...@gmail.com:
I did remove old ImproveCPackDoc from stage.
I did remove old CMake-completion-improvement from stage as well
and I'll push something clean without reference to potential cpack enhancement
in a new topic.
Done as well:
Merge topic 'CMake-bash
Hi All,
I have been giving wrong advice about the usage of CMAKE_FIND_ROOT_PATH
which seems to be reserved for cross-compiling whereas
CMAKE_PREFIX_PATH
CMAKE_INCLUDE_PATH
CMAKE_PROGRAM_PATH
CMAKE_LIBRARY_PATH
CMAKE_IGNORE_PATH
could someone enlight me about the intended relationship between
Sorry sent too soon, finger slipped.
...
I have been giving wrong advice about the usage of CMAKE_FIND_ROOT_PATH
which seems to be reserved for cross-compiling whereas
CMAKE_PREFIX_PATH
CMAKE_INCLUDE_PATH
CMAKE_PROGRAM_PATH
CMAKE_LIBRARY_PATH
CMAKE_IGNORE_PATH
are meant to be used in the
Hi Brad,
I've seen you are integrating new upstream libarchive today.
Any particular reason to pick-up 3.0.0-r3950 and
not some real version like 3.0.2 ?
I did notice that this particular version may unblock a pending CMake issue
related to symbolic link handling in zip files, see:
2012/1/3 Brad King brad.k...@kitware.com:
On 1/3/2012 4:07 PM, Eric Noulard wrote:
I've seen you are integrating new upstream libarchive today.
Any particular reason to pick-up 3.0.0-r3950 and
not some real version like 3.0.2 ?
3.0.2 wasn't out when I started that topic. I just took
Could anyone with appropriate knowledge of fixup_bundle internal
have a look at this bug:
http://public.kitware.com/Bug/view.php?id=12656
It may be windows specific.
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
--
Powered by www.kitware.com
The current comments in
Modules/CMakeRCInformation.cmake
looks like copy/paste from another file.
# This file sets the basic flags for the Fortran language in CMake.
# It also loads the available platform file for the system-compiler
# if it exists.
How would the seek for windres be related to
2012/1/24 Brad King brad.k...@kitware.com:
On 1/22/2012 7:58 AM, Eric Noulard wrote:
2012/1/3 Eric Noularderic.noul...@gmail.com:
back to cleaner way of work.
I did update and clean-up my previous attempt to ease documentation for
CPack.
http://public.kitware.com/Bug/view.php?id=10067
2012/1/25 Brad King brad.k...@kitware.com:
On 1/24/2012 5:50 PM, Eric Noulard wrote:
cmake --help-module CPackComponent
or any other (untouched module)
cmake --help-module FindQt4
you'll see that the extra space are there as well.
So yes there is too much space, but this is not due to
my
2012/1/25 Alexander Neundorf neund...@kde.org:
On Wednesday 25 January 2012, Eric Noulard wrote:
cmake already supports CMAKE_MODULE_PATH for generating help, e.g. like this:
$ cmake -DCMAKE_MODULE_PATH=$HOME/src/kdelibs/cmake/modules/ --help-custom-
modules
This generates docs for all
2012/1/25 Brad King brad.k...@kitware.com:
On 1/25/2012 3:20 PM, Eric Noulard wrote:
So with my proposal you can perfectly document a script in the middle
of the file or as usual just in front of the concerned
macro/function/var. This may be easier for doc maintenance because
the function
2012/1/31 Rolf Eike Beer e...@sf-mail.de:
Ok Agreed.
Just merged the branch to next.
Just spotted a bug in it:
@@ -559,6 +511,8 @@ bool cmDocumentation::CreateSingleModule(const char*
fname,
{
if(line.size() line[0] == '#')
{
+ /* line beginnings with ## are mark-up
2012/1/31 Eric Noulard eric.noul...@gmail.com:
2012/1/31 Rolf Eike Beer e...@sf-mail.de:
Ok Agreed.
Just merged the branch to next.
Just spotted a bug in it:
@@ -559,6 +511,8 @@ bool cmDocumentation::CreateSingleModule(const char*
fname,
{
if(line.size() line[0
2012/2/1 Eric Noulard eric.noul...@gmail.com:
2012/2/1 David Cole david.c...@kitware.com:
On Wed, Feb 1, 2012 at 2:27 AM, Rolf Eike Beer e...@sf-mail.de wrote:
Am Dienstag, 31. Januar 2012, 23:39:30 schrieb Eric Noulard:
2012/1/31 Rolf Eike Beer e...@sf-mail.de:
Eric Noulard wrote:
2012/1
2012/2/1 David Cole david.c...@kitware.com:
There's no rush here. We won't be reviewing your changes again until
next Tuesday at this point...
Hi all,
I did push the work and the branch a little further yesterday.
I didn't get any big red on the dashboard this time and I think
it was worth
2012/2/6 David Cole david.c...@kitware.com:
On Sun, Feb 5, 2012 at 6:50 PM, Eric Noulard eric.noul...@gmail.com wrote:
2012/2/1 David Cole david.c...@kitware.com:
There's no rush here. We won't be reviewing your changes again until
next Tuesday at this point...
Hi all,
I did push the work
David Cole david.c...@kitware.com:
My unmerged commit:
commit 6a74eb1d36b079fe6b566244a636ac1e43303aa6
Author: Eric NOULARD eric.noul...@gmail.com
Date: Sun Feb 5 13:13:48 2012 +0100
3 days!!
Just kidding but...
Thanks -- that will make our weekly merge sessions easier to do when we
don't
2012/2/15 Rolf Eike Beer e...@sf-mail.de:
Hi,
as I found out today this construct doesn't work:
find_library(MYLIB libfoo.so.2)
This is because find_library will only try to access the whole path if the
given name matches PREFIX.*SUFFIX, which is obviously not the case here. My
simple
2012/2/15 Brad King brad.k...@kitware.com:
On 2/15/2012 9:18 AM, Eric Noulard wrote:
If the user does not trust find_library for checking proper extension
then:
1) He could modify/append CMAKE_FIND_LIBRARY_SUFFIXES
in this case:
list(APPEND CMAKE_FIND_LIBRARY_SUFFIXES
2012/2/16 Brad King brad.k...@kitware.com:
On 2/16/2012 3:29 PM, Eric Noulard wrote:
What are you targeting?
install-time i.e. make install usage?
package install time prodduced with cpack usage?
package install time NOT produced with cpack usage?
a subset of this?
The goal
2012/2/16 Brad King brad.k...@kitware.com:
On 2/16/2012 4:13 PM, David Cole wrote:
On Thu, Feb 16, 2012 at 3:52 PM, Eric Noulard eric.noul...@gmail.com
mailto:eric.noul...@gmail.com wrote:
I'm not convinced, yet I'll have to try with the example provided by
Alex
by adding proper CPack
2012/2/17 Alexander Neundorf neund...@kde.org:
On Thursday 16 February 2012, Brad King wrote:
On 2/16/2012 1:24 PM, Alexander Neundorf wrote:
Actually I expected I would prefer this over the fixed names, but now
that I've done it and look at what Config.cmake.in file I have to write,
I
2012/2/17 Stephen Kelly steve...@gmail.com:
Hi there,
Also in this thread one of the discussion topics was making CMake default to
creating Gui-ready executables. That is, setting the WIN32_EXECUTABLE or
MACOSX_BUNDLE property on the executable target.
2012/2/17 Alexander Neundorf neund...@kde.org:
On Friday 17 February 2012, Eric Noulard wrote:
2012/2/17 Alexander Neundorf neund...@kde.org:
On Thursday 16 February 2012, Brad King wrote:
On 2/16/2012 1:24 PM, Alexander Neundorf wrote:
Actually I expected I would prefer this over
2012/2/17 Stephen Kelly steve...@gmail.com:
Marcel Loose wrote:
Hi Stephen,
On Fri, 2012-02-17 at 12:06 +0100, Stephen Kelly wrote:
-- 8 8 8 8 8 8 8 8 8 --
diff --git a/templates/tests/CMakeLists.txt
b/templates/tests/CMakeLists.txt
index
2012/2/17 Eric Noulard eric.noul...@gmail.com:
2012/2/17 Alexander Neundorf neund...@kde.org:
On Friday 17 February 2012, Eric Noulard wrote:
2012/2/17 Alexander Neundorf neund...@kde.org:
On Thursday 16 February 2012, Brad King wrote:
On 2/16/2012 1:24 PM, Alexander Neundorf wrote
Hi all,
I'm pursuing my quest for a better CPack doc.
First set of modifications are in master:
cpack --help-command-xxx
cpack --help-variable-xxx
works.
However variables are somehow problematic because I get all the
properties defined for CMake in the doc because variables are a
special kind
My recent commit on CPack-dynamicDocSection
http://cmake.org/gitweb?p=cmake.git;a=shortlog;h=e175af3e74006e6f3a4fdaead20522b29034c45b
may have broken this build
http://open.cdash.org/testDetails.php?test=135708291build=2018382
the trouble is I cannot imagine why, since most of the modification
2012/2/18 Eric Noulard eric.noul...@gmail.com:
2012/2/18 Alexander Neundorf neund...@kde.org:
On Saturday 18 February 2012, Eric Noulard wrote:
Hi all,
I'm pursuing my quest for a better CPack doc.
First set of modifications are in master:
cpack --help-command-xxx
cpack --help-variable
1 - 100 of 214 matches
Mail list logo
