Addition of a build system generator

[elfring]

I suggest to reuse a higher level build system than your current small make file so that powerful checks for software features will become easier.

• CMake
• Autotools

[trufae]

both are crap imho

its just 2 C files and it doesn’t really compensates shipping 1MB of scripts to build this

On 26 Apr 2016, at 18:03, Markus Elfring notifications@github.com wrote:

I suggest to reuse a higher level build system than your current small make file https://github.com/nowsecure/fsmon/blob/6a56b1b72fc55712a363c953ef1916b49c72ceee/Makefile#L1 so that powerful checks for software features will become easier.

CMake https://cmake.org/ Autotools http://www.gnu.org/software/autoconf/#TOCintroduction — You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/nowsecure/fsmon/issues/18

[elfring]

• Does a tool like "autoscan" show any software dependencies that you find worth for further considerations?
• How do you think about to support more development environments by the reuse of build system generators?

[trufae]

there are no software dependencies in fsmon. only target ones. none of those tools is able to detecti if you have an NDK installed or if the target kernel supports fanotify.

adding supoport for other build systems is also useless, because make is available everywhere, even on windows, and this tool only works on unix systems for now. so it doesn't solves any problem.

15 years ago i wrote ACR, and that's the sofware i use instead of autoconf, which is much smaller, equally portable, compatible at script level and easier to maintain. and that's what i use in most of my projects when they really need this.

A single makefile is much better option for 99% of projects and 100% if the target is that simple