09:05 <kristate_> @andrewrk Any documentation for cross compiling? Going to look at the compiler flags.

09:56 <tiehuis> kristate_: nothing specific, just look at `zig targets` to see the applicable host-os-environ triples and the corresponding `--target-` compiler flags

09:56 <kristate> tiehuis: thanks!

09:57 <kristate> working on https://github.com/ziglang/zig/issues/1271

09:57 <tiehuis> remember there are only os abstractions for windows/linux/macos x86_64 at this time as well, so something more obscure you will want to use freestanding

09:57 <tiehuis> you can still use the stdlib mostly of course! just not the std.os stuff for the most part

09:58 <kristate> tiehuis: yes :-)

10:00 <tiehuis> regarding os posix support i usually find it best to just build up the minimal set of functionality at a time and get that tested before continuing

10:01 <tiehuis> also in regards to freebsd, i have a semi-active branch with support for that here: https://github.com/ziglang/zig/tree/freebsd

10:01 <kristate> tiehuis: okay, cool -- networking is so underworked at the moment

10:02 <tiehuis> yeah, on the current main platforms with os support there is still plenty of work to be done there

10:17 <GitHub68> [zig] kristate opened pull request #1272: More Socket Defines for Darwin (master...posix-darwin-issue1271) https://git.io/fNWzr

11:38 <GitHub67> [zig] tiehuis opened pull request #1273: Tighten Int.to bounds and add twos-complement bitcount (master...bigint-twos-comp) https://git.io/fNW2K

17:23 <GitHub106> [zig] kristate opened pull request #1275: Skippable tests issue1274 (master...skippable-tests-issue1274) https://git.io/fNWMR

17:43 <Sahnvour> hi andrewrk , I'm back again about the windows error traces. I doubt I'll finish the implementation in a short amount of time since this is proving to be not so trivial, so I figured i'd be better off to share my work now in case anyone can help on this

17:43 <Sahnvour> what do you advise; keeping a branch on my fork, PR'ing it to the official repo, ... ?

17:44 <kristate_> Sahnvour: where is your fork ?

17:44 <Sahnvour> https://github.com/Sahnvour/zig nothing to see at the moment

17:45 <kristate_> I would put it into a branch and PR it to the main repo for review

17:46 <kristate_> Sahnvour: branches usually have -issue#### where #### is the issue number

17:46 <kristate_> Sahnvour: if you don't have an issue assigned, please assign one in the tracker

17:46 <Sahnvour> okay (there is one)

17:47 <kristate_> Sahnvour: https://github.com/ziglang/zig/issues/721 ??

17:48 <Sahnvour> correct

17:48 <kristate_> Cool, looking forward to seeing what you got

17:48 <kristate_> you could call the branch windows-coff-issue721

17:49 <Sahnvour> very rough at the moment, I still haven't really figured out how to map address to source line, but can already sort of browse the pdb file

17:50 <kristate_> Also, place [WIP] before the title so we know to review it

17:52 <Sahnvour> are you ok with having debug output in the implementation or do you want me to clean it up ? (probably still very useful to continue development)

18:00 <kristate_> Sahnvour: debug is fine for now, as it is a WIP

18:01 <Sahnvour> cool, I'll do that then, thanks

18:01 <kristate_> Sahnvour: Thank-you!

18:51 <Sahnvour> is it OK to target master with a wip branch ?

22:01 <GitHub69> [zig] Sahnvour opened pull request #1276: [WIP] Windows coff issue721 (master...windows-coff-issue721) https://git.io/fNWF9