On Thu, Mar 15, 2012 at 11:41 AM, Michael Hertling wrote:
> IMO, using solely _FIND_REQUIRED_ to indicate if
> a requested component is mandatory or optional is not sufficient.
> Consider the following use case:
>
> FIND_PACKAGE(Foo COMPONENTS X OPTIONAL_COMPONENTS Y)
>
> Suppose both X and Y do r
On 03/13/2012 09:55 PM, Brad King wrote:
> On Tue, Mar 13, 2012 at 4:43 PM, Alexander Neundorf wrote:
>> We could also not set _FIND_REQUIRED_, or set it to "0"
>> (which
>> would mean it is not required).
>
> Even better. One can loop over the_FIND_COMPONENTS list and then test
> the variable
On 03/13/2012 06:30 PM, Brad King wrote:
> On 3/13/2012 1:12 PM, Alexander Neundorf wrote:
>> Setting CMP0018 to new would mean that the project supports only those
>> component-aware packages which follow that new convention.
>
> Yes, that cannot be a requirement to use
>
>cmake_minimum_requ
So, I did a git branch switch to next and ran ninja on my build tree.
It correctly re-ran cmake. But I found a link error building cmake-gui:
CMakeLib.lib(cmLocalVisualStudio10Generator.cxx.obj) : error LNK2001:
unresolved external symbol "public: virtual void __thiscall
cmLocalVisualStudio7
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=13043
==
Reported By:Vadim Sushchenko
Assigned To:
