CI: fixes #429
No reviewers
Labels
No labels
CI
all
basisu
blog
bug
build
contributor-friendly
core
correctness
deferred
dev
direct3d-headers
docs
driver-os-issue
duplicate
dxcompiler
editor
examples
experiment
feature-idea
feedback
flac
freetype
gamemode
gkurve
glfw
gpu
gpu-dawn
harfbuzz
help welcome
in-progress
infrastructure
invalid
libmach
linux-audio-headers
long-term
mach
mach.gfx
mach.math
mach.physics
mach.testing
model3d
needs-triage
object
opengl-headers
opus
os/linux
os/macos
os/wasm
os/windows
package-manager
priority
proposal
proposal-accepted
question
roadmap
slipped
stability
sysaudio
sysgpu
sysjs
validating-fix
vulkan-zig-generated
wayland-headers
website
wontfix
wrench
www
x11-headers
xcode-frameworks
zig-update
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
hexops/mach!429
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -51,0 +52,4 @@test_app.setBuildMode(mode);test_app.setTarget(target);link(b, test_app, .{ .freetype = .{ .brotli = true } });test_app.install();I've been making an effort to not create unused static libraries (which add to compile times), and not to install them for the reasons described in https://github.com/hexops/mach/issues/232
This change and the GLFW change below go against that. But why? How's it helpful?
@ -51,0 +52,4 @@test_app.setBuildMode(mode);test_app.setTarget(target);link(b, test_app, .{ .freetype = .{ .brotli = true } });test_app.install();because
zig buildneed to do something. otherwise e.g cross-compiling in CI is pointlessEither this should be just
libasound2(not-dev), or whatever header dependency we have in here should be distributed via https://github.com/hexops/sdk-linux-x86_64 and https://github.com/hexops/sdk-linux-aarch64 instead.It's a bit unfortunate we now have different formatting for CI files throughout this repository.
I suggest we add a new script:
dev/ci-lint.shwhich runs:on all our CI yml files.
@ -51,0 +52,4 @@test_app.setBuildMode(mode);test_app.setTarget(target);link(b, test_app, .{ .freetype = .{ .brotli = true } });test_app.install();OK, I see what you're going for here. But it doesn't seem like we should
.install()these, as they are for testing only after all.Separately, I want to ask: does
zig buildnot build the test binary themselves? It seems to me we should be able to havezig buildbuild the tests.. and those should build for the target OS, too - and then we wouldn't need to build useless static libraries like this.(I can address this in a future PR)
(should address this before merging)
@ -51,0 +52,4 @@test_app.setBuildMode(mode);test_app.setTarget(target);link(b, test_app, .{ .freetype = .{ .brotli = true } });test_app.install();(should address this before merging)
@ -51,0 +52,4 @@test_app.setBuildMode(mode);test_app.setTarget(target);link(b, test_app, .{ .freetype = .{ .brotli = true } });test_app.install();there's
b.addTestExei'd tried without
-devbut it didn't work. i do the same in my machine (linux mint)yamlfmtresults the same output. at least im gonna say it has nothing to do with quotes",'EDIT: i did a lot of research but didn't find a good yaml formatter. i think we should just have to be careful with yaml files
@ -51,0 +52,4 @@test_app.setBuildMode(mode);test_app.setTarget(target);link(b, test_app, .{ .freetype = .{ .brotli = true } });test_app.install();addTestExelooks good to me!What part about it didn't work? This would indicate cross-compilation won't work
To be clear, I am fine with the formatting being anything (double quotes, whatever) as long as we have a way for it to be consistent. We can use yamlfmt.
missing headers/static libs
i think actionlint is enough and yaml formatters doesn't make any change as long as we just edit github workflows. that's why there's no many yaml formatters, or at least they are unused in most cases
i mean yaml is already very strict. formatting a formatted file make no sense
https://github.com/hexops/mach/issues/430
https://github.com/hexops/mach/issues/431
@ -51,0 +52,4 @@test_app.setBuildMode(mode);test_app.setTarget(target);link(b, test_app, .{ .freetype = .{ .brotli = true } });test_app.install();https://github.com/hexops/mach/issues/433
Filed issues for my outstanding concerns with this PR. Will merge now since there are good changes here otherwise.
omg i had a lot of changes. forgot to mark as draft lol
ah gotcha, my bad