NEW Basic escriptize support

[quiquepaz]

• make escriptize
• ./smother
• Compiling code with 'TEST' macro for easier integration with rebarized projects
• preprocess option currently unsupported in escript (couldn't make it work)
• smother escript would benefit from cleaner file management in smother: compiled code been dropped at /tmp, no option to generate reports in a specific location, etc

[quiquepaz]

@ramsay-t Is this of any interest for you? Should I mail you to discuss the approach?

[ramsay-t]

Its certainly interesting! I haven't seen ascriptive before (but then I'm pretty new to rebar...) but something that would allow me to form a catch process to smother compile -> run tests -> generate output in sensible ways would be great.

I'm currently in the middle of a fairly drastic overhaul of the way Smother generates reports, since it was a pretty dodgy hack in the prototype.

Let me know if Smother is useful to you; its still part of an EU funded research project, so feedback is really valuable!

[quiquepaz]

Smother is definitely nice, and I'm happy to hear about the report generation being reworked. So that's your positive feedback. On the negative side, I haven't been able to make it work with the preprocess option (although I haven't look deeply into it).

In short, this PR provides you with 2 things:

• The TEST macro being defined when smother compiling. This is key for projects using stuff like

-ifdef(TEST).
-export([...]).
-endif.

... for testing unexported functions, since the TEST macro is automatically defined when you use rebar eunit.

• make escriptize now generates a self contained ./smother script you can use from the shell in any machine of the same architecture to get coverage reports for projects without any Erlang knowledge needed (great for QA specialists)