@@ -9,32 +9,36 @@ You can find a list of what binaries we'll need to tar up in `index.js`.
99For example:
1010
1111``` javascript
12- var root = " https://github.com/elm-lang/elm-platform/releases/download/" + binVersion + " -exp/elm-platform" ;
12+ var root =
13+ " https://github.com/elm/compiler/releases/download/" +
14+ binVersion +
15+ " /binaries-for-" ;
1316
1417module .exports = binwrap ({
15- binaries: [" elm" , " elm-make " , " elm-repl " , " elm-reactor " , " elm-package " ],
18+ binaries: [" elm" ],
1619 urls: {
17- " darwin-x64" : root + " -macos .tar.gz" ,
18- " win32-x64" : root + " - windows.tar.gz" ,
19- " win32-ia32" : root + " - windows.tar.gz" ,
20- " linux-x64" : root + " - linux-64bit .tar.gz"
20+ " darwin-x64" : root + " mac .tar.gz" ,
21+ " win32-x64" : root + " windows.tar.gz" ,
22+ " win32-ia32" : root + " windows.tar.gz" ,
23+ " linux-x64" : root + " linux.tar.gz"
2124 }
2225});
2326```
2427
2528If this is the end of your ` index.js ` , you'll need to create these files:
2629
27- 1 . ` elm-platform-macos .tar.gz`
28- 2 . ` elm-platform -windows.tar.gz`
29- 3 . ` elm-platform -linux-64bit .tar.gz`
30+ 1 . ` binaries-for-mac .tar.gz`
31+ 2 . ` binaries-for -windows.tar.gz`
32+ 3 . ` binaries-for -linux.tar.gz`
3033
31- Each of these tarballs should have ** only binaries** inside them - no directories!
34+ Each of these tarballs should have ** only the Elm binary** inside them - no
35+ directories!
3236
3337So create them by making a directory, putting all the binaries in it, ` cd ` -ing
3438into that directory, and then running something like this:
3539
3640``` shell
37- $ tar cvzf elm-platform -linux-64bit .tar.gz *
41+ $ tar cvzf binaries-for -linux.tar.gz elm
3842```
3943
4044Make sure each tarball contains all the binaries listed in that ` binaries: ` list
0 commit comments