ChanServ changed the topic of #zig to: zig programming language | ziglang.org | be excellent to each other | channel logs: https://irclog.whitequark.org/zig/
arBmind has quit [Quit: Leaving.]
<GitHub92>
[zig] ibara opened pull request #551: Add OpenBSD support (WIP) (master...master) https://git.io/vdd4X
hasen_judy has joined #zig
hasen_judy has quit [Ping timeout: 255 seconds]
scurest has quit [Quit: Page closed]
tiehuis has joined #zig
hasen_judy has joined #zig
hasen_judy has quit [Ping timeout: 246 seconds]
achambe has joined #zig
Andris_zbx has joined #zig
tiehuis has quit [Quit: WeeChat 1.9.1]
hasen_judy has joined #zig
hasen_judy has quit [Ping timeout: 252 seconds]
arBmind has joined #zig
_whitelogger has quit [K-Lined]
_whitelogger has joined #zig
arBmind has quit [Quit: Leaving.]
achambe has quit [Ping timeout: 260 seconds]
hasen_judy has joined #zig
hasen_judy has quit [Ping timeout: 252 seconds]
arBmind has joined #zig
arBmind1 has joined #zig
arBmind has quit [Ping timeout: 252 seconds]
hasen_judy has joined #zig
hasen_judy has quit [Remote host closed the connection]
hasen_judy has joined #zig
pupp has joined #zig
Dimenus has joined #zig
<Dimenus>
does anyone here compile Zig in debug on a regular basis?
<pupp>
well, I compile zig with debug info, I'm on windows though
<Dimenus>
i am also on windows
<pupp>
compiler?
<Dimenus>
MSVC x64 2017
<pupp>
I'm with mingw
<Dimenus>
i should back up, I was originally getting linker errors in the zig debug build
<Dimenus>
so I thought it was the clang install I had which was compiled in release mode
<Dimenus>
i would prefer mingw to be honest......
<Dimenus>
i just ran into the issue where the compiler doesn't exist cleanly and I didn't know where to add 'TerminateProcess'
<pupp>
mingw is quite shit, I warn you
<Dimenus>
anyway, I guess I'm just a bit stuck. Do I need to build clang & the associated tools in debug as well?
<andrewrk>
Dimenus, "-DCMAKE_BUILD_TYPE=Release" in the Debug Mode section is not a mistake
<andrewrk>
that's the only way it worked for me, and it did in fact make a debug build
<Dimenus>
duly noted
<dtzWill>
poking at clashos: https://github.com/andrewrk/clashos while giving Nixpkgs-built Zig a try... I don't have a RPI3 on hand, so I'm using the 'zig build qemu' bit.
<dtzWill>
Well lemme first say I'm still /shocked/ that it actually built a freestanding armv7 kernel out-of-the-box and did so quickly
<dtzWill>
didn't need to chase down some codesourcery toolchain at a particular year-quarter version or something ;)
<andrewrk>
dtzWill, finally somebody appreciates how great cross compiling works :)
<dtzWill>
but anyway: Is that "supposed" to work re:running in qemu? I'm getting a blue screen and it outputs "800600" which is curious
<andrewrk>
hm I think there was a regression
<andrewrk>
I mean, what I had working before was a blue screen, and it printed something more coherent
<dtzWill>
okay a quick look through the code suggested that
<andrewrk>
haven't had time to look at that yet, but obviously if I find the regression I'll add a test for it in the compiler
<dtzWill>
interestingly I see it print things like width x height, lol, but never ${width}${height} haha
<andrewrk>
you can actually test it pretty easily with gdb
<andrewrk>
I forget what the command is
<dtzWill>
okay no worries! I am just trying out various things, and "known" regression is NBD compared to the much scarier silently miscompiling in an environment-specific manner lol
<dtzWill>
last time I did I was debugging my LLVM-JIT compiled Linux kernel :D
<dtzWill>
although I "cheated" and pushed LLVM JIT into the hypervisor layer and added hypercalls for it hehe
<andrewrk>
ha
<dtzWill>
while I have you, when printing build errors there seems to be ... spurious newlines proportional to the number of errors? Is that a thing? xD
<dtzWill>
anyway great stuff
<dtzWill>
I still can't believe that this works
<dtzWill>
:D
<andrewrk>
dtzWill, hmm that doesn't sound familair, feel free to make an issue
<andrewrk>
*familiar
<dtzWill>
aye aye
<dtzWill>
is there a linux platform that's "most" supported/tested with?
<dtzWill>
I like to confirm when things are blatantly NixOS-specific before handing things over to upstream xD
<andrewrk>
dtzWill, my main dev platform is nixos
<andrewrk>
the tetris app works out of the box for me if I use zig build, which is nixos-aware
<andrewrk>
zig build being nixos aware is just looking at those env vars
<andrewrk>
we're not going to support all the c flags, but I don't see the harm in supporting -I -L -l
<dtzWill>
hahaha I can't believe it worked
<dtzWill>
okay well this is just magical
<dtzWill>
well /honestly/ if I can just nix-shell (and presumably this means nix-build aka write nix expressions to build things w/zig) like this.... I'm very happy
<dtzWill>
haha
<dtzWill>
and yes your example nix-shell did the trick, alrighty then
<andrewrk>
:)
<andrewrk>
there's still a lot of work to do, but we're off to a good start!
<dtzWill>
understood, and agreed!!
<Dimenus>
clang in debug build takes so long to compile
<Dimenus>
lol
<andrewrk>
Dimenus, yeah I pretty much left it overnight
<andrewrk>
I'm going to have to do it again, too, because I want to test if llvm master branch fixes debug symbols for windows
<Dimenus>
i probably should have done that
<Dimenus>
i grabbed release_50
<Dimenus>
did they close your ticket?
<dtzWill>
j/w, debug builds are significantly more... useful for your debugging experience.. than Release+Asserts?
<dtzWill>
only ask because the latter is much faster O:)
<Dimenus>
well, some open issues straight up crash :p