Hi Richard,

You mean copying the whole module directory and doing a “make install” in the 
remote computer?

I havent tried that, but I guess that would end up the same way, since all I’m 
doing is copying the target directory (where "make install" puts things) from 
one computer to another. This doesn’t work, by the way. I get an error that 
looks like this:

self.mymodule_detect_gen_mac_b_0 = mymodule.detect_gen_mac_b("packet_len")
AttributeError: 'module' object has no attribute 'detect_gen_mac_b'

If I take the whole module directory and redo “cmake”+”make”+”make install” it 
works perfectly, but my whole point is avoiding compiling everything again.

Thanks,

Leo

--
Leonardo S. Cardoso
Maitre de Conference
CITI lab, INSA-Lyon - INRIA



> On 20 May 2015, at 20:16 , Richard Bell <[email protected]> wrote:
> 
> Leonardo,
> 
> Have you tried copying the entire module directory (including build) from one 
> computer to another? What errors do you see when you do that? 
> 
> v/r,
> Rich
> 
> On Wed, May 20, 2015 at 10:31 AM, Leonardo S. Cardoso 
> <[email protected] 
> <mailto:[email protected]>> wrote:
> Hello everyone,
> 
> I come to you with a rather strange request :)
> 
> I’m looking into the possibility of installing OOTs that were precompiled in 
> one system onto another. 
> 
> Lets consider basic stuff first:
> 
> 1. Versions of all software are identical in both systems (linux, gnuradio, 
> uhd, build suite, etc...).
> 2. I’m copying all relevant binaries and compiled stuff from 
> $INSTALL_PREFIX/lib to another computer and installing in exactly the same 
> $INSTALL_PREFIX
> 3. LD_LIBRARY_PATH, PYTHONPATH, PKG_CONFIG_PATH, etc, are set correctly on 
> both systems and tested for OOTs build locally in each.
> 
> Will this crazy idea work? If not, why? 
> 
> If it is possible, then what will be the limitations (ex: different version 
> of software, different $INSTALL_PREFIX)?
> 
> Thank you.
> 
> Best regards
> 
> Leonardo
> 
> --
> Leonardo S. Cardoso
> Associate Professor
> CITI lab, INSA-Lyon - INRIA
> 
> 
> 
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> [email protected] <mailto:[email protected]>
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio 
> <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
> 
> 

_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to