[JdeRobot] Two questions: ArDrone deps & out-of-source build

Victor Arribas v.arribas.urjc at gmail.com
Fri Oct 30 13:23:34 CET 2015


Reflog thread due #206

https://github.com/RoboticsURJC/JdeRobot/issues/206

2015-10-30 13:01 GMT+01:00 Victor Arribas <v.arribas.urjc en gmail.com>:

> [Resend message of 20 de octubre de 2015, 19:16 to f.perez475 en gmail.com
> Fran, you can skip it]
>
> Thanks Fran.
>
> About 2: recently, chainned CMakeLists changed from:
> add_subdirectory(child-folder, child-folder)
> To:
> add_subdirectory(child-folder)
> First one overrides defauld build dir (cmake_current_binary_dir) with
> source dir, so it forces an in-source compilation.
> Now, it will be under binary_dir.
> So for out-of-source compilation (mkdir build + cmake ..) all generated
> files will be under build tree
> (Nevertheless, cmake . will maitain in-source style for backward
> compatibility).
>
> Y love this change, but it will bite us in some ways (hardcoded relative
> paths, in-source dependencies (=config files)).
> Workaround? Just build in source, so...
>
> Therefore, as long as not al cmakelists took this change, will be the
> official method?
> Just to adapt it if it is part of my changeset (so at least I test the
> change).
>
> About 3:
> I do not understand cmake pretty well, neither possible behavior changes
> since ancient versions.
> So, for example, if we have:
> jderobot/a/b/c (directories)
> And b is just a cmakelist with add_subdirectory(c)
> Could this cmakelists disapear in favor of
> add_subdirectory(b/c) at 'a' level?
>
> ps: only drawback to avoid it is that binary_dir will lost "c prefix"
> hierarchy, so b will no longer be at binary path. But i have no idea.
>
> 2015-10-20 18:17 GMT+02:00 Francisco Pérez <f.perez475 en gmail.com>:
>
>> Hi Victor,
>>
>> 1- As the ardrone_server driver needs the parrot SDK to work, it make
>> sense
>> that it throws an error if there is no SDK installed. If this error does
>> not
>> appear in compilation time, it has to be fixed. On the other hand it also
>> depends on the installation method of JdeRobot, as the
>> installation-by-packages would install all the dependencies automatically;
>> if you, otherwise, choose the manual installation (from source) you'll
>> need
>> to install all the dependencies before compiling JdeRobot (which includes
>> the ardrone SDK).
>>
>> 2- Which commit do you mean? I don't understand quite well this question
>> :S
>>
>> 3- Do you mean in the JdeRobot compilation chain? I've not tested it, but
>> I
>> think it would exist a workaround for this! Fran or Roberto will know
>> better!
>>
>>
>>
>> --
>> View this message in context:
>> http://jderobot-developer-list.2315034.n4.nabble.com/JdeRobot-Two-questions-ArDrone-deps-out-of-source-build-tp4642782p4642785.html
>> Sent from the Jderobot Developer List mailing list archive at Nabble.com.
>> _______________________________________________
>> Jde-developers mailing list
>> Jde-developers en gsyc.es
>> http://gsyc.escet.urjc.es/cgi-bin/mailman/listinfo/jde-developers
>>
>
>
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: http://gsyc.escet.urjc.es/pipermail/jde-developers/attachments/20151030/06010d31/attachment.htm 


More information about the Jde-developers mailing list