Re: [CMake] Bug fix requests for the *next* release of CMake...

[Nick Hutchinson]

http://public.kitware.com/Bug/view.php?id=13574


On 8/11/2012, at 5:39 PM, cmake-requ...@cmake.org wrote:

> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of 
> David Cole
> Sent: mercredi 7 novembre 2012 20:41
> To: cmake; CMake Developers
> Subject: [CMake] Bug fix requests for the *next* release of CMake...
> 
> 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://www.cmake.org/mailman/listinfo/cmake
> 
> 
> 

--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Glenn Coombs]

http://www.cmake.org/Bug/view.php?id=12437 (do not set default stacksize of
10MB for Visual Studio)

--
Glenn
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Gregoire Aujay]

http://www.cmake.org/Bug/view.php?id=13643

Fix is included in the issue but I do not know we could easily add a test.

Regards,
Gregoire


-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of 
David Cole
Sent: mercredi 7 novembre 2012 20:41
To: cmake; CMake Developers
Subject: [CMake] Bug fix requests for the *next* release of CMake...

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://www.cmake.org/mailman/listinfo/cmake


--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Clifford Yapp]

http://public.kitware.com/Bug/view.php?id=11575


On Wed, Nov 7, 2012 at 2: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://www.cmake.org/mailman/listinfo/cmake
>
--

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://www.cmake.org/mailman/listinfo/cmake

[CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

kitware-provided CMake installer/executables should be codesigned with 
'Developer ID' for GateKeeper on OS X



--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Xavier Besseron]

Sorry for this late reply.

http://public.kitware.com/Bug/view.php?id=12630 - "Support for SVN
externals in CTest update"

I will resume the discussion about this issue in the mailing list.

Xavier


On Fri, Aug 10, 2012 at 10:47 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=13463
>
> 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.10, scheduled to have an "rc1" release candidate
> on Wed. October 17, 2012 -- just 9 weeks from next Wednesday.
>
> If you have a particular issue that you think should be fixed for
> inclusion in 2.8.10, 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 on the roadmap
> for this release here:
> http://public.kitware.com/Bug/roadmap_page.php?version_id=100
>
> 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.9
> release, see here:
> http://public.kitware.com/Bug/changelog_page.php?version_id=93 -- it
> currently lists 74 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://www.cmake.org/mailman/listinfo/cmake
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Golub]

http://www.cmake.org/Bug/view.php?id=13202
http://www.cmake.org/Bug/view.php?id=13203

-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
David Cole
Sent: Friday, August 10, 2012 4:48 PM
To: cmake
Subject: [CMake] Bug fix requests for the *next* release of CMake...

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=13463

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.10, scheduled to have an "rc1" release candidate on Wed. October 17,
2012 -- just 9 weeks from next Wednesday.

If you have a particular issue that you think should be fixed for inclusion
in 2.8.10, 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 on the roadmap for this release
here:
http://public.kitware.com/Bug/roadmap_page.php?version_id=100

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.9 release,
see here:
http://public.kitware.com/Bug/changelog_page.php?version_id=93 -- it
currently lists 74 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://www.cmake.org/mailman/listinfo/cmake

--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

On Mon, Aug 13, 2012 at 12:07 PM, Alexander Neundorf
 wrote:
> On Friday 10 August 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=13463
>
> Personally I would prefer this link together with the title of the bug -
> makes it much faster to see what the bug is about:
>
> http://public.kitware.com/Bug/view.php?id=12621 - "Compatibility with Xcode
> 4.3"
>
> Alex

Adding the title would be fine with me. Although that does introduce
some data duplication. Even in this context, that's a little bit evil.
In the case of people making typos in the bug number or the title,
please clarify which one they're talking about before adding to the
roadmap. :-)
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Alexander Neundorf]

On Friday 10 August 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=13463

Personally I would prefer this link together with the title of the bug - makes 
it much faster to see what the bug is about:

http://public.kitware.com/Bug/view.php?id=12621 - "Compatibility with Xcode 
4.3"

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Johannes Zarl]

http://public.kitware.com/Bug/view.php?id=12373
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Dave Abrahams]

http://www.cmake.org/Bug/view.php?id=13204
http://www.cmake.org/Bug/view.php?id=13162 

-- 
Dave Abrahams
BoostPro Computing  Software DevelopmentTraining
http://www.boostpro.com Clang/LLVM/EDG Compilers  C++  Boost


--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Clifford Yapp]

http://public.kitware.com/Bug/view.php?id=11575
--

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://www.cmake.org/mailman/listinfo/cmake

[CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

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=13463

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.10, scheduled to have an "rc1" release candidate
on Wed. October 17, 2012 -- just 9 weeks from next Wednesday.

If you have a particular issue that you think should be fixed for
inclusion in 2.8.10, 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 on the roadmap
for this release here:
http://public.kitware.com/Bug/roadmap_page.php?version_id=100

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.9
release, see here:
http://public.kitware.com/Bug/changelog_page.php?version_id=93 -- it
currently lists 74 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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

Support for Xcode 4.3 (sic)



--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Stephen Kelly]

David Cole wrote:
> Replies requested. Short replies only. 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.
> 

http://public.kitware.com/Bug/view.php?id=12588
Discussion: 
http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/2285/focus=2299

Thanks,

--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Orion Poplawski]

On 01/23/2012 11:29 AM, Rolf Eike Beer wrote:

Theodore Papadopoulo wrote:

I do not know if it is too late to require bugfix for the next release
or even whether this bug is known (a quick browsing of buzilla shows
nothing and the git sources still contain the bug), but in any case.

In cmake-2.8.6, the module FindLAPACK.cmake contains the lines:

if (CMAKE_SYSTEM_NAME STREQUAL "Linux")
# for ubuntu's libblas3gf and liblapack3gf packages
set(CMAKE_FIND_LIBRARY_SUFFIXES ${CMAKE_FIND_LIBRARY_SUFFIXES} .so.3gf)
endif ()


AFAICS this just adds another suffix, but will not remove an existing one, so
this should not make anything go undetected that was detected before. You can
try yourself if you just comment out this lines.

I think this may be something entirely different, that I have seen today for
completely unrelated modules: if the library is in /usr/lib64 like on my
openSuSE 12.1, the library is sometimes not detected. When trying it on my
machine at home it works like a charm. I've not entirely understood what was
wrong there and had no time yet to debug this.


It's a typo in 2.8.6 fixed in 2.8.7:


$ diff ./cmake-2.8.6/Modules/FindLAPACK.cmake 
./cmake-2.8.7/Modules/FindLAPACK.cmake

83c83
< set(CMAKE_FIND_LIBRARY_SUFFIXES .lib ${CMAKE_FIND_LIBRRAY_SUFFIXES})
---
> set(CMAKE_FIND_LIBRARY_SUFFIXES .lib ${CMAKE_FIND_LIBRARY_SUFFIXES})
86c86
< set(CMAKE_FIND_LIBRARY_SUFFIXES .lib ${CMAKE_FIND_LIBRRAY_SUFFIXES})
---
> set(CMAKE_FIND_LIBRARY_SUFFIXES .lib ${CMAKE_FIND_LIBRARY_SUFFIXES})
88c88
< set(CMAKE_FIND_LIBRARY_SUFFIXES .a ${CMAKE_FIND_LIBRRAY_SUFFIXES})
---
> set(CMAKE_FIND_LIBRARY_SUFFIXES .a ${CMAKE_FIND_LIBRARY_SUFFIXES})
93c93
< set(CMAKE_FIND_LIBRARY_SUFFIXES ${CMAKE_FIND_LIBRRAY_SUFFIXES} 
.so.3gf)
---
> set(CMAKE_FIND_LIBRARY_SUFFIXES ${CMAKE_FIND_LIBRARY_SUFFIXES} 
.so.3gf)

May be time to push 2.8.7 to F16.


--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder Office  FAX: 303-415-9702
3380 Mitchell Lane  or...@cora.nwra.com
Boulder, CO 80301  http://www.cora.nwra.com
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Dan Kegel]

On Mon, Jan 2, 2012 at 9:11 AM, David Cole  wrote:
> Replies requested. Short replies only. Read on. Just a short reply
> with bug numbers or links to the bugs is all we need here.

Two easy ones (sorry they're late, but they're really small, and would
help java support on ubuntu):
http://public.kitware.com/Bug/view.php?id=12878
http://public.kitware.com/Bug/view.php?id=12880
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Theodore Papadopoulo]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 01/23/2012 07:29 PM, Rolf Eike Beer wrote:
> Theodore Papadopoulo wrote:
>> I do not know if it is too late to require bugfix for the next
>> release or even whether this bug is known (a quick browsing of
>> buzilla shows nothing and the git sources still contain the bug),
>> but in any case.
>> 
>> In cmake-2.8.6, the module FindLAPACK.cmake contains the lines:
>> 
>> if (CMAKE_SYSTEM_NAME STREQUAL "Linux") # for ubuntu's libblas3gf
>> and liblapack3gf packages set(CMAKE_FIND_LIBRARY_SUFFIXES
>> ${CMAKE_FIND_LIBRARY_SUFFIXES} .so.3gf) endif ()
> 
> AFAICS this just adds another suffix, but will not remove an
> existing one, so this should not make anything go undetected that
> was detected before. You can try yourself if you just comment out
> this lines.

I did that (not by deleting the line but by just keeping .so instead
of .so.3gf, and then the detection works...

Hum strange...
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8dwNgACgkQEr8WrU8nPV2O8gCZAYxLCMkSbKO3SZpfJkD35w8N
ILwAoIIaesT3t5vL+IbgRKfAjT342+y7
=f5g0
-END PGP SIGNATURE-
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Rolf Eike Beer]

Theodore Papadopoulo wrote:
> I do not know if it is too late to require bugfix for the next release
> or even whether this bug is known (a quick browsing of buzilla shows
> nothing and the git sources still contain the bug), but in any case.
> 
> In cmake-2.8.6, the module FindLAPACK.cmake contains the lines:
> 
> if (CMAKE_SYSTEM_NAME STREQUAL "Linux")
># for ubuntu's libblas3gf and liblapack3gf packages
>set(CMAKE_FIND_LIBRARY_SUFFIXES ${CMAKE_FIND_LIBRARY_SUFFIXES} .so.3gf)
> endif ()

AFAICS this just adds another suffix, but will not remove an existing one, so 
this should not make anything go undetected that was detected before. You can 
try yourself if you just comment out this lines.

I think this may be something entirely different, that I have seen today for 
completely unrelated modules: if the library is in /usr/lib64 like on my 
openSuSE 12.1, the library is sometimes not detected. When trying it on my 
machine at home it works like a charm. I've not entirely understood what was 
wrong there and had no time yet to debug this.

Eike

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Theodore Papadopoulo]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I do not know if it is too late to require bugfix for the next release
or even whether this bug is known (a quick browsing of buzilla shows
nothing and the git sources still contain the bug), but in any case.

In cmake-2.8.6, the module FindLAPACK.cmake contains the lines:

if (CMAKE_SYSTEM_NAME STREQUAL "Linux")
   # for ubuntu's libblas3gf and liblapack3gf packages
   set(CMAKE_FIND_LIBRARY_SUFFIXES ${CMAKE_FIND_LIBRARY_SUFFIXES} .so.3gf)
endif ()

The problem here is that not all linux distribution are ubuntu, as a
result the lapack detection is broken on releases such as Fedora (14
to 16).

Is there a way to make this test more specific, or at least to provide
an option to let the user disable this "feature".

In the meantime, it might be interesting to have a patch in the fedora
package that just removes the .3gf (Orion I put you in copy just in
case, as I saw you are the fedora packager for cmake).

  Thank you very much,

Theo Papadopoulo.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8dltsACgkQEr8WrU8nPV2k7ACeOD8Df7A6wTPUNVCyiBDP4R4j
T6kAoJsnekGUH1s7AseXPwuB6teq4ujo
=ws/T
-END PGP SIGNATURE-
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[A A]

http://public.kitware.com/Bug/view.php?id=10094
http://public.kitware.com/Bug/view.php?id=9905 (Might be fixed already)
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Alexander Neundorf]

On Monday 16 January 2012, Abdelrazak Younes wrote:
> http://public.kitware.com/Bug/view.php?id=12614


It's on my list, but I can't prmise I'll be able to do it for 2.8.8.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Abdelrazak Younes]

http://public.kitware.com/Bug/view.php?id=12614

Even though this is not a bug fix... :-)

Thanks and regards,
Abdel.

-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of 
David Cole
Sent: Monday, January 02, 2012 6:12 PM
To: cmake
Subject: [CMake] Bug fix requests for the *next* release of CMake...

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. 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.

Example one-line reply:

  http://public.kitware.com/Bug/view.php?id=12647

We are aiming for quarterly releases from now on, scheduling them
every 3 months. That would make the next release of CMake version
2.8.8, scheduled to have an "rc1" release candidate on Wed. March 7,
2012 -- just 9 weeks from this Wednesday.

If you have a particular issue that you think should be fixed for
inclusion in 2.8.8, 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 on the roadmap
for this release here:
http://public.kitware.com/Bug/roadmap_page.php?version_id=90

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.7
release, see here:
http://public.kitware.com/Bug/changelog_page.php?version_id=89
-- 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 the last release...
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://www.cmake.org/mailman/listinfo/cmake
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Alexander Neundorf]

On Wednesday 11 January 2012, Patrick Spendrin wrote:
> Am 02.01.2012 18:11, schrieb David Cole:
> > 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. 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.
> > 
> > Example one-line reply:
> >   http://public.kitware.com/Bug/view.php?id=12647
> > 
> > We are aiming for quarterly releases from now on, scheduling them
> > every 3 months. That would make the next release of CMake version
> > 2.8.8, scheduled to have an "rc1" release candidate on Wed. March 7,
> > 2012 -- just 9 weeks from this Wednesday.
> > 
> > If you have a particular issue that you think should be fixed for
> > inclusion in 2.8.8, 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 on the roadmap
> > for this release here:
> > http://public.kitware.com/Bug/roadmap_page.php?version_id=90
> > 
> > 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.
> 
> My personal issues are:
> http://www.cmake.org/Bug/view.php?id=10994
> and connected to it: http://www.cmake.org/Bug/view.php?id=11153
> The handling of the windows drive root is not consistent/wrong, which
> leads to both errors. I checked yesterday but the patches I added in
> 10994 do lead to an endless loop in 11153. I will try to come up with a
> better patch in the coming days.

IMO these are quite important issue, since they issue causes every 
FooConfig.cmake file installed by any of the KDE libraries to contain extra 
code to work around this issue, which makes them less readable and harder to 
write (and easier to get wrong).

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[ycollette . nospam]

And this one maybe: http://public.kitware.com/Bug/view.php?id=12367

It should be nice to have this one corrected, for the aesthetic of the NSIS 
installer :)

Best regards,

YC

- Mail original -
De: "Patrick Spendrin" 
À: cmake@cmake.org
Envoyé: Mercredi 11 Janvier 2012 13:14:21
Objet: Re: [CMake] Bug fix requests for the *next* release of CMake...

Am 02.01.2012 18:11, schrieb David Cole:
> 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. 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.
> 
> Example one-line reply:
> 
>   http://public.kitware.com/Bug/view.php?id=12647
> 
> We are aiming for quarterly releases from now on, scheduling them
> every 3 months. That would make the next release of CMake version
> 2.8.8, scheduled to have an "rc1" release candidate on Wed. March 7,
> 2012 -- just 9 weeks from this Wednesday.
> 
> If you have a particular issue that you think should be fixed for
> inclusion in 2.8.8, 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 on the roadmap
> for this release here:
> http://public.kitware.com/Bug/roadmap_page.php?version_id=90
> 
> 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.

My personal issues are:
http://www.cmake.org/Bug/view.php?id=10994
and connected to it: http://www.cmake.org/Bug/view.php?id=11153
The handling of the windows drive root is not consistent/wrong, which
leads to both errors. I checked yesterday but the patches I added in
10994 do lead to an endless loop in 11153. I will try to come up with a
better patch in the coming days.

regards,
Patrick
--

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://www.cmake.org/mailman/listinfo/cmake
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Patrick Spendrin]

Am 02.01.2012 18:11, schrieb David Cole:
> 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. 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.
> 
> Example one-line reply:
> 
>   http://public.kitware.com/Bug/view.php?id=12647
> 
> We are aiming for quarterly releases from now on, scheduling them
> every 3 months. That would make the next release of CMake version
> 2.8.8, scheduled to have an "rc1" release candidate on Wed. March 7,
> 2012 -- just 9 weeks from this Wednesday.
> 
> If you have a particular issue that you think should be fixed for
> inclusion in 2.8.8, 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 on the roadmap
> for this release here:
> http://public.kitware.com/Bug/roadmap_page.php?version_id=90
> 
> 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.

My personal issues are:
http://www.cmake.org/Bug/view.php?id=10994
and connected to it: http://www.cmake.org/Bug/view.php?id=11153
The handling of the windows drive root is not consistent/wrong, which
leads to both errors. I checked yesterday but the patches I added in
10994 do lead to an endless loop in 11153. I will try to come up with a
better patch in the coming days.

regards,
Patrick
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Daniel Dekkers]

Xcode stuff would be great...
http://public.kitware.com/Bug/view.php?id=12640
http://public.kitware.com/Bug/view.php?id=12506
http://public.kitware.com/Bug/view.php?id=12532

On Jan 2, 2012, at 6:11 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. 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.
> 
> Example one-line reply:
> 
>  http://public.kitware.com/Bug/view.php?id=12647
> 
> We are aiming for quarterly releases from now on, scheduling them
> every 3 months. That would make the next release of CMake version
> 2.8.8, scheduled to have an "rc1" release candidate on Wed. March 7,
> 2012 -- just 9 weeks from this Wednesday.
> 
> If you have a particular issue that you think should be fixed for
> inclusion in 2.8.8, 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 on the roadmap
> for this release here:
> http://public.kitware.com/Bug/roadmap_page.php?version_id=90
> 
> 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.7
> release, see here:
> http://public.kitware.com/Bug/changelog_page.php?version_id=89
> -- 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 the last release...
> 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://www.cmake.org/mailman/listinfo/cmake

--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Alexander Neundorf]

On Monday 02 January 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. 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.

If I may ;-) :
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Genest]

http://public.kitware.com/Bug/view.php?id=8438

http://public.kitware.com/Bug/view.php?id=11258

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

Might be nice to decide about this one:


Sean


--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Rolf Eike Beer]

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. 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.

http://public.kitware.com/Bug/view.php?id=12648

 (Patch is attached and pushed to next a minute ago)


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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Jean-Christophe Fillion-Robin]

http://public.kitware.com/Bug/view.php?id=12564
http://public.kitware.com/Bug/view.php?id=11403

Jc

On Mon, Jan 2, 2012 at 12:20 PM, Robert Dailey  wrote:

> http://public.kitware.com/Bug/view.php?id=12649
>
> -
> Robert Dailey
>
>
>
> On Mon, Jan 2, 2012 at 11:11 AM, 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. 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.
>>
>> Example one-line reply:
>>
>>  http://public.kitware.com/Bug/view.php?id=12647
>>
>> We are aiming for quarterly releases from now on, scheduling them
>> every 3 months. That would make the next release of CMake version
>> 2.8.8, scheduled to have an "rc1" release candidate on Wed. March 7,
>> 2012 -- just 9 weeks from this Wednesday.
>>
>> If you have a particular issue that you think should be fixed for
>> inclusion in 2.8.8, 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 on the roadmap
>> for this release here:
>> http://public.kitware.com/Bug/roadmap_page.php?version_id=90
>>
>> 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.7
>> release, see here:
>> http://public.kitware.com/Bug/changelog_page.php?version_id=89
>> -- 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 the last release...
>> 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://www.cmake.org/mailman/listinfo/cmake
>>
>
>
> --
>
> 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://www.cmake.org/mailman/listinfo/cmake
>



-- 
+1 919 869 8849
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Robert Dailey]

http://public.kitware.com/Bug/view.php?id=12649

-
Robert Dailey


On Mon, Jan 2, 2012 at 11:11 AM, 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. 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.
>
> Example one-line reply:
>
>  http://public.kitware.com/Bug/view.php?id=12647
>
> We are aiming for quarterly releases from now on, scheduling them
> every 3 months. That would make the next release of CMake version
> 2.8.8, scheduled to have an "rc1" release candidate on Wed. March 7,
> 2012 -- just 9 weeks from this Wednesday.
>
> If you have a particular issue that you think should be fixed for
> inclusion in 2.8.8, 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 on the roadmap
> for this release here:
> http://public.kitware.com/Bug/roadmap_page.php?version_id=90
>
> 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.7
> release, see here:
> http://public.kitware.com/Bug/changelog_page.php?version_id=89
> -- 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 the last release...
> 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://www.cmake.org/mailman/listinfo/cmake
>
--

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://www.cmake.org/mailman/listinfo/cmake

[CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

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. 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.

Example one-line reply:

  http://public.kitware.com/Bug/view.php?id=12647

We are aiming for quarterly releases from now on, scheduling them
every 3 months. That would make the next release of CMake version
2.8.8, scheduled to have an "rc1" release candidate on Wed. March 7,
2012 -- just 9 weeks from this Wednesday.

If you have a particular issue that you think should be fixed for
inclusion in 2.8.8, 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 on the roadmap
for this release here:
http://public.kitware.com/Bug/roadmap_page.php?version_id=90

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.7
release, see here:
http://public.kitware.com/Bug/changelog_page.php?version_id=89
-- 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 the last release...
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Domagoj Saric]

On 10.11.2011. 16:08, David Cole wrote:

As noted in that bug itself in the most recent note:

"Brad just put this one in the backlog... I'm not going to put it on
the roadmap for 2.8.6 unless somebody else steps forward with more
work on this, as noted by Brad in his previous comments here."

I'm going to say the same thing for 2.8.7 unless somebody volunteers
to take on the work for it.


Is there something substantially different to COMPILE_FLAGS_ than there 
is to the already existing LINK_FLAGS_?



--
"What Huxley teaches is that in the age of advanced technology, spiritual
devastation is more likely to come from an enemy with a smiling face than
from one whose countenance exudes suspicion and hate."
Neil Postman
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

As noted in that bug itself in the most recent note:

"Brad just put this one in the backlog... I'm not going to put it on
the roadmap for 2.8.6 unless somebody else steps forward with more
work on this, as noted by Brad in his previous comments here."

I'm going to say the same thing for 2.8.7 unless somebody volunteers
to take on the work for it.


Thanks,
David


On Thu, Nov 10, 2011 at 9:18 AM, Domagoj Saric
 wrote:
> I'm sorry I'm late but if this old one could possibly get in for 2.8.7:
>
> http://public.kitware.com/Bug/view.php?id=6493
>
>
> --
> "What Huxley teaches is that in the age of advanced technology, spiritual
> devastation is more likely to come from an enemy with a smiling face than
> from one whose countenance exudes suspicion and hate."
> Neil Postman
> --
>
> 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://www.cmake.org/mailman/listinfo/cmake
>
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Domagoj Saric]

I'm sorry I'm late but if this old one could possibly get in for 2.8.7:

http://public.kitware.com/Bug/view.php?id=6493


--
"What Huxley teaches is that in the age of advanced technology, spiritual
devastation is more likely to come from an enemy with a smiling face than
from one whose countenance exudes suspicion and hate."
Neil Postman
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Robert Dailey]

I realize this is a feature but since I've provided the patch files that
implement this (attached to the bug below) I was hoping you wouldn't mind.
It's a small feature addition for source control bindings. Read more here:
http://public.kitware.com/Bug/view.php?id=12549

-
Robert Dailey


On Fri, Oct 28, 2011 at 10:26 AM, Robert Dailey  wrote:

> I just created a bug here:
> http://public.kitware.com/Bug/view.php?id=12545
>
> The issue involves duplicate entries in the Add Remove Programs dialog in
> Windows 7 when installing upgrades for CMake using the installer. I'd like
> to see this cleaned up by the next release, as subsequent upgrades will
> surely only add more duplicated entries.
>
> -
> Robert Dailey
>
>
>
> On Fri, Oct 21, 2011 at 11:19 AM, 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://www.cmake.org/mailman/listinfo/cmake
>>
>
>
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Robert Dailey]

I just created a bug here:
http://public.kitware.com/Bug/view.php?id=12545

The issue involves duplicate entries in the Add Remove Programs dialog in
Windows 7 when installing upgrades for CMake using the installer. I'd like
to see this cleaned up by the next release, as subsequent upgrades will
surely only add more duplicated entries.

-
Robert Dailey


On Fri, Oct 21, 2011 at 11:19 AM, 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://www.cmake.org/mailman/listinfo/cmake
>
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Claudio Bley]

Hi.

This one, please: http://public.kitware.com/Bug/view.php?id=12273
(*very* easy ;))

And this one too: http://public.kitware.com/Bug/view.php?id=11773

Thanks,
Claudio


--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Bill Hoffman]

On 10/25/2011 2:46 PM, Thomas Sondergaard wrote:

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



There is an out of cmake solution for this.

http://vscommands.com/

If you install the VSCommands plugin free version, it will fix the 
reload dialog to only ask once.


-Bill

--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Bill Hoffman]

On 10/25/2011 2:46 PM, Thomas Sondergaard wrote:



The VS2010 bug!

http://public.kitware.com/Bug/view.php?id=11258


Would love to fix that if we knew how :(


-Bill

--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Thomas Sondergaard]

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Mike Wittman]

http://public.kitware.com/Bug/view.php?id=8438

-Mike

On 10/21/2011 01: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://www.cmake.org/mailman/listinfo/cmake


--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Yuri Timenkov]

Hi David,

Please add http://public.kitware.com/Bug/view.php?id=9742 to road map.
At least part which generates proper GUIDS for different projects (I'm
especially interested into including C# projects).

Thanks,
Yuri

On Fri, Oct 21, 2011 at 10: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://www.cmake.org/mailman/listinfo/cmake
>
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Daniel Dekkers]

Yes, me -> http://public.kitware.com/Bug/view.php?id=12532

Don't think as a reporter you can even edit your own bug entries after 
committing them. Or I'm missing a button somewhere.

Op 21 okt. 2011 om 20:20 heeft David Cole  het volgende 
geschreven:

> 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://www.cmake.org/mailman/listinfo/cmake
--

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

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://www.cmake.org/mailman/listinfo/cmake

[CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Johannes Stallkamp]

Probably a bit late, but I was on vacaction:
 
http://www.cmake.org/Bug/view.php?id=12260
 
Johannes
 
 
 

___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Glenn Coombs]

Probably too late now and there isn't a bug filed so far as I know, but one
thing I would love to see added to cmake is an append command so that lines
like this:

set(CMAKE_EXE_LINKER_FLAGS_RELEASE "${CMAKE_EXE_LINKER_FLAGS_RELEASE}
/INCREMENTAL:NO")

become shorter and easier to understand:

append(CMAKE_EXE_LINKER_FLAGS_RELEASE "/INCREMENTAL:NO")

The existing syntax for the set command is just ugly when appending.  I know
you can define a macro or function to do this but I just feel that it should
be supported out of the box as it would make CMakeLists.txt files more
readable.

--
Glenn
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Johan Björk]

http://public.kitware.com/Bug/view.php?id=12284 (cpack copies data in
symlinks)


On Mon, Aug 1, 2011 at 9:26 PM, Alexander Neundorf
wrote:

> On Saturday 30 July 2011, Alan W. Irwin wrote:
> > Please do a fundamental fix for
> > http://public.kitware.com/Bug/view.php?id=9220.
>
> Since I implemented this, I feel responsible for it.
> But most probably I will not be able to do this for 2.8.6.
> At least I'll try to make it work again for ASM.
>
> 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://www.cmake.org/mailman/listinfo/cmake
>
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

David,



Cheers,

Sean


___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Alexander Neundorf]

On Saturday 30 July 2011, Alan W. Irwin wrote:
> Please do a fundamental fix for
> http://public.kitware.com/Bug/view.php?id=9220.

Since I implemented this, I feel responsible for it.
But most probably I will not be able to do this for 2.8.6.
At least I'll try to make it work again for ASM.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Johan Björk]

http://www.cmake.org/Bug/view.php?id=12379 (EXCLUDE_FROM_DEFAULT_BUILD
broken)
http://www.cmake.org/Bug/view.php?id=12377 (-g0 enables debug in XCode)
http://www.cmake.org/Bug/view.php?id=12358 (ENABLE_LANGUAGE(.. OPTIONAL)
breaks configure step
http://www.cmake.org/Bug/view.php?id=11690 (XCode generator overwrites user
settings)

Bonus wishlist:
http://www.cmake.org/Bug/view.php?id=12275 (Generated files not removed by
clean target w/XCode)

On Mon, Aug 1, 2011 at 12:54 PM, Domagoj Saric <
domagoj.sa...@littleendian.com> wrote:

>
> http://public.kitware.com/Bug/**view.php?id=12375
> http://public.kitware.com/Bug/**view.php?id=12376
>
> thanks ;)
>
>
> --
> "What Huxley teaches is that in the age of advanced technology, spiritual
> devastation is more likely to come from an enemy with a smiling face than
> from one whose countenance exudes suspicion and hate."
> Neil Postman
>
> __**_
> 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://www.cmake.org/mailman/**listinfo/cmake
>
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Domagoj Saric]

http://public.kitware.com/Bug/view.php?id=12375
http://public.kitware.com/Bug/view.php?id=12376

thanks ;)


--
"What Huxley teaches is that in the age of advanced technology, spiritual
devastation is more likely to come from an enemy with a smiling face than
from one whose countenance exudes suspicion and hate."
Neil Postman
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Glenn Coombs]

http://public.kitware.com/Bug/view.php?id=6493
configuration dependent COMPILE_FLAGS for SET_TARGET_PROPERTIES

http://public.kitware.com/Bug/view.php?id=6269
Some CMake commands should support Debug/Release configurations

http://public.kitware.com/Bug/view.php?id=12124
Need per configuration version of target_link_libraries() or fix
IMPORTED_LOCATION to allow empty string

--
Glenn
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Rolf Eike Beer]

Am Donnerstag, 28. Juli 2011, 18:49:17 schrieb David Cole:
> 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. 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.

> (Many of those were specifically addressed because somebody brought it up in
> response to my similar email from just after 2.8.4... Don't be shy!)

Ok, then let's see what is still open on my whishlist for 2.8.4:

http://www.cmake.org/Bug/view.php?id=12054
  FindJava.cmake too noisy on second run

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=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=10941
  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

#1 and #2 already have patches.

Eike

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Niels Dekker - address until 2014]

http://public.kitware.com/Bug/view.php?id=12323 ("FindDCMTK cannot find 
all includes for MSVC build of DCMTK", by Dan Thill) See also my note:

http://public.kitware.com/Bug/bug_relationship_graph.php?bug_id=12323#bugnotes

Kind regards, Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Alan W. Irwin]

http://public.kitware.com/Bug/view.php?id=12301
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Alan W. Irwin]

Please do a fundamental fix for http://public.kitware.com/Bug/view.php?id=9220.

Alan


__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__

Linux-powered Science
__
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

2011/7/29 Alexander Neundorf 

> On Friday 29 July 2011, 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. 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.
> >
> > Example one-line reply:
> >
> >   http://public.kitware.com/Bug/view.php?id=8707
> >
> > We are planning for CMake 2.8.6 already, and it's going to be a
> compressed
> > release cycle this time around. We're targeting Sept. 14, 2011 for
> > releasing it, and in order to make that happen we'll have to do an "rc1"
> > as early as Aug 10th or 17th... just 2 or 3 weeks from now.
>
> From the KDE point of view this is somewhat unfortunate, that exactly this
> cycle will be shorter.
> Are there reasons for it ?
>

There are reasons for it. For one thing, the 2.8.5 release took too long, so
we want to make this one shorter to keep us on schedule for getting 4
releases per year out there. If we can actually deliver 2.8.6 on Sept. 14th,
we can reliably plan on 2.8.7 being delivered in mid-December.

It may be unfortunate, but we will stick with it unless we receive mucho
objections from others in addition to KDE.

Is mid-December too far in the future? (And a minimum version of 2.8.7...?)



> With the coming Qt5 and the binary break this causes in KDE we plan to also
> break binary compatibility once (while keeping source compatibility similar
> to
> Qt more or less completely).
>

When is the Qt5 release scheduled for?



>
> With this break we will also use the chance to break our cmake source
> compatiblity once, the first time since KDE 4.0.0 in early 2007.
> Which means we try to merge a lot of our stuff into cmake, and then depend
> on
> this version of cmake, i.e. 2.8.6.
> 2.8.7 will be released maybe around January or so, right ? This would be
> quite
> late for us.
> This does not just mean merge, but also change it so it becomes acceptable
> for
> cmake, etc.
>
> This is the list of files in KDE which are potential candidates for being
> upstreamed:
>
> http://community.kde.org/index.php?title=KDE_Core/Platform_11/Buildsystem/FindFilesSurvey
>
> Not all files listed on this page have realistic chances IMO.
> But I'd really like to get rid of the copies in KDE of the files in the
> sections "2 Check*.cmake files", "3 Generic Macros" and "5.1.1 Find*.cmake
> from kdelibs which exist in cmake".
>
> If you look there, already in these three sections there are still a lot of
> files marked as TODO.
> Getting all that done until August 10th is hard, to say the least. Also now
> is
> the time for summer vacations, which makes it even more hard.
>
> So, from our (KDE) side being able to work on the stuff listed on the page
> linked above until like end of September would be ideal.
> (additionally there are the things like automoc which I already started
> discussing on the cmake developers list).
>
> Alex
>
>
That is an ambitious amount of work. I'm skeptical that we could even fit
all that into a mid-September rc1, let alone a mid-August rc1... It would
probably be better if you shoot for getting that in by November, and
counting on a December release of CMake 2.8.7.

Let me know if you have further thoughts or comments here.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

bugs:






features:


not a bug, but a distribution consideration:


Cheers!

Sean


___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Alexander Neundorf]

On Friday 29 July 2011, 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. 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.
> 
> Example one-line reply:
> 
>   http://public.kitware.com/Bug/view.php?id=8707
> 
> We are planning for CMake 2.8.6 already, and it's going to be a compressed
> release cycle this time around. We're targeting Sept. 14, 2011 for
> releasing it, and in order to make that happen we'll have to do an "rc1"
> as early as Aug 10th or 17th... just 2 or 3 weeks from now.

>From the KDE point of view this is somewhat unfortunate, that exactly this 
cycle will be shorter.
Are there reasons for it ?

With the coming Qt5 and the binary break this causes in KDE we plan to also 
break binary compatibility once (while keeping source compatibility similar to 
Qt more or less completely).

With this break we will also use the chance to break our cmake source 
compatiblity once, the first time since KDE 4.0.0 in early 2007.
Which means we try to merge a lot of our stuff into cmake, and then depend on 
this version of cmake, i.e. 2.8.6.
2.8.7 will be released maybe around January or so, right ? This would be quite 
late for us.
This does not just mean merge, but also change it so it becomes acceptable for 
cmake, etc.

This is the list of files in KDE which are potential candidates for being 
upstreamed:
http://community.kde.org/index.php?title=KDE_Core/Platform_11/Buildsystem/FindFilesSurvey

Not all files listed on this page have realistic chances IMO.
But I'd really like to get rid of the copies in KDE of the files in the 
sections "2 Check*.cmake files", "3 Generic Macros" and "5.1.1 Find*.cmake 
from kdelibs which exist in cmake".

If you look there, already in these three sections there are still a lot of 
files marked as TODO.
Getting all that done until August 10th is hard, to say the least. Also now is 
the time for summer vacations, which makes it even more hard.

So, from our (KDE) side being able to work on the stuff listed on the page 
linked above until like end of September would be ideal.
(additionally there are the things like automoc which I already started 
discussing on the cmake developers list).

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

On Thu, Jul 28, 2011 at 8:32 PM, Jean-Christophe Fillion-Robin <
jchris.filli...@kitware.com> wrote:

> Make sure
> http://cmake.org/gitweb?p=cmake.git;a=commit;h=702538eaa3315f3fcad9f1daea01e6a83928967bis
>  integrated to CMake 2.8.6
>
> Thanks
> Jc
>

This commit is already in 'master' which means it will automatically be in
2.8.6 unless a further commit also merged to 'master' negates its effect
It should be in 2.8.6.

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[J Decker]

On Thu, Jul 28, 2011 at 3:49 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. 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.
>

http://public.kitware.com/Bug/view.php?id=12245
http://public.kitware.com/Bug/view.php?id=11866
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Jean-Christophe Fillion-Robin]

http://public.kitware.com/Bug/view.php?id=11177

On Thu, Jul 28, 2011 at 8:32 PM, Jean-Christophe Fillion-Robin <
jchris.filli...@kitware.com> wrote:

> Make sure
> http://cmake.org/gitweb?p=cmake.git;a=commit;h=702538eaa3315f3fcad9f1daea01e6a83928967bis
>  integrated to CMake 2.8.6
>
> Thanks
> Jc
>
>
> On Thu, Jul 28, 2011 at 8:23 PM, Steven Velez  wrote:
>
>> http://public.kitware.com/Bug/view.php?id=12299
>>
>> ___
>> 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://www.cmake.org/mailman/listinfo/cmake
>>
>
>
>
> --
> +1 919 869 8849
>
>


-- 
+1 919 869 8849
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Jean-Christophe Fillion-Robin]

Make sure
http://cmake.org/gitweb?p=cmake.git;a=commit;h=702538eaa3315f3fcad9f1daea01e6a83928967bis
integrated to CMake 2.8.6

Thanks
Jc

On Thu, Jul 28, 2011 at 8:23 PM, Steven Velez  wrote:

> http://public.kitware.com/Bug/view.php?id=12299
>
> ___
> 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://www.cmake.org/mailman/listinfo/cmake
>



-- 
+1 919 869 8849
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Steven Velez]

http://public.kitware.com/Bug/view.php?id=12299

___
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://www.cmake.org/mailman/listinfo/cmake

[CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

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. 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.

Example one-line reply:

  http://public.kitware.com/Bug/view.php?id=8707

We are planning for CMake 2.8.6 already, and it's going to be a compressed
release cycle this time around. We're targeting Sept. 14, 2011 for releasing
it, and in order to make that happen we'll have to do an "rc1" as early as
Aug 10th or 17th... just 2 or 3 weeks from now.

Since we released CMake 2.8.5 less than three weeks ago, we now need to
prioritize bug fixes for the next release of CMake. And we probably only
have time to get a few handfuls of them addressed.

If you have a particular issue that you think should be fixed for inclusion
in 2.8.6, please bring it up by Wed. Aug 3 at the latest. 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.6 -- 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 few weeks.


Thanks,
David Cole
Kitware, Inc.


P.S. - as a nice summary of what we accomplished in the CMake 2.8.5 release,
including contributions from 33 individuals around the world, see here:
http://public.kitware.com/Bug/changelog_page.php?version_id=84 -- it
currently lists 80 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.4... 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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Johan Björk]

http://public.kitware.com/Bug/view.php?id=11690 XCode user settings

http://public.kitware.com/Bug/view.php?id=11692 interrupt batch build
doesn't stop visual studio

http://public.kitware.com/Bug/view.php?id=10039 Xcode gen only creates one
level of group nesting

http://public.kitware.com/Bug/view.php?id=11844 Xcode depends helper works
badly. But prefer to remove dep helper completely.



http://public.kitware.com/Bug/view.php?id=11667 <- this bug is already fixed
and should be closed.

http://public.kitware.com/Bug/view.php?id=8179 <- dup of above



-Johan



On Fri, Apr 1, 2011 at 2:18 AM, Chris Scharver  wrote:

> On Thu, Mar 31, 2011 at 6:39 PM, Bill Hoffman 
> wrote:
> > On 3/31/2011 6:15 PM, David Cole wrote:
> >>
> >> On Thu, Mar 31, 2011 at 6:05 PM, Bill Hoffman  >> > wrote:
> >>
> >>On 3/31/2011 4:19 PM, Chris Scharver wrote:
> >>
> >>EXTERNAL_OBJECT not linked using Visual Studio 2010
> >>http://public.kitware.com/Bug/view.php?id=11891
> >>
> >>Thanks for the pointer to that bug.  It even has a fix.  The thing I
> >>can not figure  out is why our ExternlObj test is passing even when
> >>this is broken   Any ideas why that test works?
> >>
> >> I think it's one of those "works in MSBuild, but not in devenv"
> issues...
> >
> > Nope, I loaded it up in devenv and ExternlObj compiles  Ran cmake-gui
> on
> > ExternalObj then loaded the project and it works... ???
>
> I just did some tinkering and found that a simple change of modifying
> the ExternalObj test to link with the external object resulted in a
> failure.
>
> ADD_EXECUTABLE(ExternalOBJ executable.cxx ${EXTERNAL_OBJECT})
> SET_SOURCE_FILES_PROPERTIES(${EXTERNAL_OBJECT} PROPERTIES EXTERNAL_OBJECT
> 1)
>
> Perhaps the fact that there's a rule to generate the custom object
> changes how it's handled?
>
> Chris
> ___
> 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://www.cmake.org/mailman/listinfo/cmake
>
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Chris Scharver]

On Thu, Mar 31, 2011 at 6:39 PM, Bill Hoffman  wrote:
> On 3/31/2011 6:15 PM, David Cole wrote:
>>
>> On Thu, Mar 31, 2011 at 6:05 PM, Bill Hoffman > > wrote:
>>
>>    On 3/31/2011 4:19 PM, Chris Scharver wrote:
>>
>>        EXTERNAL_OBJECT not linked using Visual Studio 2010
>>        http://public.kitware.com/Bug/view.php?id=11891
>>
>>    Thanks for the pointer to that bug.  It even has a fix.  The thing I
>>    can not figure  out is why our ExternlObj test is passing even when
>>    this is broken   Any ideas why that test works?
>>
>> I think it's one of those "works in MSBuild, but not in devenv" issues...
>
> Nope, I loaded it up in devenv and ExternlObj compiles  Ran cmake-gui on
> ExternalObj then loaded the project and it works... ???

I just did some tinkering and found that a simple change of modifying
the ExternalObj test to link with the external object resulted in a
failure.

ADD_EXECUTABLE(ExternalOBJ executable.cxx ${EXTERNAL_OBJECT})
SET_SOURCE_FILES_PROPERTIES(${EXTERNAL_OBJECT} PROPERTIES EXTERNAL_OBJECT 1)

Perhaps the fact that there's a rule to generate the custom object
changes how it's handled?

Chris
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Bill Hoffman]

On 3/31/2011 6:15 PM, David Cole wrote:

On Thu, Mar 31, 2011 at 6:05 PM, Bill Hoffman mailto:bill.hoff...@kitware.com>> wrote:

On 3/31/2011 4:19 PM, Chris Scharver wrote:

EXTERNAL_OBJECT not linked using Visual Studio 2010
http://public.kitware.com/Bug/view.php?id=11891


Thanks for the pointer to that bug.  It even has a fix.  The thing I
can not figure  out is why our ExternlObj test is passing even when
this is broken   Any ideas why that test works?

Thanks.

-Bill


I think it's one of those "works in MSBuild, but not in devenv" issues...



Nope, I loaded it up in devenv and ExternlObj compiles  Ran 
cmake-gui on ExternalObj then loaded the project and it works... ???


-Bill
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

On Thu, Mar 31, 2011 at 6:05 PM, Bill Hoffman wrote:

> On 3/31/2011 4:19 PM, Chris Scharver wrote:
>
>> EXTERNAL_OBJECT not linked using Visual Studio 2010
>> http://public.kitware.com/Bug/view.php?id=11891
>>
>
> Thanks for the pointer to that bug.  It even has a fix.  The thing I can
> not figure  out is why our ExternlObj test is passing even when this is
> broken   Any ideas why that test works?
>
> Thanks.
>
> -Bill
>
>
I think it's one of those "works in MSBuild, but not in devenv" issues...



> ___
> 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://www.cmake.org/mailman/listinfo/cmake
>
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Bill Hoffman]

On 3/31/2011 4:19 PM, Chris Scharver wrote:

EXTERNAL_OBJECT not linked using Visual Studio 2010
http://public.kitware.com/Bug/view.php?id=11891


Thanks for the pointer to that bug.  It even has a fix.  The thing I can 
not figure  out is why our ExternlObj test is passing even when this is 
broken   Any ideas why that test works?


Thanks.

-Bill
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Chris Scharver]

EXTERNAL_OBJECT not linked using Visual Studio 2010
http://public.kitware.com/Bug/view.php?id=11891
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Michael Jackson]

http://public.kitware.com/Bug/view.php?id=12034
___
Mike Jackson  www.bluequartz.net
Principal Software Engineer   mike.jack...@bluequartz.net 
BlueQuartz Software   Dayton, Ohio

On 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!)
> 
> ___
> 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://www.cmake.org/mailman/listinfo/cmake

___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Martin Apel]

On 29/03/11 19:56, David Cole wrote:
> 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.

http://public.kitware.com/Bug/view.php?id=11942

This currently keeps us from upgrading to 2.8.3 or 2.8.4.

Thanks,

Martin
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Brian Bassett]

I second this request.  This also includes

http://public.kitware.com/Bug/view.php?id=8170

Brian

On Wed, Mar 30, 2011 at 6:25 AM, Jay Foad  wrote:

> Support for assembler sources in the Visual Studio generators, please!
>
> http://public.kitware.com/Bug/view.php?id=9905
> http://public.kitware.com/Bug/view.php?id=11536
>
> Thanks,
> Jay.
> ___
> 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://www.cmake.org/mailman/listinfo/cmake
>
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[James C. Sutherland]

http://public.kitware.com/Bug/print_bug_page.php?bug_id=10077*
*
James
*



*
On Tue, Mar 29, 2011 at 11:56 AM, 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!)
>
>
> ___
> 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://www.cmake.org/mailman/listinfo/cmake
>
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Aaron_Wright]

http://public.kitware.com/Bug/view.php?id=11171

I'm hoping this one isn't too hard to fix.

---
Aaron Wright




From:   David Cole 
To: cmake , CMake Developers 

Date:   03/29/2011 10:57 AM
Subject:    [CMake] Bug fix requests for the *next* release of 
CMake...
Sent by:cmake-boun...@cmake.org



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!)
___
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://www.cmake.org/mailman/listinfo/cmake

___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Doria]

CMAKE_BUILD_TYPE should be a drop down box/fixed set of choices

http://public.kitware.com/Bug/view.php?id=11806

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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Jay Foad]

Support for assembler sources in the Visual Studio generators, please!

http://public.kitware.com/Bug/view.php?id=9905
http://public.kitware.com/Bug/view.php?id=11536

Thanks,
Jay.
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Chatterjee, Shash]

Hi David,

http://public.kitware.com/Bug/view.php?id=11896

Thanks,
Shash


-Original Message-
From: cmake-boun...@cmake.org on behalf of David Cole
Sent: Tue 3/29/2011 12:56 PM
To: cmake; CMake Developers
Subject: [CMake] Bug fix requests for the *next* release of CMake...
 
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. 
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

On Tue, 29 Mar 2011 13:56:03 -0400, David Cole said:

>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.



-- 

Sean McBride, B. Eng s...@rogue-research.com
Rogue Researchwww.rogue-research.com 
Mac Software Developer  Montréal, Québec, Canada


___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Alan W. Irwin]

On 2011-03-29 13:56-0400 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.


Please do a fundamental fix for http://public.kitware.com/Bug/view.php?id=9220.

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__

Linux-powered Science
__
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[John Drescher]

http://public.kitware.com/Bug/view.php?id=11206

John
___
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://www.cmake.org/mailman/listinfo/cmake

[CMake] Bug fix requests for the *next* release of CMake...

[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.

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!)
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Tony Bridges]

Hi David, 

0008165 - vs2005 midl chokes on CMAKE_INTDIR  (also 2008)
  http://public.kitware.com/Bug/view.php?id=8165

I would love to see a fix for 0008165 in the next version.

Each new version we pick up, I have to reapply Robert Lenhardt's patch and 
rebuild.
   http://public.kitware.com/Bug/file_download.php?file_id=1887&type=bug
The change is simple and isolated, from what I can see. 

Thanks!
/t


-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of 
David Cole
Sent: Wednesday, November 10, 2010 12:53 PM
To: Adam J Richardson
Cc: cmake@cmake.org
Subject: Re: [CMake] Bug fix requests for the *next* release of CMake...

On Fri, Nov 5, 2010 at 6:29 AM, Adam J Richardson  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi David,
>
>> Replies requested.
>
> CMake is already pretty awesome from my POV, but since you ask...
>
>> Replies on this thread should just be a collector for bug numbers.
>
> Afraid I don't have a bug number, but I can explain quickly.
>
>> If you have a particular issue that you think should be fixed for 
>> inclusion in 2.8.4, please bring it up now.
>
> Could you guys have a chat with the Boost guys and fix the "future 
> safety" of FindBoost.cmake somehow? Fiddling with ADDITIONAL_VERSIONS 
> is really a pain on a build farm.
>
> Oh, and include Mateusz Loskot's FindODBC.cmake in the release?

To include a new module in CMake, we need a module maintainer for it, as 
outlined here:
http://www.cmake.org/Wiki/CMake:Module_Maintainers

So unless there is a volunteer for FindODBC, it will not be in CMake.

Let me know if you or somebody you know wants to be that volunteer.


David


>
> Thanks,
> Adam J Richardson
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAkzT3GwACgkQSUH6dLOqvqlyOQCfaC2+BL+jkULzetoh3bduWoHU
> tmMAniddpSiMW4KpeRjpS0me9C+3RNjm
> =4TE7
> -END PGP SIGNATURE-
>
___
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://www.cmake.org/mailman/listinfo/cmake

-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Adam J Richardson]

> > If I have ignored one of your non-bug-issue points from a reply to
> > this thread, it's because it was not a bug number. If you still have
> > an issue, open a bug and reply here with its number or start a new
> > thread!!

Argh. Fine. Here's a bug number: #0011445

> Let me know if you or somebody you know wants to be that volunteer.

Unfortunately I have my fingers in way too many pies to find time to be
a maintainer. :( 


signature.asc
Description: PGP signature
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

By the way, I have also targeted the "10 oldest still open bugs" for
this release. I am thinking most of those can simply be closed,
(they're either fixed already or irrelevant after several years have
passed) but will leave it up to the people assigned them to decide
whether they should be kept alive for a future release still.


Cheers,
David


On Wed, Nov 10, 2010 at 1:30 PM, David Cole  wrote:
> Thanks to all of you who have participated in this thread so far...
>
> You have helped to create the initial roadmap for CMake 2.8.4:
> http://www.cmake.org/Bug/roadmap_page.php
>
> The roadmap currently lists 31 issues as "targeted" for CMake 2.8.4.
> What that means is: these are the 31 issues currently open for
> discussion for *possibly* fixing in CMake 2.8.4. It does not
> necessarily mean that a bug listed there will definitely be fixed for
> the release. It means we'll have discussions, try some fixes, and get
> the ones that work in for the release.
>
> If we make a decision not to fix a bug, I'll either close it out as
> "fixed in 2.8.4" with an appropriate non-fix resolution, or leave it
> open for a future release and simply unset the "target release" field.
>
> If there are still others to consider for the 2.8.4 release, please
> reply here with just the bug numbers. Please do not hijack this thread
> to talk about specifics. Bug numbers only please. I really appreciate
> the vast majority here who have simply listed the issues of
> interest...
>
> If I have ignored one of your non-bug-issue points from a reply to
> this thread, it's because it was not a bug number. If you still have
> an issue, open a bug and reply here with its number or start a new
> thread!!
>
>
> Thank you,
> David Cole
> Kitware, Inc.
>
>
> On Fri, Nov 5, 2010 at 10:48 AM, Rolf Eike Beer  wrote:
>> Am Donnerstag, 4. November 2010 schrieb David Cole:
>>> 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.
>>
>> #11362
>>  Tests should be able to be called from a given working directory
>>    (has patch & testcase)
>>
>> #11332
>>  No dependency from ADD_CUSTOM_COMMAND to external project
>>
>> #11333
>>  FindThreads incorrectly adds -pthread to linker options
>>
>> #11329
>>  No system information on QNX
>>   (has patch)
>>
>> #11326: FindBISON breaks on localized systems
>>   (already in next, only needs merge into master)
>>
>> #11404: VS2010 generator broken by: set_source_files_properties(file.h
>> PROPERTIES LANGUAGE "C")
>>  (has patch)
>>
>> Without bug report as I only looked into the code:
>>  See thread with subject "Suspicious CPU speed calculation on Mac" on this
>> list, the 3rd mail has a patch.
>>
>>> 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.
>>
>> Any chance to just do a splash&dash release by just collecting some already
>> finished or rather minimal bugfixes and going into rc1 in like 2 weeks to 
>> see a
>> 2.8.4 with fixes only in half of the time? There are already some fixes 
>> around
>> and doing the rest of development for the then 2.8.5 in next for some more
>> weeks shouldn't hurt.
>>
>> Eike
>>
>> ___
>> 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://www.cmake.org/mailman/listinfo/cmake
>>
>
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[James Bigler]

Since the VS Plugin broken in 2010 bug (
http://public.kitware.com/Bug/view.php?id=11258) was added to the roadmap,
here's another bug that I noticed with the VS plugin.

VS Plugin doesn't reload the solution in VS 2008
http://public.kitware.com/Bug/view.php?id=11440

Thanks,
James
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Sean McBride]

On Wed, 10 Nov 2010 13:30:46 -0500, David Cole said:

>If there are still others to consider for the 2.8.4 release, please
>reply here with just the bug numbers. Please do not hijack this thread
>to talk about specifics. Bug numbers only please. I really appreciate
>the vast majority here who have simply listed the issues of
>interest...

David,

I suggest this one:


Cheers,

Sean


___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

Thanks to all of you who have participated in this thread so far...

You have helped to create the initial roadmap for CMake 2.8.4:
http://www.cmake.org/Bug/roadmap_page.php

The roadmap currently lists 31 issues as "targeted" for CMake 2.8.4.
What that means is: these are the 31 issues currently open for
discussion for *possibly* fixing in CMake 2.8.4. It does not
necessarily mean that a bug listed there will definitely be fixed for
the release. It means we'll have discussions, try some fixes, and get
the ones that work in for the release.

If we make a decision not to fix a bug, I'll either close it out as
"fixed in 2.8.4" with an appropriate non-fix resolution, or leave it
open for a future release and simply unset the "target release" field.

If there are still others to consider for the 2.8.4 release, please
reply here with just the bug numbers. Please do not hijack this thread
to talk about specifics. Bug numbers only please. I really appreciate
the vast majority here who have simply listed the issues of
interest...

If I have ignored one of your non-bug-issue points from a reply to
this thread, it's because it was not a bug number. If you still have
an issue, open a bug and reply here with its number or start a new
thread!!


Thank you,
David Cole
Kitware, Inc.


On Fri, Nov 5, 2010 at 10:48 AM, Rolf Eike Beer  wrote:
> Am Donnerstag, 4. November 2010 schrieb David Cole:
>> 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.
>
> #11362
>  Tests should be able to be called from a given working directory
>    (has patch & testcase)
>
> #11332
>  No dependency from ADD_CUSTOM_COMMAND to external project
>
> #11333
>  FindThreads incorrectly adds -pthread to linker options
>
> #11329
>  No system information on QNX
>   (has patch)
>
> #11326: FindBISON breaks on localized systems
>   (already in next, only needs merge into master)
>
> #11404: VS2010 generator broken by: set_source_files_properties(file.h
> PROPERTIES LANGUAGE "C")
>  (has patch)
>
> Without bug report as I only looked into the code:
>  See thread with subject "Suspicious CPU speed calculation on Mac" on this
> list, the 3rd mail has a patch.
>
>> 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.
>
> Any chance to just do a splash&dash release by just collecting some already
> finished or rather minimal bugfixes and going into rc1 in like 2 weeks to see 
> a
> 2.8.4 with fixes only in half of the time? There are already some fixes around
> and doing the rest of development for the then 2.8.5 in next for some more
> weeks shouldn't hurt.
>
> Eike
>
> ___
> 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://www.cmake.org/mailman/listinfo/cmake
>
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[David Cole]

On Fri, Nov 5, 2010 at 6:29 AM, Adam J Richardson  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi David,
>
>> Replies requested.
>
> CMake is already pretty awesome from my POV, but since you ask...
>
>> Replies on this thread should just be a collector for bug numbers.
>
> Afraid I don't have a bug number, but I can explain quickly.
>
>> If you have a particular issue that you think should be fixed for
>> inclusion in 2.8.4, please bring it up now.
>
> Could you guys have a chat with the Boost guys and fix the "future
> safety" of FindBoost.cmake somehow? Fiddling with ADDITIONAL_VERSIONS
> is really a pain on a build farm.
>
> Oh, and include Mateusz Loskot's FindODBC.cmake in the release?

To include a new module in CMake, we need a module maintainer for it,
as outlined here:
http://www.cmake.org/Wiki/CMake:Module_Maintainers

So unless there is a volunteer for FindODBC, it will not be in CMake.

Let me know if you or somebody you know wants to be that volunteer.


David


>
> Thanks,
> Adam J Richardson
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAkzT3GwACgkQSUH6dLOqvqlyOQCfaC2+BL+jkULzetoh3bduWoHU
> tmMAniddpSiMW4KpeRjpS0me9C+3RNjm
> =4TE7
> -END PGP SIGNATURE-
>
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Philip Lowman]

On Sun, Nov 7, 2010 at 8:29 PM, Luigi Calori  wrote:

>  On 07/11/2010 21.01, Philip Lowman wrote:
>
> On Fri, Nov 5, 2010 at 12:08 PM, Luigi Calori  wrote:
>
>>  +1 for FindBoost support to "CMakeified" version of Boost at "
>>> http://gitorious.org/~denisarnaud/boost/denisarnauds-zeuners-boost-cmake/commits/1.44.0-denis
>>> ":
>>
>>
>  Luigi,
>
>  Does the "CMakeified" version of Boost still not produce build outputs
> that match bjam by default?  I remember when I looked at it a year or two
> ago there appeared to be only minor issues with the library names.  I would
> have hoped that these issues would have been resolved by now.
>
> I just tried the build with cmake 2.8.2  under MSVC9 using release build
> and static linking:
> There seem to be a minor inconsistency: when building Boost with cmake the
> static libs do not have the prefix "lib" so boost the auto-linking fails.
> I have resolved by
>
> 1) when building boos, configure with -DLIBPREFIX=lib,
>
> 2) configure the project that search for boost with
> -DBoost_USE_STATIC_LIBS=ON
>
> During the installation step of "cmakefied" boost,  Boost.cmake config
> files get installed but not sure if FindBoost use it
>
> I' m not sure if this can be solved in FindBoost, but was just raising
> attention on a (for me) much better build system for Boost
>

Luigi,

Thanks for the additional information.  It sounds like a bug in the CMake
build system for Boost.  On WIN32 (but not CYGWIN) it should create static
boost libraries with the lib prefix and shared boost libraries without it to
match the long-established Boost/bjam conventions.  This allows static &
shared libraries to exist alongside each other in the lib folder since
otherwise their filenames would collide.

-- 
Philip Lowman
___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Luigi Calori]

On 07/11/2010 21.01, Philip Lowman wrote:
On Fri, Nov 5, 2010 at 12:08 PM, Luigi Calori > wrote:


+1 for FindBoost support to "CMakeified" version of Boost at

"http://gitorious.org/~denisarnaud/boost/denisarnauds-zeuners-boost-cmake/commits/1.44.0-denis

":


Luigi,

Does the "CMakeified" version of Boost still not produce build outputs 
that match bjam by default?  I remember when I looked at it a year or 
two ago there appeared to be only minor issues with the library names. 
 I would have hoped that these issues would have been resolved by now.
I just tried the build with cmake 2.8.2  under MSVC9 using release build 
and static linking:
There seem to be a minor inconsistency: when building Boost with cmake 
the static libs do not have the prefix "lib" so boost the auto-linking 
fails.

I have resolved by

1) when building boos, configure with -DLIBPREFIX=lib,

2) configure the project that search for boost with 
-DBoost_USE_STATIC_LIBS=ON


During the installation step of "cmakefied" boost,  Boost.cmake config 
files get installed but not sure if FindBoost use it


I' m not sure if this can be solved in FindBoost, but was just raising 
attention on a (for me) much better build system for Boost


thanks
   Luigi



Could you elaborate in a bug report what does and doesn't work between 
FindBoost.cmake and the branch of Boost that you're referring to and I 
would be more than happy to look into the issue.  I've heard reports 
of people getting FindBoost and CMakeified boost to play nice together 
but it involved changing build settings in CMakeified Boost (not quite 
ideal).


--
Philip Lowman


___
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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Bug fix requests for the *next* release of CMake...

[Philip Lowman]

On Fri, Nov 5, 2010 at 6:29 AM, Adam J Richardson wrote:

> Could you guys have a chat with the Boost guys and fix the "future
> safety" of FindBoost.cmake somehow? Fiddling with ADDITIONAL_VERSIONS
> is really a pain on a build farm.
>

To implement this I think we would need wildcat version searching support
for find_library() and friends.  I had a proposal for this a while ago but
it didn't go anywhere nor did I ever implement it.

http://www.itk.org/Bug/view.php?id=8396

I suggested that support for searching for files or directories that match a
particular regex that describes a version number be added.  In other words,
you could try to find:

NAMES foo-([0-9])\.([0-9]) or
PATHS bar([0-9]+)

The module would be responsible of passing on the request to find the latest
version number that matches, or it could specify an absolute version to
find.  It would probably have to be an extended form of the find_library(),
find_path(), etc. commands.

-- 
Philip Lowman
___
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://www.cmake.org/mailman/listinfo/cmake