| Summary: | Switch SDK to be a self extracting python script instead of a self extracting shell script | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Joshua Watt <JPEWhacker> |
| Component: | Scripts and Tools | Assignee: | Colin McAllister <colinmca242> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | colinmca242, kergoth, randy.macleod, ross.burton |
| Version: | 0.0.0 | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Joshua Watt
2019-04-02 15:16:23 UTC
This is a good idea. We could use PyOxidizer or similar to make it truly self-contained, too. 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. Moved en masse from 4.2 to 4.3 by Randy. Bulk move of 5.1 bugs to 5.2. -- YP bug review (Randy) |