Support #315
Updated by Florian Lier about 10 years ago
If you have a look at the YARP-bindings folder structure:
https://github.com/robotology/yarp
The bindings folder is located in $YARP_ROOT/bindings. If you add a <code>"sub-directory"</code> variable to your recipe, which is needed in this case, the analysis works well. However, the according Jenkins job is then comprised of two build steps:
1. #1
<pre>
<code>
mv $(find "bindings" -maxdepth 1 -mindepth 1) .
</code>
</pre>
2.
<pre>
<code>
#2 cmake config, compile & install ...
</code>
</pre>
#1 will already fail because the folder "bindings" contains a folder called "src" which also exists in $YARP_ROOT folder (c.f. github)
I am not so sure if this is a corner case or not --- however I guess we need to address this.
https://github.com/robotology/yarp
The bindings folder is located in $YARP_ROOT/bindings. If you add a <code>"sub-directory"</code> variable to your recipe, which is needed in this case, the analysis works well. However, the according Jenkins job is then comprised of two build steps:
1. #1
<pre>
<code>
mv $(find "bindings" -maxdepth 1 -mindepth 1) .
</code>
</pre>
2.
<pre>
<code>
#2 cmake config, compile & install ...
</code>
</pre>
#1 will already fail because the folder "bindings" contains a folder called "src" which also exists in $YARP_ROOT folder (c.f. github)
I am not so sure if this is a corner case or not --- however I guess we need to address this.