mal/impls/scala/Makefile

SOURCES_BASE = types.scala reader.scala printer.scala
SOURCES_LISP = env.scala core.scala stepA_mal.scala
SOURCES = $(SOURCES_BASE) $(SOURCES_LISP)

TARGET_DIR=target/scala-2.11

all: $(TARGET_DIR)/mal.jar

dist: mal

mal: $(TARGET_DIR)/mal.jar
	cp $< $@

$(TARGET_DIR)/mal.jar:
	sbt assembly

$(TARGET_DIR)/classes/step%.class: step%.scala $(SOURCES)
	sbt assembly

clean:
	rm -rf mal target

.PHONY: all dist clean
Scala: refactor collections with metadata. Convert numeric to Long. Add time-ms. Add Makefile for stats targets. 2014-12-19 08:52:59 +03:00			`SOURCES_BASE = types.scala reader.scala printer.scala`
All: rename stepA_interop to stepA_mal Also, add missed postscript interop tests. 2015-02-28 20:09:54 +03:00			`SOURCES_LISP = env.scala core.scala stepA_mal.scala`
Scala: refactor collections with metadata. Convert numeric to Long. Add time-ms. Add Makefile for stats targets. 2014-12-19 08:52:59 +03:00			`SOURCES = $(SOURCES_BASE) $(SOURCES_LISP)`

scala: Run steps directly from jar file The Scala build will create a mal.jar file with all the steps' classes in it. A `run` wrapper script will run that jar with a specific step main class according to the `$STEP` environment variable. Now the jar file is created only once (when testing step0) and then re-used for testing the next steps, which should speed up the build. Moreover, sbt now prepends shell script header to the jar file, so no need to implement this in Makefile (for the `dist` target). 2016-05-16 18:25:42 +03:00			`TARGET_DIR=target/scala-2.11`
Add dist targets to most implementations. TODO: factor groovy guile julia matlab miniMAL swift 2016-02-18 09:33:19 +03:00
scala: Run steps directly from jar file The Scala build will create a mal.jar file with all the steps' classes in it. A `run` wrapper script will run that jar with a specific step main class according to the `$STEP` environment variable. Now the jar file is created only once (when testing step0) and then re-used for testing the next steps, which should speed up the build. Moreover, sbt now prepends shell script header to the jar file, so no need to implement this in Makefile (for the `dist` target). 2016-05-16 18:25:42 +03:00			`all: $(TARGET_DIR)/mal.jar`
Scala: refactor collections with metadata. Convert numeric to Long. Add time-ms. Add Makefile for stats targets. 2014-12-19 08:52:59 +03:00
scala: Run steps directly from jar file The Scala build will create a mal.jar file with all the steps' classes in it. A `run` wrapper script will run that jar with a specific step main class according to the `$STEP` environment variable. Now the jar file is created only once (when testing step0) and then re-used for testing the next steps, which should speed up the build. Moreover, sbt now prepends shell script header to the jar file, so no need to implement this in Makefile (for the `dist` target). 2016-05-16 18:25:42 +03:00			`dist: mal`
Add dist targets to most implementations. TODO: factor groovy guile julia matlab miniMAL swift 2016-02-18 09:33:19 +03:00
scala: Run steps directly from jar file The Scala build will create a mal.jar file with all the steps' classes in it. A `run` wrapper script will run that jar with a specific step main class according to the `$STEP` environment variable. Now the jar file is created only once (when testing step0) and then re-used for testing the next steps, which should speed up the build. Moreover, sbt now prepends shell script header to the jar file, so no need to implement this in Makefile (for the `dist` target). 2016-05-16 18:25:42 +03:00			`mal: $(TARGET_DIR)/mal.jar`
			`cp $< $@`
Add dist targets to most implementations. TODO: factor groovy guile julia matlab miniMAL swift 2016-02-18 09:33:19 +03:00
scala: Run steps directly from jar file The Scala build will create a mal.jar file with all the steps' classes in it. A `run` wrapper script will run that jar with a specific step main class according to the `$STEP` environment variable. Now the jar file is created only once (when testing step0) and then re-used for testing the next steps, which should speed up the build. Moreover, sbt now prepends shell script header to the jar file, so no need to implement this in Makefile (for the `dist` target). 2016-05-16 18:25:42 +03:00			`$(TARGET_DIR)/mal.jar:`
			`sbt assembly`
Dist/packaging for most impls. erlang, racket ARGV fixes. Also in this commit: - fix ARGV setup in erlang and racket. - print startup message in fsharp Dist/packaging support for most implementations and also generate a /mal standalone app for most languages. The following implementations still have ability to generate a single /mal standalone application: - guile - julia - matlab (mkoctfile doesn't actually package up source files) - swift - vb (mkbundle error) Also, the following are mostly packaged into a single file but need some module dependencies - coffee: requires node_modules/ffi - es6: requires node_modules/ffi - js: requires node_modules/ffi - lua: module 'readline' not found - miniMAL: cannot find module '/mal/node_readline.js' - r: needs lib directory 2016-02-24 09:45:40 +03:00
scala: Run steps directly from jar file The Scala build will create a mal.jar file with all the steps' classes in it. A `run` wrapper script will run that jar with a specific step main class according to the `$STEP` environment variable. Now the jar file is created only once (when testing step0) and then re-used for testing the next steps, which should speed up the build. Moreover, sbt now prepends shell script header to the jar file, so no need to implement this in Makefile (for the `dist` target). 2016-05-16 18:25:42 +03:00			`$(TARGET_DIR)/classes/step%.class: step%.scala $(SOURCES)`
			`sbt assembly`
Dist/packaging for most impls. erlang, racket ARGV fixes. Also in this commit: - fix ARGV setup in erlang and racket. - print startup message in fsharp Dist/packaging support for most implementations and also generate a /mal standalone app for most languages. The following implementations still have ability to generate a single /mal standalone application: - guile - julia - matlab (mkoctfile doesn't actually package up source files) - swift - vb (mkbundle error) Also, the following are mostly packaged into a single file but need some module dependencies - coffee: requires node_modules/ffi - es6: requires node_modules/ffi - js: requires node_modules/ffi - lua: module 'readline' not found - miniMAL: cannot find module '/mal/node_readline.js' - r: needs lib directory 2016-02-24 09:45:40 +03:00
Add dist targets to most implementations. TODO: factor groovy guile julia matlab miniMAL swift 2016-02-18 09:33:19 +03:00			`clean:`
scala: Run steps directly from jar file The Scala build will create a mal.jar file with all the steps' classes in it. A `run` wrapper script will run that jar with a specific step main class according to the `$STEP` environment variable. Now the jar file is created only once (when testing step0) and then re-used for testing the next steps, which should speed up the build. Moreover, sbt now prepends shell script header to the jar file, so no need to implement this in Makefile (for the `dist` target). 2016-05-16 18:25:42 +03:00			`rm -rf mal target`
Add dist targets to most implementations. TODO: factor groovy guile julia matlab miniMAL swift 2016-02-18 09:33:19 +03:00
Convert to loccount based stats calculation. 2019-03-21 07:32:35 +03:00			`.PHONY: all dist clean`