Can you change the Emakefile to have your target first in the tuple?
I have not worked with ASN1, but from what I know of Emakefiles the first entry in the tuple should be the target (module). According to the compile documentation ASN1 files are the source for targets, not targets.
> Can you change the Emakefile to have your target first in the tuple?
> I have not worked with ASN1, but from what I know of Emakefiles the > first entry in the tuple should be the target (module). According to the > compile documentation ASN1 files are the source for targets, not > targets.
Now my Emakefile is:
{"SSWConn", [{outdir, "."}]}.
There is SSWConn.asn file in directory. "erl -make" prints:
$ erl -make Recompile: SSWConn ./SSWConn.erl:none: no such file or directory
BTW, for .erl files my Emakefile is: {"src/*", [debug_info, {i, "../asn"}, {warn_format, 1}, {outdir, "ebin"}]}.
> Can you change the Emakefile to have your target first in the tuple?
> I have not worked with ASN1, but from what I know of Emakefiles the > first entry in the tuple should be the target (module). According > to the > compile documentation ASN1 files are the source for targets, not > targets.
> Now my Emakefile is:
> {"SSWConn", [{outdir, "."}]}.
> There is SSWConn.asn file in directory. "erl -make" prints:
> $ erl -make > Recompile: SSWConn > ./SSWConn.erl:none: no such file or directory
> BTW, for .erl files my Emakefile is: > {"src/*", [debug_info, {i, "../asn"}, {warn_format, 1}, {outdir, > "ebin"}]}.
There is expand/2 in make.erl, which handles only .erl files. I can make patch for handling .asn files too, but I don't know, which behaviour must be used here without conflicts with previous case.