FLIF

FLIF copied to clipboard

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

I completely agree.

CMake :+1:

I would strongly discourage autotools. I do not want to start a flame war, but its negatives almost always outweigh the positives.

CMake is a far better choice, but a simple make file is often really not a problem. Something like tup or waf may also be a great alternative.

What is wrong with autotools?

• 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?

Just tested the current git master branch version with CMake on Fedora 23. Mostly seems ok, with the exception of viewflif which doesn't seem to have a target for it yet.

I tried integrating viewflif into the CMake build, but since CMake doesn't really support SDL2, it gets ugly (at least on the Windows side).