forked from positively-charged/bcc
-
Notifications
You must be signed in to change notification settings - Fork 4
CommandLineOptions
TDRR edited this page Jan 17, 2023
·
8 revisions
./zt-bcc [options] source-file [object-file]
| Option | Description |
|---|---|
| -acc-err | On error, create an error file like one created by the acc compiler. |
| -acc-stats | Show compilation statistics like those shown by the acc compiler. |
| -h | Show help information. |
| -i directory | Add a directory to search in for files. |
| -I directory | |
| -one-column | Start column position at 1. Default is 0. |
| -tab-size size | Specify the width of the tab character. |
| -strip-asserts | Do not include asserts in object file. (Asserts will not be executed at run-time.) |
| -E | Do preprocessing only. |
| -D name | Create a macro with the specified name. The macro will be defined as 1. The macro will only be available during the preprocessing of the main library. |
| -l library | Create a link to the specified library. This is the same as: #linklibrary "library"
|
| Option | Description |
|---|---|
| -cache | Enable caching of libraries. Only imported libraries are cached. |
| -cache-dir directory | Store cache-related files in the specified directory. If one is not specified, a system-default temporary directory will be used. |
| -cache-lifetime duration |
Keep a library cached for the specified duration. The duration is measured in hours. |
| -cache-print | Show the contents of the cache. |
| -cache-clear | Delete all cached library files. |
SLADE supports using BCC as an ACS compiler. The following sections describe how to make SLADE use ZT-BCC.
Download the latest version of ZT-BCC. Create a new folder, naming it whatever you want. Then extract the contents of the ZIP file into the folder you just created.
The following steps describe how to configure SLADE to use ZT-BCC:
- Start SLADE
- Open the SLADE Preferences window
- Open the Scripting page, then open the ACS page
- Press the Browse button, then go to your ZT-BCC folder and select the zt-bcc executable file
- Press Apply
SLADE only exports files it recognizes as ACS (typically by having the .acs extension) so the compiler can see them. This means that ZT-BCC can only include files if they have the .acs extension when used with SLADE, so all #included/imported files must have the .acs extension, and not .bcs/.h. This is a SLADE problem and there's currently no documented way around it.