# Re: Copying OOT blocks to a different system

**URL:** <https://www.ruby-forum.com/t/re-copying-oot-blocks-to-a-different-system/241350>\
**Category:** GNU Radio\
**Created:** [March 31, 2015, 9:17pm UTC](https://www.ruby-forum.com/t/re-copying-oot-blocks-to-a-different-system/241350 "2015-03-31T21:17:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![musicdenotation](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ea666f/32.png) [@musicdenotation](https://www.ruby-forum.com/u/musicdenotation)\
**Post date:** [March 31, 2015, 9:17pm UTC](https://www.ruby-forum.com/t/re-copying-oot-blocks-to-a-different-system/241350/1 "2015-03-31T21:17:27Z")

</div>

Thanks Marcus, that worked. And it is much simpler.

- John

From: Marcus Müller

you shouldn’t use gr\_modtool to create a new module on your destination  
system – just take your OOT’s folder, and copy it over to the  
destination system, deleting/omitting your build folder. Then rebuild  
and install – CMake should make sure to find all the libraries on the  
destination system itself.

In fact, OOTs were designed to be self-contained and transportable like  
this – which is what tools like pybombs rely on: you can just copy/git  
clone the OOT directory tree, mkdir build, cd build, cmake …, make and  
make install and be set.