[erlang-questions] escript lives
Bengt Kleberg
bengt.kleberg@REDACTED
Tue Oct 17 09:30:47 CEST 2006
On 2006-10-16 23:42, Wayne Vucenic wrote:
...deleted
> moving over Joe's .tgz file and unzipping it on OS X. This
> fixes the problem I was seeing with mk_escript.sh. I'm not
good.
...deleted
> changed Makefile to
> all:
> echo ${BEAM_FILES}
> as you suggested:
>
> Mini:~/erlang/escript-4.0 wayne$ make
> echo escript.beam .beam
> escript.beam .beam
>
> well, that explains what we're seeing. It correctly makes
> escript.beam, then fails to make .beam
i did not expect make to get escript.beam right, so there i was wrong.
but i did get the error location right. yay me :-)
...deleted
> One fix would be to change the first 3 lines in the Makefile from
>
> MODS = escript
> ERL_FILES = $(MODS:=.erl)
> BEAM_FILES = $(MODS:=.beam)
>
> to
>
> ERL_FILES = escript.erl
> BEAM_FILES = escript.beam
>
> With this one change it all builds correctly.
i think your solution is the right one for escripts makefile.
generally speaking, using make is a problem. this is just a minor
nuisance, for the real problems see (among others)
http://aegis.sourceforge.net/auug97.pdf
bengt
--
EPO guidelines 1978: "If the contribution to the known art resides
solely in a computer program then the subject matter is not
patentable in whatever manner it may be presented in the claims."
More information about the erlang-questions
mailing list