[erlang-questions] Auto recompilation

Matthew Williamson <>
Wed Aug 13 16:56:43 CEST 2008

If you want all you're beam files in the ebin directory, run `erlc
mymodule.erl -o ebin`. Try out my makefile. I think you'll like it.


# Compile bytecode
    erlc -I include -pa $(BIN) -o $(BIN) -v $(SRCS)
# Compile documentation
    erl -noshell -eval 'edoc:files(filelib:wildcard("src/*.erl"), [{dir,
"doc"}]).' -s init stop

    rm -f $(BIN)/*

On Wed, Aug 13, 2008 at 8:50 AM, Matthew Williamson <>wrote:

> Really I just mean calling erlc on all the files. See erlc(1) (`man erlc`).
> Even a bash script would suffice.
> 2008/8/13 Hynek Vychodil <>
>> No, I don't mean using it in production system. But anyway automate
>> stop/compile/deploy/start cycle is better way than solve it by auto
>> recompile. It should be controllable. When it is controllable, you can
>> transform stop/compile/deploy/start cycle to compile/upgrade without stop
>> cycle as erlang provide by hot code swap in controlled manner. Do it every
>> time when I press :w or C-x C-s or auto-save is invoked is weird. It should
>> be invoked by pressing another button.
>> On Wed, Aug 13, 2008 at 11:08 AM, Paul Guyot <> wrote:
>>> Le 13 août 08 à 10:56, Hynek Vychodil a écrit :
>>>  I cooked another one for myself (a little shorter than yours) but than I
>>>> decide it is wrong idea. Auto recompilation is good toy but
>>>> contraindication
>>>> to reliability.
>>> Do you mean using auto recompilation in production systems? There seems
>>> to be a misunderstanding here, as I'm mentioning auto-recompilation as a
>>> development tool, i.e. as a way to avoid stop/compile/deploy/start cycles
>>> during development.
>>> Paul
>> --
>> --Hynek (Pichi) Vychodil
>> _______________________________________________
>> erlang-questions mailing list
>> http://www.erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20080813/8c2fa771/attachment.html>

More information about the erlang-questions mailing list