Christian Helmich

oh, that's fine. I meant to say that `Release` gets changed to `ReleaseFast` when writing the zig file. nothing really hard.

Interestingly, `os.get() / os.is()` depend on the `--os` option if provided. ``` function os.get() return _OPTIONS.os or _OS end function os.is(id) return (os.get():lower() == id:lower()) end ``` IMHO, it's safe...

Also, if we do it with an API field ``` configuration {"windows"} namestyle "windows" configuration {} ``` we can leave the configuration and its assumptions to the user.

I see. It's my first time using a different toolchain than MSVC on Windows (namely clang + ninja), and obviously I'm running into all those small issues.

So far for today. Please don't merge this yet, I still need to test with other IDEs. (especially ce8f9c9 might have unwanted side effects) . What do you think of...

E.g. from my current build ``` ==== Building cgltf (debug) ==== Archiving cgltf ar: no archive members specified usage: ar -d [-TLsv] archive file ... ar -m [-TLsv] archive file...

And from being added as link dependency to other projects, yes. I still think making it explicit through the project type is more elegant, but I got your point about...

You mean, generating a `.c`, respectively `.cpp` file, containing a simple ```static void libname_dummy(){}``` ? Sounds feasible. I'll start adding this to gmake and ninja to see how it works...

@bkaradzic My PR #491 seems like an easily feasible approach? What do you think? I still have to verify I didn't break anything with VS and other generators I haven't...

Addendum: some IDEs (VS, Xcode) actually allow to have static/dynamic libs among the project files, and even link them correctly. The proposed change is kind of riding on this idea,...