@@ -27,7 +27,7 @@ cd hUGETracker |
| 27 |
lazbuild --add-package-link rackctls/RackCtlsPkg.lpk |
27 |
lazbuild --add-package-link rackctls/RackCtlsPkg.lpk |
| 28 |
lazbuild --add-package-link bgrabitmap/bgrabitmap/bgrabitmappack.lpk |
28 |
lazbuild --add-package-link bgrabitmap/bgrabitmap/bgrabitmappack.lpk |
| 29 |
|
29 |
|
| 30 |
:: At this point if you want to develop HT, then open GBEmu.lpi in Lazarus, make sure you're in the |
30 |
:: At this point if you want to develop HT, then open hUGETracker.lpi in Lazarus, make sure you're in the |
| 31 |
:: Development build mode, and everything should build correctly. However, in order to allow for concurrent |
31 |
:: Development build mode, and everything should build correctly. However, in order to allow for concurrent |
| 32 |
:: development on the tracker (this repo) and the sound driver (https://github.com/SuperDisk/hUGEDriver), |
32 |
:: development on the tracker (this repo) and the sound driver (https://github.com/SuperDisk/hUGEDriver), |
| 33 |
:: the hUGEDriver folder is not copied to the output directory, and you're expected to symlink it there yourself; |
33 |
:: the hUGEDriver folder is not copied to the output directory, and you're expected to symlink it there yourself; |
@@ -38,9 +38,9 @@ ln -s hUGEDriver lib/Development/x86_64-linux/hUGEDriver |
| 38 |
|
38 |
|
| 39 |
:: If you just want to build a release for whatever platform you have, pick one of the following: |
39 |
:: If you just want to build a release for whatever platform you have, pick one of the following: |
| 40 |
|
40 |
|
| 41 |
lazbuild GBEmu.lpi --build-mode="Production Windows" |
41 |
lazbuild hUGETracker.lpi --build-mode="Production Windows" |
| 42 |
lazbuild GBEmu.lpi --build-mode="Production Mac" |
42 |
lazbuild hUGETracker.lpi --build-mode="Production Mac" |
| 43 |
lazbuild GBEmu.lpi --build-mode="Production Linux" |
43 |
lazbuild hUGETracker.lpi --build-mode="Production Linux" |
| 44 |
|
44 |
|
| 45 |
``` |
45 |
``` |
| 46 |
|
46 |
|