The project you linked is using
CMake instead of a regular
GNU/Make makefile.
That's cool. Some projects don't even include makefiles. If you're familiar with the command line, these steps should be enough:
- cd to the root of the repository. (To get it off github, git clone https://github.com/FGRE/nptools, then navigate to nptools/)
- Use mkdir to create a build directory. (mkdir build)
- cd to build.
- Run cmake .. to get CMake to read CMakeLists.txt files and handle the rest of the compilation process.
Install CMake and have its process in your PATH environment variable. If you don't want to have it there permanently, run
set PATH=%PATH%;C:\Path\To\CMake in the command prompt instance you're running.
I have never used CMake, so I can't help you with troubleshooting, in case you do encounter problems. Keep in mind GNU/Make and CMake are not compiler alternatives(don't quote me on that for CMake), but rather tools to assist the compilation process. Makefiles are there to simplify life, compiling is done purely by running
make filename, where filename follows a recipe.
I'd advise you to read tutorials on how to use CMake.
For some reason, the CODE tags aren't working...
EDIT: Just realized you wanted someone to compile it for you. I'd do it, but I really can't be bothered to install CMake and use it just for that. You should use the opportunity to get familiar with CMake and other build utilities, like GNU/Make. On Windows, I used
MinGW's mingw32-make, since I had been using it for gcc(GNU C Compiler), from GCC(GNU Compiler Collection, heh).
You can install GCC through mingw-get, which you install in order to install MinGW's packages, upon its own installation. Be sure to mark g++(GNU C++ Compiler) for instalation, if you want to compile C++ projects(like the one you linked).
Again, I never used CMake. Sorry, pal. Pressure the developers to include a binary release with the GitHub releases, maybe they'll do it.