Ole-Jeger Hoffstuen

That may well be, but it actually seemed to import without any issues the moment I just pasted the folder in the right place on my filesystem.

Hi, thanks for the quick reply. Although it seems that I could have been clearer in the original post. As for my question being too broad, I can see how...

It is not the compiler that needs to be influenced but rather the build systems. If a build system checks whether the compiler it has been configured to use can...

Yes, but this should require no additional abstractions over the compiler. That seems like the wrong way to solve this. If I want to compile my stuff with some obscure...

Ok, it seems like we want to address different issues here. The issue you are describing is that the build system doesn't listen to the conventional environment flags. I have...

I'm working on a minimum project to show what I mean more closely as I am generally terrible at explaining stuff.

I do feel like this is somewhat besides the question, but that is a good point. Although I suspect that there would be more complications with this approach due to...

So just to be sure I just tried with Cygwin as well. No luck. After installing winpthread for either environment and modifying `LIBRARY_PATH` before running `build.sh` so that winpthread could...

Where in the documentation does it say that? the only reference I can find to anything windows specific is a sentence that states you only support building with Cygwin. Nonetheless,...

The `I2C_M_NOSTART` flag does fix the issue, but it assumes that the i2c device supports it. This can be checked using the `I2C_FUNCS` operation of `ioctl`. One potential issue with...