search

BrettMayson / HEMTT

Build System for Arma 3
http://hemtt.dev/
GNU General Public License v2.0
113 stars 40 forks source link

Cannot NOT binarize cpp files #671

Closed CrashDome closed 7 months ago

CrashDome commented 7 months ago

Tools (complete and add to the following information):

Description: Upgraded and now notice all my config.cpp files are binarized in dev build. Also main addon has SQFC files - not sure if related. Other addons in folder have config.bin but no sqfc files.. Tried the binarize.enabled = false to no avail. Cannot for the life of me get it to stop doing this.

Steps to reproduce:

  1. Have a project with 7 addons and 1 optional
  2. Run '.\hemtt dev -O'
  3. All addons including optional have config.bin files
  4. only main addon has compiled sqf files

Expected behavior: Neither config.bin nor sqfc files present

Logs: Available at request

Additional context: only have one hemtt\project.toml file and one additional addon.toml file in main addon folder. I temporarily removed the addon.toml to see if any change and noticed none.

project.toml file: name = "XPS" prefix = "xps" author= "Crashdome" reuse_private_key = false

[files] include = ["readme.txt"]

[binarize] enabled = false

BrettMayson commented 7 months ago

reuse_private_key = false

This doesn't exist on HEMTT 1.*

[binarize] enabled = false

This can only go in addon.toml

If you want to to disable config.bin, that is rapify

Although, why do you want to disable config.bin and use config.cpp? Disabling rapify will also disable HEMTT's checks of your configs

CrashDome commented 7 months ago

This can only go in addon.toml

If you want to to disable config.bin, that is rapify

Although, why do you want to disable config.bin and use config.cpp? Disabling rapify will also disable HEMTT's checks of your configs

I see my mistake. And yes, I want to disable all checks when debugging. Some checks are not valid such as "A3_DEBUG is undefined" when doing conditionals (#if A3_DEBUG == 1..) At least at this point when other tools for debugging dont solve some needs I have that I can use some macros for (yes, all macros are out of cpp files - they just dont behave properly when config is rapified). For builds I dont use these macros anyway. - Optionally maybe introduce the --no-rap parameter for dev command. I would like to globally do this once in awhile and editing several addon.toml files to turn on/off is a pain. I use dev instead of build because I have A LOT of optionals and I want them all grouped together when debugging but seperate when producing builds. Consider maybe allowing that for dev flag? - thank you.