Who Should Pay For Source Code Availability?
Remote
Loris Cro ⚡
@kristoff@hachyderm.io
mastodon 4.7.3VP of Community @ Zig Software Foundation • Zig Livecoding http://twitch.tv/kristoff_it • Creator of http://softwareyoucan.love • Blogging http://kristoff.it • Host of https://zig.show • 📧 loris@sycl.it
856 Followers
16 Following
24 Posts
Joined July 16, 2023
https://kristoff.it:
Twitch:
YouTube:
Software You Can Love:
RE: @zigtoberfest@mastodon.social
Zigtoberfest was really fun, and I'm very happy with how the European Zig community is shaping up.
Btw, I'm not in the photo because I chose the wrong time to go to the restroom :^)
Could very well have been a keynote for Software You Can Love but in some ways it's better this way :^)
Zine v0.12.0 is out, bringing a big upgrade to Ziggy, the config and frontmatter language.
*taps sign*
gingerbill calling andrew a communist is one of the weirdest things I've seen from the neo handmade community
It seems that Godot knows how to play Contributor Poker as well...
Review of Zig after 100k lines of game code by Madrigal Games.
(spoilers: not everything is perfect)
Working on a Zig library to generate SVG railroad diagrams!
RE: @winbuzzer@mastodon.social
What a terrible day to know how to read...
The next Systems Distributed has been announced. Next to it we'll also run a special one-off Zig Day Boston open to anybody!
So it seems that now everybody else is realizing that GitHub is broken as fuck in a storm of managers that have no idea what to do with the product and mindless vibecoding. Told ya.
Systems Distributed '26 is getting closer and so is the Zig Day Boston scheduled for the day before (completely free, NO conference ticket required).
Come practice your systems thinking and make software you can love with us!
The first ever Zig Day Napoli is scheduled for March 28!
Both Andrew and I will be there, join us for some good Zig...
...and some good food as well!
The vibecoding will continue until uptime improves.
-- Manager @ Microslop GitHub
pip install ziglang
Last reminder that this saturday Zig Day Naples will take place!
Join Andrew, me and other people interested in making software you can love!
Replying to
Upcoming Zig Days!
Seattle: March 21
Naples: March 28 (Andrew will be there!)
Stockholm: April 11
Nuremberg: April 11
More info on https://zig.day!
Replying to
@SonnyBonds correction, since in your case wgpu_lib is the upstream project, then you would have to do something along the lines of wgpu_dep.builder.dependencies("wgpu_lib", .{}). This is the super manual version where you reach for your dep's dependenncies. There are less invasive methods where you expose a path to consumers (similarly to how you can expose modules and artifacts) but at this point your method seems preferable (if you want only the header files, if you want the full lib you can just linkLibrary).
Replying to
@SonnyBonds You have two main kinds of consumers: Zig and C (either directly or FFI). For the former you want to create zig modules, like you are doing in the screenshot, while for the latter you want to create libraries (b.addLibrary), which will also install headers that you specify via installHeader. Zig users don't need header files if you give them a translate-c module.
I've recently made this package that you can use as a reference https://github.com/allyourcodebase/rnnoise notice how I'm creating:
- a module that contains the full implementation (+ the translate-c output as the root file)
- a module that only contains translate-c definitions in case that the user just wants those and plans to use a system-provided dynamic library
- static and dynamic library artifacts for non-Zig consumers, which also install public header files.
The only thing that I'm missing in that package is system integration options, which I have yet to really learn how to use.