Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
http://public.kitware.com/Bug/view.php?id=8996 On Wed, Nov 7, 2012 at 8:40 PM, David Cole wrote: > Hi all, > > Replies requested. Short replies only. Read on. Just a short reply > with bug numbers or links to the bugs is all we need here. > > Example one-line reply: > > http://public.kitware.com/Bug/view.php?id=13571 > > Please move specific discussions into the bugs themselves or start a > new thread to talk about it... Replies on this thread should just be a > collector for bug numbers. > > We are aiming for approximately quarterly releases from now on, > scheduling them every 3 to 4 months. The next release of CMake will > likely be version 2.8.11, scheduled to have an "rc1" release candidate > on Wed. January 9, 2013 -- just 9 weeks from today. > > If you have a particular issue that you think should be fixed for > inclusion in 2.8.11, please bring it up within the next two weeks. > Ideally, each issue will be discussed as needed on the mailing list to > come to any consensus about what should be done to fix it, and then an > entry in the bug tracker may be used to keep it on the radar screen, > and to track activity related to it. You can see what's already on the > roadmap for this release here: > > http://public.kitware.com/Bug/roadmap_page.php?version_id=103 > > Patches are always welcome. Patches that include testing of any new > features, or tests that prove a bug is really fixed on the dashboards, > (basically any patch with testing) is preferred over a patch with no > testing. Also, if you are *adding* code, then you also probably need > to add *tests* of that code, so that the coverage percentage stays as > is or rises. > > Please discuss issues here as needed, and add notes to existing issues > in the bug tracker that you are interested in seeing fixed -- we will > be looking at the mailing list and activity in the bug tracker to help > prioritize the bug fixes that will occur in the near future. > > > Thanks, > David Cole > Kitware, Inc. > > > P.S. - as a nice summary of what we accomplished in the CMake 2.8.10 > release, see here: > http://public.kitware.com/Bug/changelog_page.php?version_id=100 -- it > currently lists 58 issues that we resolved: nice job, everybody! > > (Many of those were specifically addressed because somebody asked for > it right here on the mailing list... Don't be shy!) > -- > > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers > -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
On Wednesday 07 November 2012, David Cole wrote: > Hi all, > > Replies requested. Short replies only. Read on. Just a short reply > with bug numbers or links to the bugs is all we need here. > > Example one-line reply: > > http://public.kitware.com/Bug/view.php?id=13571 http://public.kitware.com/Bug/view.php?id=8170 http://public.kitware.com/Bug/view.php?id=9905 http://public.kitware.com/Bug/view.php?id=11536 Alex -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
2010/7/5 David Cole : > Hi all, > Now that we have released CMake 2.8.2 last Monday, and we have switched to > this new workflow using branches in the git repository, *now* would be a > great time to prioritize bug fixes for the next release of CMake. > We are leaning towards quarterly releases from now on, scheduling them every > 3 months. That would make the next release of CMake version 2.8.3 and > scheduled to have an "rc1" release candidate in approximately mid-September, > 2010. > If you have a particular issue that you think should be fixed for inclusion > in 2.8.3, please bring it up now. Ideally, each issue will be discussed as > needed on the mailing list to come to any consensus about what should be > done to fix it, and then an entry in the bug tracker may be used to keep it > on the radar screen, and to track activity related to it. > Patches are always welcome. Patches that include testing of any new > features, or tests that prove a bug is really fixed on the dashboards, > basically any patch with testing is preferred over a patch with no testing. > Also, if you are *adding* code, then you also probably need to add *tests* > of that code, so that the coverage percentage stays as is or rises. > Please discuss issues here as needed, and add notes to existing issues in > the bug tracker that you are interested in seeing fixed for 2.8.3 -- we will > be looking at the mailing list and activity in the bug tracker to help > prioritize the bug fixes that will occur in the next several weeks. > > Thanks, > David Cole > Kitware, Inc. So here goes my own list. I'd like to fix 2 annoying relatively long-standing bugs: 1) "Make CPack generic generator delegate the name of the file to specific generator" http://public.kitware.com/Bug/view.php?id=9900 (may be fixed together with http://public.kitware.com/Bug/view.php?id=10736) 2) CPack RPM generator should always "CPACK_SET_DESTDIR" http://public.kitware.com/Bug/view.php?id=7000 1) Should come first because it will help fix others "depending" bugs related to this one and makes it possible to use "standard" package name for at least RPM and DEB. May be it can be fixed together with http://public.kitware.com/Bug/view.php?id=10736. The idea would be for the CPack generic generator to offer a "new compresFiles API" in which the name of the package is both an input AND an output. Moreover the output should be a vector of filenames and not a single filename. 2) In the same way this one is blocking some pending features for CPackRPM (or CPackDEB) and the issue is raising from time to time on the list. May be interested people could add themselves to the monitor list of those bugs. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
I am not sure if this is a reported bug (I can report it now if it isn't reported already). Using ExternalProject with a git repo and specifying a sha1 revision via GIT_TAG will blow away the entire source directory whenever the revision is changed. This leads to complete rebuilds of said project. On Thu, Nov 4, 2010 at 3:34 PM, David Cole wrote: > Hi all, > > Now that we have released CMake 2.8.3, *now* would be a great time to > prioritize bug fixes for the next release of CMake. > > Replies requested. Read on. *Just a short reply with bug numbers* or links > to the bugs is all we need here. Please move specific discussions into the > bugs themselves or start a new thread to talk about it... Replies on this > thread should just be a collector for bug numbers. > > We are aiming for quarterly releases from now on, scheduling them every 3 > or 4 months. That would make the next release of CMake version 2.8.4 and > scheduled to have an "rc1" release candidate in approximately mid-January, > 2011, target date: Wed. 1/12/2011. > > If you have a particular issue that you think should be fixed for inclusion > in 2.8.4, please bring it up now. Ideally, each issue will be discussed as > needed on the mailing list to come to any consensus about what should be > done to fix it, and then an entry in the bug tracker may be used to keep it > on the radar screen, and to track activity related to it. > > Patches are always welcome. Patches that include testing of any new > features, or tests that prove a bug is really fixed on the dashboards, > basically any patch with testing is preferred over a patch with no testing. > Also, if you are *adding* code, then you also probably need to add *tests* > of that code, so that the coverage percentage stays as is or rises. > > Please discuss issues here as needed, and add notes to existing issues in > the bug tracker that you are interested in seeing fixed for 2.8.4 -- we will > be looking at the mailing list and activity in the bug tracker to help > prioritize the bug fixes that will occur in the next several weeks. > > > Thanks, > David Cole > Kitware, Inc. > > > P.S. - as a nice summary of what we've accomplished in the CMake 2.8.3 > release, see here: http://public.kitware.com/Bug/changelog_page.php > -- it lists 89 issues that we resolved: nice job, everybody! > > (About 45 of those were specifically addressed because somebody brought it > up in response to my similar email from just after 2.8.2... Don't be shy!) > > ___ > cmake-developers mailing list > cmake-developers@cmake.org > http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers > > ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
VS 2010 CMake plugin is broken http://www.vtk.org/Bug/view.php?id=11258 This is a problem for projects such as mine where I have dozens of projects in my solution and they can change rather frequently, especially with my FindCUDA.cmake script that computes dependencies and then changes the VS projects. Thanks, James ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
On Thursday 04 November 2010, David Cole wrote: > Hi all, > > Now that we have released CMake 2.8.3, *now* would be a great time to > prioritize bug fixes for the next release of CMake. > > Replies requested. Read on. *Just a short reply with bug numbers* or links > to the bugs is all we need here. Please move specific discussions into the > bugs themselves or start a new thread to talk about it... Replies on this > thread should just be a collector for bug numbers. I'd like to have * dependencies to imported targets (#10395) * the localized bison fix which is already in next * #10176 - support for the IAR toolchain This should be like 90% done I think, in the branch AddIARSupport on staging, AFAIK there are only some whitespace escaping issues left, but the reporters are not cmake expert enough to find the correct escaping. The IAR compiler can be downloaded for free after registering (did that), but I didn't get it installed in a ReactOS in a VM. Didn't try Wine yet. Don't have a real Windows (and don't want one). * support for Windows CE (#7919, #8486) * support for Symbian (#8486) There are two approaches, one to make the Makefile generators support Symbian (I have a basically working patch for one version of Symbian with one toolchain), and one for a special symbian project generator (for their weird project files). I prefer the makefile based one ;-) What I'll be trying to get into 2.8.4 * prefer CMAKE_ROOT over CMAKE_MODULE_PATH when included from CMAKE_ROOT (branch PreferCMakeModulesByCMakeModulesWithPolicy in staging) How do we proceed with this ? * #10069, branch AddASM_NASMSupport in staging * #8392 - passing asm files by default through the C compiler (discussed this here with Brad already) * improved support for graphviz Alex ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
Hi David, I've got one more, one that I just entered in Mantis. #11410 - Result of IF() is inconsistent Regards, Marcel Loose. ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
When using external_project, if GIT_TAG is modified the entire source tree is removed and re-cloned causing a full rebuild of said project. http://cmake.org/Bug/view.php?id=11403 On Tue, Mar 29, 2011 at 1:56 PM, David Cole wrote: > Hi all, > > Now that we have released CMake 2.8.4, *now* would be a great time to > prioritize bug fixes for the next release of CMake. > > Replies requested. Read on. *Just a short reply with bug numbers* or links > to the bugs is all we need here. Please move specific discussions into > the bugs themselves or start a new thread to talk about it... Replies on > this thread should just be a collector for bug numbers. > > We are aiming for quarterly releases from now on, scheduling them every 3 > or 4 months. That would make the next release of CMake version 2.8.5, > scheduled > to have an "rc1" release candidate on Wed. April 27, 2011. > > If you have a particular issue that you think should be fixed for inclusion > in 2.8.5, please bring it up by the end of this week. Ideally, each issue > will be discussed as needed on the mailing list to come to any consensus > about what should be done to fix it, and then an entry in the bug tracker > may be used to keep it on the radar screen, and to track activity related to > it. > > Patches are always welcome. Patches that include testing of any new > features, or tests that prove a bug is really fixed on the dashboards, > basically any patch with testing is preferred over a patch with no testing. > Also, if you are *adding* code, then you also probably need to add *tests* > of that code, so that the coverage percentage stays as is or rises. > > Please discuss issues here as needed, and add notes to existing issues in > the bug tracker that you are interested in seeing fixed for 2.8.5 -- we > will be looking at the mailing list and activity in the bug tracker to help > prioritize the bug fixes that will occur over the next 4 weeks. > > > Thanks, > David Cole > Kitware, Inc. > > > P.S. - as a nice summary of what we accomplished in the CMake 2.8.4 > release, see here: http://public.kitware.com/Bug/changelog_page.php > -- it currently lists 127 issues that we resolved: nice job, everybody! > > (Many of those were specifically addressed because somebody brought it up > in response to my similar email from just after 2.8.3... Don't be shy!) > > > ___ > cmake-developers mailing list > cmake-developers@cmake.org > http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers > > ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
Am Dienstag 29 März 2011, 19:56:03 schrieb David Cole: > Hi all, > > Now that we have released CMake 2.8.4, *now* would be a great time to > prioritize bug fixes for the next release of CMake. > > Replies requested. Read on. *Just a short reply with bug numbers* or links > to the bugs is all we need here. Please move specific discussions into the > bugs themselves or start a new thread to talk about it... Replies on this > thread should just be a collector for bug numbers. The simple answer is as always: fix all bugs I submitted ;) http://www.cmake.org/Bug/view.php?id=11333 FindThreads incorrectly adds -pthread to linker options http://www.cmake.org/Bug/view.php?id=7830 Likely a dupe of the above http://www.cmake.org/Bug/view.php?id=12054 FindJava.cmake too noisy on second run http://www.cmake.org/Bug/view.php?id=10740 This has been fixed in 2.8.4, but the doc update was not committed http://www.cmake.org/Bug/view.php?id=10476 No program output if CTest aborts test with timeout http://www.cmake.org/Bug/view.php?id=11792 Improve handling of CTEST_SITE http://www.cmake.org/Bug/view.php?id=11792 Code comments for many commands are wrong (copy&paste) http://www.cmake.org/Bug/view.php?id=8466 Provide finer control than pass/fail for a test program Here are also some bugs that are resolved and can be closed as they are fixed in 2.8.4: http://www.cmake.org/Bug/view.php?id=11362 http://www.cmake.org/Bug/view.php?id=11329 http://www.cmake.org/Bug/view.php?id=11791 Eike ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
As an esteemed colleague has pointed out, those with "reporter" level account in Mantis may not edit bugs other than their own directly. So. if you are in that boat, but would like to vote for a bug fix to be considered for 2.8.7, please reply to this thread, and just list the bug number, or a URL linking to its bug tracker page. I will follow the replies to this thread and add those bugs to the roadmap as they roll in. Thanks, David C. On Fri, Oct 21, 2011 at 12:19 PM, David Cole wrote: > Hi all, > > *NO* replies requested. Different technique this time. Please edit the > bug tracker directly. (Unless you have problems with the bug tracker: > if so, please feel free to reply here with your suggestions.) > > We are planning for CMake 2.8.7, aiming for a December release. We're > targeting Dec. 28, 2011 for releasing it, and in order to make that > happen we'll have to do an "rc1" by Dec. 7th or so... about 7 weeks > from now. > > If you have a particular issue that you think should be fixed for > inclusion in 2.8.7, please put it on the roadmap yourself by the end > of next week, Fri. Oct. 28th. To do so, edit the bug at > http://public.kitware.com/Bug and set the "Target Version" field to > "CMake 2.8.7" - that will make it appear on the roadmap page ( > http://www.cmake.org/Bug/roadmap_page.php?version_id=89 ). Also: add a > note saying why it's important to you, or even add a patch that fixes > and documents and tests it if you're able to. > > Ideally, each issue will be discussed as needed on the mailing list to > come to any consensus about what should be done to fix it, and then > the entry in the bug tracker may be used to keep it on the radar > screen, and to track activity related to it. > > Patches are *always* welcome. Patches that include testing of any new > features, or tests that prove a bug is really fixed on the dashboards > are better: a patch with testing is strongly preferred over a patch > with no testing. Also, if you are *adding* code, then you also > probably need to add *tests* of that code, so that the coverage > percentage stays as is or rises. > > Please discuss issues here on the mailing list as needed, and add > notes to existing issues in the bug tracker that you are interested in > seeing fixed for 2.8.7 -- we will be looking at activity both on the > mailing list and in the bug tracker to help prioritize the bug fixes > for the next couple months. > > > Thanks, > David Cole > Kitware, Inc. > > > P.S. - as a nice summary of what we accomplished in the CMake 2.8.6 > release, including contributions from 27 individuals around the world, > see here: http://public.kitware.com/Bug/changelog_page.php?version_id=87 > -- it currently lists 43 issues that we resolved: nice job, everybody! > > (Many of those were specifically addressed because somebody brought it > up in response to my similar email from just after 2.8.5... Don't be > shy!) > -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
On 2011-10-21 20:20, David Cole wrote: As an esteemed colleague has pointed out, those with "reporter" level account in Mantis may not edit bugs other than their own directly. So. if you are in that boat, but would like to vote for a bug fix to be considered for 2.8.7, please reply to this thread, and just list the bug number, or a URL linking to its bug tracker page. I will follow the replies to this thread and add those bugs to the roadmap as they roll in. The VS2010 bug! http://public.kitware.com/Bug/view.php?id=11258 Thomas -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
Reminder: Please make your requests for bug fixes for CMake 2.8.7 by the end of the day, this Friday, October 28. It will be nice to have as complete a picture as possible so we can plan the next 6 weeks effectively. Thanks, David On Fri, Oct 21, 2011 at 2:20 PM, David Cole wrote: > As an esteemed colleague has pointed out, those with "reporter" level > account in Mantis may not edit bugs other than their own directly. > So. if you are in that boat, but would like to vote for a bug fix > to be considered for 2.8.7, please reply to this thread, and just list > the bug number, or a URL linking to its bug tracker page. > > I will follow the replies to this thread and add those bugs to the > roadmap as they roll in. > > > Thanks, > David C. > > > On Fri, Oct 21, 2011 at 12:19 PM, David Cole wrote: >> Hi all, >> >> *NO* replies requested. Different technique this time. Please edit the >> bug tracker directly. (Unless you have problems with the bug tracker: >> if so, please feel free to reply here with your suggestions.) >> >> We are planning for CMake 2.8.7, aiming for a December release. We're >> targeting Dec. 28, 2011 for releasing it, and in order to make that >> happen we'll have to do an "rc1" by Dec. 7th or so... about 7 weeks >> from now. >> >> If you have a particular issue that you think should be fixed for >> inclusion in 2.8.7, please put it on the roadmap yourself by the end >> of next week, Fri. Oct. 28th. To do so, edit the bug at >> http://public.kitware.com/Bug and set the "Target Version" field to >> "CMake 2.8.7" - that will make it appear on the roadmap page ( >> http://www.cmake.org/Bug/roadmap_page.php?version_id=89 ). Also: add a >> note saying why it's important to you, or even add a patch that fixes >> and documents and tests it if you're able to. >> >> Ideally, each issue will be discussed as needed on the mailing list to >> come to any consensus about what should be done to fix it, and then >> the entry in the bug tracker may be used to keep it on the radar >> screen, and to track activity related to it. >> >> Patches are *always* welcome. Patches that include testing of any new >> features, or tests that prove a bug is really fixed on the dashboards >> are better: a patch with testing is strongly preferred over a patch >> with no testing. Also, if you are *adding* code, then you also >> probably need to add *tests* of that code, so that the coverage >> percentage stays as is or rises. >> >> Please discuss issues here on the mailing list as needed, and add >> notes to existing issues in the bug tracker that you are interested in >> seeing fixed for 2.8.7 -- we will be looking at activity both on the >> mailing list and in the bug tracker to help prioritize the bug fixes >> for the next couple months. >> >> >> Thanks, >> David Cole >> Kitware, Inc. >> >> >> P.S. - as a nice summary of what we accomplished in the CMake 2.8.6 >> release, including contributions from 27 individuals around the world, >> see here: http://public.kitware.com/Bug/changelog_page.php?version_id=87 >> -- it currently lists 43 issues that we resolved: nice job, everybody! >> >> (Many of those were specifically addressed because somebody brought it >> up in response to my similar email from just after 2.8.5... Don't be >> shy!) >> > -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
0010476 No program output if CTest aborts test with timeout 0010941 Code comments for many commands are wrong (copy&paste) 0012054 FindJava.cmake too noisy on second run 0010740 STRING(SUBSTRING) should work with length -1 0009658 FindQt4.cmake depends on C language These is fixed AFAICT and should be closed 0011333 FindThreads incorrectly adds -pthread to linker options This was in last time until we found out that CHECK_SYMBOL_EXISTS is unreliable which caused this to be broken. 0011792 Improve handling of CTEST_SITE 0008466 Provide finer control than pass/fail for a test program 0012441 No progress reporting for add_custom_command signature.asc Description: This is a digitally signed message part. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
On Fri, Oct 28, 2011 at 12:13 PM, Rolf Eike Beer wrote: > 0010476 No program output if CTest aborts test with timeout > 0010941 Code comments for many commands are wrong (copy&paste) > 0012054 FindJava.cmake too noisy on second run > 0010740 STRING(SUBSTRING) should work with length -1 > 0009658 FindQt4.cmake depends on C language > > These is fixed AFAICT and should be closed > They are all marked as "resolved" now. I leave "resolved" bugs open for 4 months after they are marked as such in order to give the original reporters time to re-open them if they disagree with the resolution, or in case a problem comes back. Once a month, I close out bugs that have been resolved for more than 4 months with no new updates. They'll be closed when they pass that threshold. > > 0011333 FindThreads incorrectly adds -pthread to linker options > > This was in last time until we found out that CHECK_SYMBOL_EXISTS is > unreliable which caused this to be broken. > > 0011792 Improve handling of CTEST_SITE > 0008466 Provide finer control than pass/fail for a test program > 0012441 No progress reporting for add_custom_command > I've added these to the roadmap, ...with the exception of http://public.kitware.com/Bug/view.php?id=8466 -- I'm not going to consider 8466 further until somebody attaches a concrete proposal to it in the form a fully documented, fully tested patch. I don't think it's a reasonable request. If somebody out there cares enough about it, then please, by all means, attach a patch to it and let's discuss further. I don't think giving special treatment and status to "77", one possible value out of 4 billion integer return values is reasonable. Thanks, David > -- > > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers > -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
