You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current Makefile only functions as intended on Linux, but not Windows. Here is a description of problems and potential solutions.
Valgrind is not supported on Windows. Since PRs require absence of memory leaks with $ make test, finding an alternative command line memory profiler is necessary and should be conditionally applied to Windows builds.
The absence of the .exe file extensions on generated executables results in failure of automated runs, also present on $ make test. This could likely be solved with a simple macro. EXT := .exe or something similar.
The default compiler for $(CC) chosen when building on Windows is cc, which is not ideal. I would prefer MSVC be used, or at the very least mingw. I'm not really sure how to handle this one to be completely honest.
The current
Makefile
only functions as intended on Linux, but not Windows. Here is a description of problems and potential solutions.$ make test
, finding an alternative command line memory profiler is necessary and should be conditionally applied to Windows builds..exe
file extensions on generated executables results in failure of automated runs, also present on$ make test
. This could likely be solved with a simple macro.EXT := .exe
or something similar.$(CC)
chosen when building on Windows iscc
, which is not ideal. I would preferMSVC
be used, or at the very leastmingw
. I'm not really sure how to handle this one to be completely honest.I tested this using
make
installed through the chocolatey package manager for windows.The text was updated successfully, but these errors were encountered: