Justas Masiulis

The problem with C is that AFAIK there are no ways to guarantee compile time computation. I would probably be possible to create something with tons of macros, but 🤷

This doesn't really use any from "runtime". If you don't have C++ includes you can define `LAZY_IMPORTER_NO_CPP_FORWARD` to get rid of the only things I use from there.

I wasn't sure myself so simply installed windows XP on a VM.  Because it works fine on win XP and on latest windows 10 I'd pretty confidently assume...

Yes, for XP there might be some changes needed to be done like remove and adding your own offsetof (which I wouldn't recommend on non MSVC compiler as they use...

the library requires c++14. I'll look into what I can do about those errors, but that might take some time.

I will get it to work on VS 2015 soon which will probably include any c++11 compliant compiler, but I don't think that it is worth for me to port...

VS 2015 should work now. I might make a branch for XP support because as I said that would require rewriting offsetof which other compilers implement as an intrinsic. As...

Sadly c++03 isn't really possible because there is no way to reliably hash strings at compile time. I might be able to work out some errors for VS 2013 which...

As long as they are exported - sure. ntdll has vsprintf, sprintf, memcpy etc

You can use the cached functions if you are ok with putting a variable in data section.