embedding_oot_modules_or_custom_libraries_binaries_in_minus_scenario
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
embedding_oot_modules_or_custom_libraries_binaries_in_minus_scenario [2016/04/21 17:02] – mimbert | embedding_oot_modules_or_custom_libraries_binaries_in_minus_scenario [2016/04/21 17:06] (current) – mimbert | ||
---|---|---|---|
Line 16: | Line 16: | ||
There is basically no way to avoid this issue: users need to target the same gnuradio version than the one on the cortexlab nodes. | There is basically no way to avoid this issue: users need to target the same gnuradio version than the one on the cortexlab nodes. | ||
- | Actually this is not only about gnuradio, but about the whole package of software used to run the radio on the nodes. We refer to this package as the **cortexlab toolchain**. | + | Actually this is not only about gnuradio, but about the whole package of software used to run the radio on the nodes. We refer to this package as the **cortexlab toolchain**. |
- | + | ||
- | * [[http:// | + | |
- | * some gnuradio additional modules / blocks, such as blocks which interface with the radio hardware ([[http:// | + | |
- | * some gnuradio additional modules adding convenient tools, which we decided to incude, such as [[http:// | + | |
- | * software for supporting the picosdr: [[http:// | + | |
There is currently three possibilities for working with the same version of toolchain than the one on the cortexlab nodes: | There is currently three possibilities for working with the same version of toolchain than the one on the cortexlab nodes: | ||
* use the cortexlab toolchain which is installed on the airlock frontend. It is the exact same toolchain as on the nodes, the only difference is that there is no hardware (usrp, picosdr, jtag) connected to the frontend. | * use the cortexlab toolchain which is installed on the airlock frontend. It is the exact same toolchain as on the nodes, the only difference is that there is no hardware (usrp, picosdr, jtag) connected to the frontend. | ||
- | * build a cortexlab toolchain on a user's workstation. We provide the [[https:// | + | * build a cortexlab toolchain on a user's workstation. We provide the [[https:// |
* build the same version of gnuradio than on airlock, without using our '' | * build the same version of gnuradio than on airlock, without using our '' | ||
- | |||
- | Besides, the main advantage of the [[https:// | ||
- | |||
- | * as it runs as a regular user, there is zero risk to damage anything in the system, you are sure that anything it does is restricted to the rights of the user running the script. The only thing that has to be run as root is a single script generated at the end, which is easy to review and audit. | ||
- | * thus,you are sure that it does not conflict with anything in the regular directory tree structure of your system. In particular, it cannot conflit with the debian package system. | ||
- | * everything from the toolchain is kept isolated in the toolchain install directory, instead of being scattered everywhere. | ||
- | * it is possible to have more than one toolchain installed in parallel. You only need to re-run the root script to switch to a different toolchain, and reboot (or possibly only restart udev? that needs to be checked), and re-source the environment configuration script. | ||
- | |||
- | When building a toolchain on a user's workstation, | ||
===== Packaging executable binaries or libraries in a minus task scenario ===== | ===== Packaging executable binaries or libraries in a minus task scenario ===== |
embedding_oot_modules_or_custom_libraries_binaries_in_minus_scenario.txt · Last modified: 2016/04/21 17:06 by mimbert