Question regarding unistd.h

[IngwiePhoenix]

Hello!

I have been sneaking around the i2p project for a while, curiously looking at it in contrast to TOR and other overlay network technologies. Now, after some time, I wanted to look at how I could use i2p myself, and came to libsam. But the first thing I noticed is that you must use MinGW to build for Windows - and I can see why. A lot of POSIX specific APIs are used.

Why, though? The one that sticks out the most to me would be unistd.h. But aside from that, what else really "hinders" a native Win32 build?

I mainly want to use libsam3 with the V language, which uses TCC by default but MSVC or GCC depending on platform and situation (or choice). So having a way to build "natively" would be really useful.

Thank you in advance and kind regards,
Ingwie

[eyedeekay]

Hypothetically nothing except my experience with Windows API's unfortunately. I'd be quite happy to accept a PR which attempts a more universal approach but for now unistd.h and mingw are used precisely because I'm not yet familiar with a better option. I've seen V before, it looks like a cool language. Another option might be implementing a SAM library in pure V, which would not be difficult at all if you're interested in trying it out. I'd be happy to help you get started if you want to go that route.