Skip to content

Commit 8e4a97d

Browse files
committed
register openkal-llvm-runtime 0.14.0
`__libunwind_config.h` --- the INSTALLED header that sizes `unw_context_t` by the target's register save area --- reads `__MCPP_TARGET_WINDOWS__` and keeps `|| defined(__CYGWIN__)` beside it. Two operands cover every engine, so the order of releases does not matter. A SIXTH PATCH SITE, FOUND BY ENUMERATING RATHER THAN BY FAILING: `compiler-rt/lib/builtins/int_lib.h`. That file is not installed, so it takes a package-private define (`OPENKAL_TARGET_WINDOWS`) instead of the engine's name --- the distinction is whose compile reads the header, which is the same distinction that decides whether a macro belongs to the engine at all. Pins openkal-musl 0.19.0, registered in #453, which carries the matching change to `bits/setjmp.h`. Cross-verified against the mcpp branch that withdraws `__CYGWIN__`: five jobs green, including the Windows-host row of `host-dimension`, which builds `x86_64-windows-gnu` and resolved `openkal-musl@0.19.0`. That row is the one that matters here, since the macro exists only on Windows targets.
1 parent 5198b69 commit 8e4a97d

1 file changed

Lines changed: 34 additions & 0 deletions

File tree

‎pkgs/o/openkal-llvm-runtime.lua‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,19 @@
2727
-- favour of definitions the package's own manifest now gives per target
2828
-- (design §3.4). Neither the release nor its sha256 exist yet -- this
2929
-- comment marks the entry as prepared and blocked, not as data to invent.
30+
-- 0.14.0 reads `__MCPP_TARGET_WINDOWS__` in `__libunwind_config.h`, the
31+
-- INSTALLED header that sizes `unw_context_t` by the target's register save
32+
-- area, keeping `|| defined(__CYGWIN__)` beside it. Two operands cover every
33+
-- engine, so the order of releases does not matter.
34+
--
35+
-- IT ALSO CARRIES A SIXTH PATCH SITE, FOUND BY ENUMERATING RATHER THAN BY
36+
-- FAILING: `compiler-rt/lib/builtins/int_lib.h`. That file is NOT installed,
37+
-- so it takes a package-private define (`OPENKAL_TARGET_WINDOWS`) rather than
38+
-- the engine's name --- the distinction is whose compile reads the header.
39+
--
40+
-- It pins openkal-musl 0.19.0, which carries the matching change to
41+
-- `bits/setjmp.h`.
42+
--
3043
package = {
3144
spec = "1",
3245
namespace = "mcpplibs",
@@ -38,6 +51,13 @@ package = {
3851

3952
xpm = {
4053
linux = {
54+
["0.14.0"] = {
55+
url = {
56+
GLOBAL = "https://github.com/mcpplibs/openkal-llvm-runtime/archive/refs/tags/0.14.0.tar.gz",
57+
CN = "https://gitcode.com/mcpp-res/openkal-llvm-runtime/releases/download/0.14.0/openkal-llvm-runtime-0.14.0.tar.gz",
58+
},
59+
sha256 = "689b753523b12b4c4a866193a28f557c502f98ef796396d541644e52de64fb68",
60+
},
4161
["0.13.0"] = {
4262
url = {
4363
GLOBAL = "https://github.com/mcpplibs/openkal-llvm-runtime/archive/refs/tags/0.13.0.tar.gz",
@@ -208,6 +228,13 @@ package = {
208228
},
209229
},
210230
macosx = {
231+
["0.14.0"] = {
232+
url = {
233+
GLOBAL = "https://github.com/mcpplibs/openkal-llvm-runtime/archive/refs/tags/0.14.0.tar.gz",
234+
CN = "https://gitcode.com/mcpp-res/openkal-llvm-runtime/releases/download/0.14.0/openkal-llvm-runtime-0.14.0.tar.gz",
235+
},
236+
sha256 = "689b753523b12b4c4a866193a28f557c502f98ef796396d541644e52de64fb68",
237+
},
211238
["0.13.0"] = {
212239
url = {
213240
GLOBAL = "https://github.com/mcpplibs/openkal-llvm-runtime/archive/refs/tags/0.13.0.tar.gz",
@@ -378,6 +405,13 @@ package = {
378405
},
379406
},
380407
windows = {
408+
["0.14.0"] = {
409+
url = {
410+
GLOBAL = "https://github.com/mcpplibs/openkal-llvm-runtime/archive/refs/tags/0.14.0.tar.gz",
411+
CN = "https://gitcode.com/mcpp-res/openkal-llvm-runtime/releases/download/0.14.0/openkal-llvm-runtime-0.14.0.tar.gz",
412+
},
413+
sha256 = "689b753523b12b4c4a866193a28f557c502f98ef796396d541644e52de64fb68",
414+
},
381415
["0.13.0"] = {
382416
url = {
383417
GLOBAL = "https://github.com/mcpplibs/openkal-llvm-runtime/archive/refs/tags/0.13.0.tar.gz",

0 commit comments

Comments
 (0)