KSo while fixing CI I've now found out that OSX isn't (and has never) worked
K@Perksey iirc you have at least a tiny amount of OSX experience. Any clue why OSX clang would not know standard libraries? Can't really find anything online...
Pstandard libraries?
Kstdint.h
Pyou mean like stdlib.h, st… ah
Pso that’s actually the case for windows too
Pand is one of the reasons why the vsresolver logic is vital
Kbut it works on windows 
Pyeah the vsresolver resolves the include path
Pfor the MSVC CRT
KI've left in the VSResolver code, but it's unused right now
Pwhat
Pok
Pthat’s very strange
Pthat never used to work
Kpretty sure clang just identifier int32_t as a primitive on non-osx
KI'm sure it breaks for other stdint.h stuff
Pint32_t can’t be a primitive though
KI thought we talked about that earlier, when I asked about what the inner text ment?
KI'm not sure, just recalling from that
PGet type name is recursive
Pso it’ll resolve the typedef and step through it to find something like “int”
Kah I see
Pwhich resolves to C# “int”
Kand It's just unclear why tf it manages to do that on windows without vsresolver logic
PIt never used to but then again I have all my shit installed in non-standard locations
Kso what's the way to do this on platforms? Windows include vsresolver folder, linux do nothing (?), osx?
PLinux do nothing because it’s a Linux convention that it’s always /usr/include iirc
PI’ll have a poke around on my Mac rq
Kso apparently there's -nostdinc and -noibuiltininc which should tell clang to not include standard libraries
Kmaybe the default is different?
Pho ho ho
Pthis is cursed
Knot surprised lmao
Pgimme a sec as I wait for discord to update on a Mac with a spinner in it
Kyou think this is an easy fix or do I get ready for bed? (And use cursed osx as bedtime story lmao)
Pyou will need to write some amount of code so yeah I’d get into bed. It’s not too hard to resolve the correct path luckily, but still probably something that can wait.
POh good discord has finally loaded
Pso
Pthe headers live in
Pare you ready
Pdrum roll please
P/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/
KOh wtf
Pluckily, you can get that path in an agnostic way by doing
xcrun --show-sdk-pathPthat gets you
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdkPand from there you can add the
/usr/includePand much like the VS resolver stuff add that into the include paths
KOK... That's kinda awkward but I guess not worse then VS resolver...
Pgod the VS resolver is much worse yeah
