Packaging of sources should be done always
(details / githubweb)
Making WIN32_LEAN_AND_MEAN a compilation option, this should only affect the speed of the build process. Check https://docs.microsoft.com/en-us/windows/win32/winprog/using-the-windows-headers
(details / githubweb)
Fixing the camel case names of the parameters
(details / githubweb)
Copying version file to the generated, so the package can work
(details / githubweb)
Copying version file to the generated, so the package can work
(details / githubweb)
In Windows, the fopen assumes the characters are encoded in ANSI. If not, we need to use the wide version of it.
(details / githubweb)
Packaging of sources should be done always
(details / githubweb)
Making WIN32_LEAN_AND_MEAN a compilation option, this should only affect the speed of the build process. Check https://docs.microsoft.com/en-us/windows/win32/winprog/using-the-windows-headers
(details / githubweb)
Fixing the camel case names of the parameters
(details / githubweb)
Copying version file to the generated, so the package can work
(details / githubweb)
Copying version file to the generated, so the package can work
(details / githubweb)
In Windows, the fopen assumes the characters are encoded in ANSI. If not, we need to use the wide version of it.
(details / githubweb)
Packaging of sources should be done always
(details / githubweb)
Making WIN32_LEAN_AND_MEAN a compilation option, this should only affect the speed of the build process. Check https://docs.microsoft.com/en-us/windows/win32/winprog/using-the-windows-headers
(details / githubweb)
Fixing the camel case names of the parameters
(details / githubweb)
Copying version file to the generated, so the package can work
(details / githubweb)
Copying version file to the generated, so the package can work
(details / githubweb)
In Windows, the fopen assumes the characters are encoded in ANSI. If not, we need to use the wide version of it.
(details / githubweb)