-
Notifications
You must be signed in to change notification settings - Fork 184
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
CPack artifacts file name format compliance (#4811)
This PR fixes these concerns with release artifact filenames: 1. Windows having `amd64` in name instead of `x86_64` 2. Package name missing full tag as name 3. Package name missing commit hash Number 1. is fixed by checking CMake variabe CMAKE_SYSTEM_PROCESSOR and if its set to `AMD64` the packaging logic uses `x86_64` instead. Number 2. and 3. are fixed by packaging process requiring `TILEDB_PACKAGE_VERSION` environment variable to be present when calling packaging commands (`make package` or `cpack ...` or similar) An example pipeline in my fork: https://github.com/dudoslav/TileDB/actions/runs/8266657611 An example release `t14` in my fork: https://github.com/dudoslav/TileDB/releases/tag/t14 (Please wait for them to finish) --- TYPE: NO_HISTORY DESC: Fix CPack packaging issues with file name format
- Loading branch information
Showing
4 changed files
with
30 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters