Re: [CMake] Modifying the FindBoost.cmake module

2016-06-27 Thread Andreas Naumann 

Hey,

if you would use the FindBoost.cmake module from cmake itself, you could 
set the environment variable BOOST_ROOT to the second path.


Regards,
Andreas

Am 28.06.2016 um 01:21 schrieb Sambeet Panigrahi:

Hi,
I  am using Cmake to build Orocos RTT. There is a FindBoost.cmake 
module available in the config directory which the project uses.Now I 
have got two boost installations one in

1)/usr/include/boost
2)~/NewRockPort/x86/Install/boost

The second installation is the one I want to use .However The 
find_package command always goes on to find the first installation. 
There is a section in the file


  SET(_boost_INCLUDE_SEARCH_DIRS
"$ENV{INSTALL_PREFIX}/boost/include/"
C:/boost/include
C:/boost
"$ENV{ProgramFiles}/boost/include"
"$ENV{ProgramFiles}/boost"
/sw/local/include
in which I have tried to set the second installation's address, but it 
always points to the first.I have also tried to set the second 
installation from environment but somehow it always detects the first 
installation.


What can I do to include the second installation in my project?

Regards
Sambeet




--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[CMake] Modifying the FindBoost.cmake module

2016-06-27 Thread Sambeet Panigrahi 
Hi,
I  am using Cmake to build Orocos RTT. There is a FindBoost.cmake module
available in the config directory which the project uses.Now I have got two
boost installations one in
1)/usr/include/boost
2)~/NewRockPort/x86/Install/boost

The second installation is the one I want to use .However The find_package
command always goes on to find the first installation. There is a section
in the file

  SET(_boost_INCLUDE_SEARCH_DIRS
"$ENV{INSTALL_PREFIX}/boost/include/"
C:/boost/include
C:/boost
"$ENV{ProgramFiles}/boost/include"
"$ENV{ProgramFiles}/boost"
/sw/local/include

in which I have tried to set the second installation's address, but it
always points to the first.I have also tried to set the second installation
from environment but somehow it always detects the first installation.

What can I do to include the second installation in my project?

Regards
Sambeet
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CMake terminology

2016-06-27 Thread Craig Scott 
On Tue, Jun 28, 2016 at 12:04 AM, Eric Noulard 
wrote:

>
>
> 2016-06-25 17:42 GMT+02:00 Ruslan Baratov :
>
>> On 25-Jun-16 10:44, Craig Scott wrote:
>>
>> One of the slight wrinkles here is that the distinction between configure
>> and generation times is now a little stronger due to generator expressions.
>> In order to really understand generator expressions, you cannot really
>> avoid getting your head around configure and generate being distinct parts
>> of the process. Personally, I tend to gloss over the distinction when
>> explaining things so as not to distract the reader, but if I'm explaining
>> something to do with generator expressions, then the distinction has to be
>> made and I deliberately use the terms *configure* and *generation*
>> stages.
>>
>> I'm not sure I understand the link between "generator expressions" and
>> "confusing configure+generate stage". Do you mean "generator expressions"
>> on "configure+generate stage" vs "build stage"?
>>
>
> Generator expression came up because one needs to evaluate some variable
> value [apparently]at "build time"
> like knowing the exact name (with path) of a target (using TARGET_FILE
> generator expression in custom command).
>
> Knowing that "generator expression" are in fact evaluated during
> "generation step" and not really at build time
> is an implementation detail. (Which is a big one for implementors) but not
> really important to user.
>

My original comment was more about the fact that users have to understand
that the *result* of a generator expression is not available at configure
time. This is what makes them unique compared to things like ordinary CMake
variables. A classic case of this is where the developer may want to know
the binary directory of a particular target. In the past, they might try
using the LOCATION target property, but this would have been wrong for
multi-config generators like Xcode or Visual Studio. The right way to do it
is to use a generator expression like $, but you
cannot use that in contexts where the value is needed immediately, such as
in a call to configure_file(). This example is contrived (there are other
ways to achieve the developer's goal), but it illustrates a common thought
process and if the developer doesn't understand when a generator expression
result is computed/available, they won't understand why using one in such
contexts doesn't work.

Not my best explanation, but hopefully that made sense. ;)

-- 
Craig Scott
Melbourne, Australia
http://crascit.com
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CTest periodic freeze under MacOS

2016-06-27 Thread Bill Hoffman 

On 6/27/2016 5:57 AM, ycollette.nos...@free.fr wrote:

I forgot to say that the cmake version installed on macos is 3.4.3.

Can you try a more recent version of cmake?

-Bill
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] subversion

2016-06-27 Thread Andreas Naumann 
The discussion is interesting and ends with the question, whether the 
macro "Subversion_IS_WC" is usable. As I understand the other arguments are

*leave the FATAL_ERROR as default for backwards compatibility
*the suggested patch hides the error message if error_quite is set .
*calling svn info twice is felt to be a waste, if the result is 
desired anyway.


So, I would suggest to extend Erik Johanssons patch from 
http://www.mail-archive.com/cmake@cmake.org/msg26817.html by storingto  
the error message and svn error code in an extra variable.
Than, we have the ability to ignore errors due to "wrong" working 
directories and to analyze the error, if the user is interested in the 
error.
In my opinion, a hard fail is annoying, because the user is not able to 
recover from the error.


Regards,
Andreas

Am 27.06.2016 um 12:57 schrieb Marcel Loose:


See also https://cmake.org/Bug/view.php?id=10200

Cheers,
Marcel Loose.


On 27/06/16 09:23, Andreas Naumann wrote:
Thanks for the 6 year old hint. But obviously, the patch is not in 
any recent cmake version.
Therefore, I could use it in my own project and ship my own 
FindSubversion.cmake.. which is quite ugly.

*Gesendet:* Montag, 27. Juni 2016 um 03:11 Uhr
*Von:* Nagger 
*An:* cmake@cmake.org
*Betreff:* Re: [CMake] subversion
Am 24.06.2016 um 19:48 schrieb Andreas Naumann:

> At the moment, I check, if my directory is a working copy and if it is
> not, the version variable is not defined. In my oppinion, it would be
> better, if the macro from the subversion module would simply define a
> variable "is_working_directory" instead of failing hard.

See https://cmake.org/pipermail/cmake/2010-January/034862.html


--

Powered by www.kitware.com 

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ


Kitware offers various services to support the CMake community. For 
more information on each offering, please visit:


CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html


Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake








--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CMake terminology

2016-06-27 Thread Eric Noulard 
2016-06-25 17:42 GMT+02:00 Ruslan Baratov :

> On 25-Jun-16 10:44, Craig Scott wrote:
>
> One of the slight wrinkles here is that the distinction between configure
> and generation times is now a little stronger due to generator expressions.
> In order to really understand generator expressions, you cannot really
> avoid getting your head around configure and generate being distinct parts
> of the process. Personally, I tend to gloss over the distinction when
> explaining things so as not to distract the reader, but if I'm explaining
> something to do with generator expressions, then the distinction has to be
> made and I deliberately use the terms *configure* and *generation* stages.
>
> I'm not sure I understand the link between "generator expressions" and
> "confusing configure+generate stage". Do you mean "generator expressions"
> on "configure+generate stage" vs "build stage"?
>

Generator expression came up because one needs to evaluate some variable
value [apparently]at "build time"
like knowing the exact name (with path) of a target (using TARGET_FILE
generator expression in custom command).

Knowing that "generator expression" are in fact evaluated during
"generation step" and not really at build time
is an implementation detail. (Which is a big one for implementors) but not
really important to user.




-- 
Craig Scott
Melbourne, Australia
http://crascit.com





-- 
Eric
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] subversion

2016-06-27 Thread Marcel Loose 
See also https://cmake.org/Bug/view.php?id=10200

Cheers,
Marcel Loose.


On 27/06/16 09:23, Andreas Naumann wrote:
> Thanks for the 6 year old hint. But obviously, the patch is not in any
> recent cmake version.
> Therefore, I could use it in my own project and ship my own
> FindSubversion.cmake.. which is quite ugly.
>  
> *Gesendet:* Montag, 27. Juni 2016 um 03:11 Uhr
> *Von:* Nagger 
> *An:* cmake@cmake.org
> *Betreff:* Re: [CMake] subversion
> Am 24.06.2016 um 19:48 schrieb Andreas Naumann:
>
> > At the moment, I check, if my directory is a working copy and if it is
> > not, the version variable is not defined. In my oppinion, it would be
> > better, if the macro from the subversion module would simply define a
> > variable "is_working_directory" instead of failing hard.
>
> See https://cmake.org/pipermail/cmake/2010-January/034862.html
>
>
> --
>
> Powered by www.kitware.com 
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For
> more information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
>
>

<>

signature.asc
Description: OpenPGP digital signature
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CTest periodic freeze under MacOS

2016-06-27 Thread ycollette . nospam 
I forgot to say that the cmake version installed on macos is 3.4.3.

- Mail original -
De: "ycollette nospam" 
À: "cmake" 
Envoyé: Lundi 27 Juin 2016 11:56:14
Objet: [CMake] CTest periodic freeze under MacOS

Hello,

I don't really know if it's a cmake / ctest bug but when I launch tests. I 
added a timeout limit for each tests. This timeout is set to 120 sec.
Some tests fail after a timeout. And in the log file, the timemout has a 
different value. For example, it can be 280 seconds. This occurs for one tests 
out of 20.
Maybe this is a MacOS bug (some kernel freeze) but I don't know how to track 
this down to cmake or MacOS.

Best regards,

YC
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[CMake] CTest periodic freeze under MacOS

2016-06-27 Thread ycollette . nospam 
Hello,

I don't really know if it's a cmake / ctest bug but when I launch tests. I 
added a timeout limit for each tests. This timeout is set to 120 sec.
Some tests fail after a timeout. And in the log file, the timemout has a 
different value. For example, it can be 280 seconds. This occurs for one tests 
out of 20.
Maybe this is a MacOS bug (some kernel freeze) but I don't know how to track 
this down to cmake or MacOS.

Best regards,

YC
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] subversion

2016-06-27 Thread Andreas Naumann 

Thanks for the 6 year old hint. But obviously, the patch is not in any recent cmake version.

Therefore, I could use it in my own project and ship my own FindSubversion.cmake.. which is quite ugly.

 

Gesendet: Montag, 27. Juni 2016 um 03:11 Uhr
Von: Nagger 
An: cmake@cmake.org
Betreff: Re: [CMake] subversion

Am 24.06.2016 um 19:48 schrieb Andreas Naumann:

> At the moment, I check, if my directory is a working copy and if it is
> not, the version variable is not defined. In my oppinion, it would be
> better, if the macro from the subversion module would simply define a
> variable "is_working_directory" instead of failing hard.

See https://cmake.org/pipermail/cmake/2010-January/034862.html


--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake



-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake