Welcome to the PTXdist Universe¶
- 1. Welcome to the Embedded World
- 2. Getting a working Environment
- 3. PTXdist User’s Manual
- 4. PTXdist Developer’s Manual
- 4.1. PTXdist’s Directory Hierarchy
- 4.2. Adding New Packages
- 4.3. Advanced Rule Files
- Adding Static Configure Parameters
- Adding Dynamic Configure Parameters
- Managing External Compile Time Dependencies
- Managing External Compile Time Dependencies on Demand
- Managing External Runtime Dependencies
- Managing Plain Makefile Packages
- Managing CMake/QMake/Meson Packages
- Managing Python Packages
- Managing Cargo Packages
- 4.4. Patching Packages
- 4.5. Adding Binary Only Files
- 4.6. Creating New Package Templates
- 4.7. Tracking licensing information in packages
- 4.8. Layers in PTXdist
- 4.9. Kconfig Diffs
- 4.10. Code Signing
- 5. PTXdist Reference
- 5.1. Variables Reference
- 5.2. Rule File Macro Reference
- targetinfo
- touch
- clean
- world/get, world/extract, world/prepare, world/compile, world/install
- extract
- compile
- world/execute, execute
- ptx/image-install, ptx/image-install-link, world/image-clean
- world/image-fit
- install_copy
- install_tree
- install_alternative_tree
- install_alternative
- install_link
- install_archive
- install_glob
- install_lib
- install_replace
- ptx/cfghash, ptx/cfghash-file
- ptx/endis, ptx/disen, ptx/wow, ptx/wwo, ptx/yesno, ptx/truefalse, ptx/falsetrue, ptx/onoff, ptx/ifdef
- ptx/get-alternative
- ptx/in-path
- ptx/in-platformconfigdir
- 5.3. Rule File Layout
- 5.4. PTXdist parameter reference
- 5.5. Code Signing Helper Functions
- 6. Various Aspects of Daily Work
- 6.1. Using an External Kernel Source Tree
- 6.2. Using the Code Signing Infrastructure with the Kernel Recipe
- 6.3. Discovering Runtime Dependencies
- 6.4. Debugging with CPU emulation
- 6.5. Migration between Releases
- 6.6. Increasing Build Speed
- 6.7. Using a Distributed Compiler
- 6.8. Using Pre-Built Archives
- 6.9. Downloading Packages from the Web
- 6.10. Creating Autotools based Packages
- 6.11. Controlling Package Dependencies in more Detail
- 6.12.
umask
Pitfall - 6.13. Read Only Filesystem
- 6.14. Using a userland NFS Server for the Target
- 6.15. Supporting Multiple Device Variants in one Platform
- 6.16. The PTXdist User Manual
- 6.17. Integrate project specific Documentation into the Manual
- 7. Contributing to PTXdist
- 8. Frequently Asked Questions (FAQ)
- 8.1. PTXdist does not support to generate some files in a way I need them. What can I do?
- 8.2. How can I stop PTXdist to build in parallel?
- 8.3. I get errors like “unterminated call to function ‘call’: missing ‘)’”
- 8.4. I got a message similar to “package <name> is empty. not generating.” What does it mean?
- 8.5. How do I download all required packages at once?
- 8.6. I want to backup all source archives for my BSP
- 8.7. OSELAS toolchain fails to start due to missing libraries
- 8.8. PTXdist does not find my own sources: “Unknown format, cannot extract”
- 8.9. Using more than one kernel version per BSP
- 8.10. Using Java packages
- 8.11. I get the error “cannot run ‘/etc/init.d/rcS’: No such file or directory”
- 8.12. I get the error “ptxdist: archives: command not found”
- 8.13. I have adapted my own rule file’s targetinstall stage, but PTXdist does not install the files
- 9. Getting help