after PR #25 tests do not pass with output

elm.mk$ make
...
./tests.sh
test #15 "ls dummy/build/images/test.jpg" failed:
	program terminated with code 2 instead of 0
test #16 "ls dummy/build/images/test.png" failed:
	program terminated with code 2 instead of 0
2 of 20 examples tests failed in 0.017s.
Makefile:4: recipe for target 'test' failed
make: *** [test] Error 1

It looks like build and build/images are part of the INSTALL_TARGETS. Calling make after make install results in the images being cp'd to build/images/images which breaks the test. The dist is unaffected because it is not part of the INSTALL_TARGETS and images are cp'd directly from the root images folder.

Removing build and build/images from the INSTALL_TARGETS solves the problem.

I am opening a PR, and would love your feedback. Great project by the way.

Goat doesn't show proper output for failed tasks, making it difficult to debug compilation errors.

Other alternatives, like https://facebook.github.io/watchman/, do a better job, but they're tricky to include as they need to be compiled.

Testing would be easier with a Vagrant box, ideally a very lightweight linux distribution like Alpine.

Add a basic task that copies images to the build folder, possibly doing some basic optimisation.

After using this a few times, I always find myself separating the generated Main.elm file into Main.elm, View.elm, State.elm and Types.elm. Should just generate separate files from the start.

This includes:

• Check if current compile flags are still valid
• Update src/Main.elm template
• Update interop.js template
• Check make test to confirm it still works as expected

Currently there's some confusion on the interop layer side of things, particularly around file naming.

The current interop boilerplate is used to boot the app and handle all interop-related code, but this is not clear.

A good change would be to rename interop to app: that way elm.mk generates 2 files:

• a main.js file, from Elm compilation, which is the compiled Elm Main module.
• a app.js file, which boots the Elm app and handles ports.

This way we can also revise the target resolution logic, so that if a file is called app.js is considered a pure js file, while anything else would be considered an Elm target.

Elm is currently available either as a standalone download or as a npm package. It would be interesting to see if it's possible/feasible/reasonable to integrate this with elm.mk.

For production it would be interesting to generate different artifacts:

• Use https://developers.google.com/closure/compiler/ on generated elm files and interop files
• Compress CSS
• Compress HTML (not sure about this)

It would be nice to include elm-format in the dev-tools - even if it's not used to build the project I usually set up my editor to use elm-format on save but i don't want to install it globally.

It would also help beginners to setup their dev environment

Heya, saw this on elm-discuss. I think this project is a great idea! I replaced my simple Makefile with yours, and tried it out. First issue I ran into was that it requires you two have at least one directory of .elm files inside your /src dir. The project I tried it out in is very simple, and all .elm files are directly in the "root" /src dir. Here's some output demonstrating the issue:

$ make
test -s src/Main.elm || echo "$main_elm" > src/Main.elm
make: *** No rule to make target 'src/**/*.elm', needed by 'build/main.js'.  Stop.
$ mkdir src/asdf
$ touch src/asdf/asdf.elm
$ make
test -s src/Main.elm || echo "$main_elm" > src/Main.elm
elm make src/Main.elm --yes --warn --output build/main.js
Success! Compiled 1 modules.                                        
Successfully generated build/main.js
...

This would be a PR, but I don't really know make well enough!

The current version only works on 0.16