13259 2019-04-02 15:16:23 +0000 Switch SDK to be a self extracting python script instead of a self extracting shell script 2025-05-13 12:02:14 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 0.0.0 x86 Multiple NEW Medium enhancement Future 1 JPEWhacker colinmca242 colinmca242 kergoth randy.macleod ross.burton --- --- Yes (doc changes required) oldest_to_newest 83408 0 JPEWhacker 2019-04-02 15:16:23 +0000 The current SDKs generated by Yocto are self extracting shell scripts, but they invoke a number of python scripts as part of the extraction process. Reworking the entire process in Python should aid in maintenance. In addition to this, a python script would be more portable to other platforms (e.g. Windows) than a shell script. 93913 1 kergoth 2022-08-25 15:38:54 +0000 This is a good idea. We could use PyOxidizer or similar to make it truly self-contained, too. 93915 2 JPEWhacker 2022-08-25 15:45:26 +0000 My actual thought on how to do this is a bit simpler: There is a little know but very useful behavior of python that if you pass it a zip file that contians a file name __main__.py, it will extract the archive and execute the __main__.py program. These files are commonly given a .pyz extension in Windows, and for Unix, you can prefix the zip file with a "#! /usr/bin/env python3" because of how zip files are constructed (the TOC is actually at the end of the file). The idea would be to include the normal SDK tar file in the zip archive, then rewrite the relocation portions into python and put the extraction + relocation in __main__.py. 95438 3 randy.macleod 2023-04-21 18:45:45 +0000 Moved en masse from 4.2 to 4.3 by Randy. 100078 4 randy.macleod 2024-10-31 15:09:20 +0000 Bulk move of 5.1 bugs to 5.2. -- YP bug review (Randy)