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 revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| embedding_oot_modules_or_custom_libraries_binaries_in_minus_scenario [2016/04/14 15:37] – mimbert | embedding_oot_modules_or_custom_libraries_binaries_in_minus_scenario [2016/04/21 17:02] – mimbert | ||
|---|---|---|---|
| Line 35: | Line 35: | ||
| * everything from the toolchain is kept isolated in the toolchain install directory, instead of being scattered everywhere. | * 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. | * 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