Differences between SCons and Shake

I am working on a Python / Haskell project and I am looking for alternatives Makefile. The obvious choices are Python SCons and Haskell Shake . Since I have no experience with any of them, I would like to ask if there is a comparison of their disadvantages and advantages.

Update: The project has several complex construction requirements:

  • Allow the user to configure the built-in parameters for on / off, toolpaths, etc.
  • At compile time, Haskell and Python files are created. Their dependencies should work properly.
  • There are several Haskell programs that share most of the source files. I would like to:
    • it is possible to build each separately, and not create sources that are not needed;
    • source files are not created several times when compiling several programs;
    • until it reaches parallelism at compile time, if possible.
  • Check for multiple programs installed on the target systems and their ways (eg python, flocketc.)
  • Check dependencies on target systems like Python, Haskell.
  • Parameterize the assembly depending on the dependencies - if there are no dependencies for testing, you can still build the project by skipping the tests (and informing the user about this).
+4
source share
2 answers

Why Shake? , Shake , SCons.

: Shake ( StackOverflow, ). Shake vs SCons:

+4

- SCons, , , Haskell/Shake.

, .

SCons ( make cmake) Python , .

+3

Source: https://habr.com/ru/post/1530017/


All Articles