Some required configuration to satisfy CBA/ACE3/ACRE2 and other projects I want to use this project on:
[x] Header extensions (prefix and other user-made ones) - example: -e "version=<git-hash>" - read from hemtt.json and straight passed to armake2's cmd_build -> #30
[x] Signature name (-s <signature> in armake2) - just use instead of middle part -> #30
[x] @mod folder name - template setup -> #30
[x] Key name (bikey) - template setup -> #30
[x] Release archive name (ACE3 does ace3_3.1.0.zip, CBA does CBA_A3_v3.1.0.zip) to zip utility - template setup -> #9
Disable specific warnings (-w --warning <wname> in armake2) - add to armake2's list of ignored warnings -> #197
Build folder (eg. armake setup with ACE3 builds into @ace/addons and also copies other files, that way you get a closer to release build preview, releases are probably best kept completely separate, or also not, HEMTT could resolve that easily)
Some required configuration to satisfy CBA/ACE3/ACRE2 and other projects I want to use this project on:
-e "version=<git-hash>"
- read fromhemtt.json
and straight passed to armake2'scmd_build
-> #30-s <signature>
in armake2) - just use instead of middle part -> #30@mod
folder name - template setup -> #30ace3_3.1.0.zip
, CBA doesCBA_A3_v3.1.0.zip
) to zip utility - template setup -> #9Other:
-w --warning <wname>
in armake2) - add to armake2's list of ignored warnings -> #197Build folder (eg. armake setup with ACE3 builds into@ace/addons
and also copies other files, that way you get a closer to release build preview, releases are probably best kept completely separate, or also not, HEMTT could resolve that easily)