Hello.

I maintain my own build chain and i've faced the same problem.

As workaround i link the rtt dir.

So :
I download orocos-rtt-2.X.X-src.tar.gz
I extract orocos-rtt-2.X.X-src.tar.gz
I link orocos-toolchain-2.X.X/rtt to orocos-rtt-2.X.X

I think that the packaging of the orocos-{rtt,ocl}-2.X.X-src.tar.gz archives is not conventional. In every project 'project-x.y.z.tar.gz' decompress as 'project-x.y.z'.

So +1 for the request.

Paul.

On 04/08/2011 07:47 PM, Philippe Hamelin wrote:
> Hello,
>
> I'm currently working on adding Orocos to buildroot. It is actually a little
> bit annoying since the orocos-rtt-2.X.X-src.tar.gz
> and orocos-ocl-2.X.X-src.tar.gz archives don't have the same directory
> structure than the git repo, i.e.:
>
> Source tar.gz:
>
> orocos-toolchain/rtt/[rtt, test, ...]
>
> Git tree:
>
> rtt/[rtt, test, ...]
>
> So, a patch generated from the GIT tree can't be applied directly on the
> uncompressed .tar.gz archive because there's one more directory
> level. Therefore, I have to hack each GIT patch to make it work through
> buildroot.
>
> Is it possible to modify the published archives to ensure that they have
> exactly the same directory tree than the GIT repo ?
>
> Philippe
>
>