Jackie9527
6ad544fcd8
build sqlite lib linking against msvcrt.dll, remove the following warning:
|
2 年之前 | |
|---|---|---|
| Scripts | 2 年之前 | |
| package-system | 2 年之前 | |
| .gitignore | 3 年之前 | |
| LICENSE.txt | 4 年之前 | |
| LICENSE_APACHE2.TXT | 4 年之前 | |
| LICENSE_MIT.TXT | 4 年之前 | |
| NOTICES.txt | 2 年之前 | |
| README.md | 3 年之前 | |
| SPDX-Licenses.csv | 2 年之前 | |
| SPDX-Licenses.json | 2 年之前 | |
| package_build_list_host_darwin.json | 2 年之前 | |
| package_build_list_host_linux-aarch64.json | 2 年之前 | |
| package_build_list_host_linux.json | 2 年之前 | |
| package_build_list_host_windows.json | 2 年之前 |
README.md
3p-package-source repo
This is where the "sources" (ie, build scripts which make packages) for the O3DE package system are located.
Note that the "sources" of most packages are not actually stored here, most "package sources" actually just consist of a script which fetches the source code (or prebuilt packages) from somewhere else, constructs a temporary folder image for it, and then lets the package system pack that folder up as the package.
In general
- Add your new package to the appropriate package_build_list_host_xxxx file
- Put the scripts or instructions to construct the package image folder into the package-system subfolder
Recommendation would be to make any temp packing in a folder called /temp/ so as to use the current git ignores.
Some notable examples
- xxhash - a tiny header-only library that is just committed-as-is since it fits in git. No build scripts.
- OpenSSL - this one uses vcpkg to build the package image.
- Lua - this one uses a script called pull_and_build_from_git.py (in Scripts/extras) to build the package image.
See the documentation (README.md in 3p-package-scripts repo for a full description of how to author packages.)