Re: [CMake] Disabling C for C++-only projects

2012-07-30 Thread Johannes Zarl
Am 26.07.2012, 17:53:01 schrieb Alexander Neundorf:
> On Thursday 26 July 2012, Johannes Zarl wrote:
> > On Wednesday 25 July 2012 22:20:55 Clinton Stimpson wrote:
> > > This has already been fixed in FindQt4 since CMake 2.8.6.
> > 
> > ...using cmake 2.8.9-rc1 from debian.
> 
> if you use it together with FindKDE4.cmake, you get the copy of
> FindQt4.cmake coming with kdelibs, which apparently does not yet have
> these fixes applied.

Yes, that's it. Thanks for the info!

  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] Disabling C for C++-only projects

2012-07-26 Thread Alexander Neundorf
On Thursday 26 July 2012, Johannes Zarl wrote:
> On Wednesday 25 July 2012 22:20:55 Clinton Stimpson wrote:
> > On Wednesday, July 25, 2012 10:06:27 PM Johannes Zarl wrote:
> > > I'm wondering if this counts as a bug in FindQt4 and FindKDE, because
> > > after all these two projects are C++, so any platform test should IMO
> > > be using the same compiler as the build-process does?
> > 
> > This has already been fixed in FindQt4 since CMake 2.8.6.
> 
> ...using cmake 2.8.9-rc1 from debian.

if you use it together with FindKDE4.cmake, you get the copy of FindQt4.cmake 
coming with kdelibs, which apparently does not yet have these fixes applied.

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] Disabling C for C++-only projects

2012-07-26 Thread Johannes Zarl
On Wednesday 25 July 2012 22:20:55 Clinton Stimpson wrote:
> On Wednesday, July 25, 2012 10:06:27 PM Johannes Zarl wrote:
> > I'm wondering if this counts as a bug in FindQt4 and FindKDE, because
> > after all these two projects are C++, so any platform test should IMO be
> > using the same compiler as the build-process does?
> 
> This has already been fixed in FindQt4 since CMake 2.8.6.

...using cmake 2.8.9-rc1 from debian. 

But I'm absolutely fine with Alexander's statement that this is a (very low 
priority) bug. This means that my understanding of 
CheckSymbolExists and CheckCXXSymbolExists is not totally wrong and that it is 
basically ok to make a project without the C language being enabled.

Sorry about the noise ;-)

Cheers,
  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] Disabling C for C++-only projects

2012-07-25 Thread Clinton Stimpson
On Wednesday, July 25, 2012 10:06:27 PM Johannes Zarl wrote:
> Hi,
> 
> Out of curiosity (and thinking about saving a couple of seconds during the
> first cmake run) I tried just to use C++ as language for some KDE program.
> 
> It turns out that without C enabled, standard modules like FindKDE, FindQt4
> and FindJPEG don't run because they use the CheckSymbolExists module.
> 
> I'm wondering if this counts as a bug in FindQt4 and FindKDE, because after
> all these two projects are C++, so any platform test should IMO be using the
> same compiler as the build-process does?
> 

This has already been fixed in FindQt4 since CMake 2.8.6.

-- 
Clinton Stimpson
Elemental Technologies, Inc
Computational Simulation Software, LLC
www.csimsoft.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] Disabling C for C++-only projects

2012-07-25 Thread Alexander Neundorf
On Wednesday 25 July 2012, Johannes Zarl wrote:
> Hi,
> 
> Out of curiosity (and thinking about saving a couple of seconds during the
> first cmake run) I tried just to use C++ as language for some KDE program.
> 
> It turns out that without C enabled, standard modules like FindKDE, FindQt4
> and FindJPEG don't run because they use the CheckSymbolExists module.
> 
> I'm wondering if this counts as a bug in FindQt4 and FindKDE, because after
> all these two projects are C++, so any platform test should IMO be using
> the same compiler as the build-process does?

Yes, but I'd consider it a very low severity bug.

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] Disabling C for C++-only projects

2012-07-25 Thread Andreas Pakulat
Hi,

On Wed, Jul 25, 2012 at 10:06 PM, Johannes Zarl  wrote:
> Hi,
>
> Out of curiosity (and thinking about saving a couple of seconds during the
> first cmake run) I tried just to use C++ as language for some KDE program.

Really? Seconds? I mean the toolchain-stuff in CMake is more or less
hardcoded anyway, there's not a lot of runtime-checking going on
there.

> It turns out that without C enabled, standard modules like FindKDE, FindQt4
> and FindJPEG don't run because they use the CheckSymbolExists module.
>
> I'm wondering if this counts as a bug in FindQt4 and FindKDE, because after
> all these two projects are C++, so any platform test should IMO be using the
> same compiler as the build-process does?

Well, on all platforms I know it actually does use the same compiler,
just under a different name :P Also some of the platforms don't have a
C compiler at all anyway (or at least none that you'd call a proper C
compiler by todays standards). That being said, technically you're
correct, they should be using CheckCXXSymbolExists instead.

Andreas
--

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