Originally at 2011-07-07T08:05:37Z by Göran Krampe closed at 2011-07-09T16:06:36Z (pull request)
Hi Nicolas!
Ok, last night I finally dug through this. The "hard part" was getting Kernel.st compiled twice - once for deployment and once for debug mode. Anyway, now it produces a deploy-Kernel.js file that is only used to produce jtalk.deploy.js.
So... run "make clean && make" in the st directory. If all js files produced (in that dir) looks fine you can always do "make install" but as you see that merely copies them over to the js dir :)
Note file sizes - and oh, forgot - you need to download the Google Closure compiler and put the jar in your home directory.
cheers, Göran
Originally at 2011-07-07T08:05:37Z by Göran Krampe closed at 2011-07-09T16:06:36Z (pull request)
Hi Nicolas!
Ok, last night I finally dug through this. The "hard part" was getting Kernel.st compiled twice - once for deployment and once for debug mode. Anyway, now it produces a deploy-Kernel.js file that is only used to produce jtalk.deploy.js.
So... run "make clean && make" in the st directory. If all js files produced (in that dir) looks fine you can always do "make install" but as you see that merely copies them over to the js dir :)
Note file sizes - and oh, forgot - you need to download the Google Closure compiler and put the jar in your home directory.
cheers, Göran
Originally at 2011-07-07T08:05:37Z by Göran Krampe closed at 2011-07-09T16:06:36Z (pull request)
Hi Nicolas!
Ok, last night I finally dug through this. The "hard part" was getting Kernel.st compiled twice - once for deployment and once for debug mode. Anyway, now it produces a deploy-Kernel.js file that is only used to produce jtalk.deploy.js.
So... run "make clean && make" in the st directory. If all js files produced (in that dir) looks fine you can always do "make install" but as you see that merely copies them over to the js dir :)
Note file sizes - and oh, forgot - you need to download the Google Closure compiler and put the jar in your home directory.
cheers, Göran