Confusing compile instructions for linux

[JanHolger]

Please add compilation instructions to the linux section in the README like you did for OS X. The repo contains a CMakeLists which made me use cmake. Unfortunately this way you will run into missing .hdll files so it might be a good idea to advise people to compile the given Makefile instead of using cmake. This problem just took me almost an hour to solve and i found the solution on some weird site.

[zaxebo1]

can you please elaborate the problem you encountered, and the solution link to the wierd site

[JanHolger]

Like i said the existing cmake file made me run cmake intuitively, but building with the cmake config instead of the already existing Makefile will end up in missing hdll files when trying to build stuff (the heaps hello world in my case). In the README you have concrete build intructions for OS X:

Once dependencies are installed you can simply call:

make

To be able to use hashlink binary with the debugger you can then call:

sudo make codesign_osx

To install hashlink binaries on your system you can then call:

make install

but only a dependency list for Linux.

My suggestion is just to add those to the linux section aswell so people don't get confused with that cmake config (for whatever reason it is there). I don't have the link to the website which gave me the tip anymore, but the author was also confused by the cmake config so i thought it might be a good idea to open an issue for that.