|Subject:||Re: [Discuss-gnuradio] GNU Radio on Air Gapped Computer|
|Date:||Thu, 30 Apr 2015 09:13:02 +0200|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0|
well, Doxygen is not the best example, because it's only needed to generate documentation at build-time.
But consider this: when you set up your soon-to-be-airgapped computer, you install python 2.7.8-15a-spam including the matching development headers.
You do the same on your on-line machine.
After a month or so, you decide you might want to update the python installation on your on-line computer. You do that, it's now 2.7.9-vikings. Another month passes. You realize that "having the most recent version of GR on the air-gapped computer" might be desirable. So you use pybombs to update GNU Radio on your on-line PC.
The problem now is that the version of python on your air-gapped computer (spam) doesn't match the one that the fresh GNU Radio was linked against. Since spam doesn't have the same symbols as vikings, things go wrong as soon as you try to call a python function from C++. That might lead to confusion and ruin .
The same mechanism applies to all libraries that GNU Radio or any of the things you build on your on-line PC. So you'd have to make absolutely sure that the libraries installed on your on-line PC match the versions on the air-gapped one.
On 04/29/2015 09:13 PM, Richard Bell wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|