Created
March 25, 2014 17:09
-
-
Save copenhas/9766498 to your computer and use it in GitHub Desktop.
Playing around with Tup
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| { | |
| "name": "tup-demo", | |
| "version": "0.0.0", | |
| "description": "Playing around with using Tup as a build system", | |
| "dependencies": {}, | |
| "devDependencies": { | |
| "coffee-script": "~1.7.1", | |
| "istanbul": "~0.2.6", | |
| "urequire": "~0.6.13-1" | |
| }, | |
| "scripts": {}, | |
| "author": "[email protected]", | |
| "license": "MIT" | |
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| : foreach app/*.coffee |> ./node_modules/coffee-script/bin/coffee -c -o _build/coffee/ %f |> _build/coffee/%B.js | |
| : foreach _build/coffee/*.coffee |> ./node_modules/istanbul/lib/cli.js --output _build/instrumented/ %f |> _build/instrumented/%B.js |
OK, after reading through the docs a little more and studying this example I think I get the mechanics of it now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Basically I was trying to install everything local to the project, using Tup to incrementally process the files, and keep all the files around so that Tup could quickly recompute any build outputs.
I'm not sure how
cleantasks or other such task automation would work in Tup. That might be where doing all of this behind a basic Makefile might be good.