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 revisionNext revisionBoth sides next revision | ||
embedding_oot_modules_or_custom_libraries_binaries_in_minus_scenario [2016/04/12 15:25] – mimbert | embedding_oot_modules_or_custom_libraries_binaries_in_minus_scenario [2016/04/14 15:44] – [gnuradio version / toolchain version] mimbert | ||
---|---|---|---|
Line 36: | Line 36: | ||
* 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 ===== | ||
Line 86: | Line 87: | ||
$ make | $ make | ||
$ make DESTDIR=/ | $ make DESTDIR=/ | ||
+ | $ mv / | ||
+ | $ rm -rf / | ||
==== multiple chained dependencies ==== | ==== multiple chained dependencies ==== | ||
Line 92: | Line 95: | ||
In this situation, you need to compile everything in reverse order starting from the end of the chain (the libraries which have no custom dependencies. In the previous example, the order would be //E//, //D//, //C//, //B//, //A//). The challenge is to be able to tell following libraries (in the order of compilation) where to find previous ones includes (for compilation) and libs (for linking) | In this situation, you need to compile everything in reverse order starting from the end of the chain (the libraries which have no custom dependencies. In the previous example, the order would be //E//, //D//, //C//, //B//, //A//). The challenge is to be able to tell following libraries (in the order of compilation) where to find previous ones includes (for compilation) and libs (for linking) | ||
+ | |||
+ | FIXME explain how to, when compiling //D//, telling it where to find //E// | ||
embedding_oot_modules_or_custom_libraries_binaries_in_minus_scenario.txt · Last modified: 2016/04/21 17:06 by mimbert