xantares 09 wrote:
> >From: xantare...@hotmail.com
> >To: cmake@cmake.org
> >Date: Thu, 24 Jan 2013 08:12:49 +0000
> >Subject: [CMake] find_packge behavior regarding enabled languages

> >I noticed that when all languages are disabled through the project command:
> >project ( Foo NONE )
> >
> >... then a dependent Bar sub-package cannot be detected from it's
> >BarConfig.cmake configuration file: find_package ( Bar MODULE )
> >
> >Do you think it's a bug ? A feature ?
> >
> >I explicitely disabled all languages to avoid compiler checks which are
> >useless for my documentation package.
> >
> >Altough it works with at least one language enabled (or let default C &
> >C++), I wondered if there's by chance any mean to avoid compiler checks
> >while still being able to detect config files, or if there's a
> >undocumented behavior of the find_package command regarding languages.

> I investigated my problem further and I noticed that find_package only finds
> the config file if located on a specific location depending on enabled
> languages: - no languages enabled:              
> /usr/lib/cmake/bar/BarConfig.cmake - at least one language enabled:  
> /usr/lib64/cmake/bar/BarConfig.cmake
> 
> So selected languages have an impact on the searched library path : it takes
> the arch into account if one is enabled.
> 
> My box is a Fedora 18 x86_64 with latest cmake 2.8.10.
> Should I report it ?

I guess the reason is that it needs CMAKE_SIZEOF_VOID_P to know the difference 
between lib and lib64, but that is only known if it has at least one compiler 
to check.

But what do you need a library for if you don't have a compiler?

Eike
-- 

Attachment: 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

Reply via email to