allenhuffman
Joined: 17 Jun 2019
Posts: 612
Location: Des Moines, Iowa, USA
|
| Command line compiling with CCSC.EXE and CCSCOMPILE.EXE |
 Posted: Thu Jan 30, 2025 2:21 pm |
 |
|
CCS support was helping me with my command line builds, and said I should be using CCSCOMPILE.EXE instead. Unlike CCSC.EXE, which pops up Windows during the build showing the status, CCSCMOPILE appears to stay entirely in the text command prompt. (It will pop up a window for help, if you use +H).
CCSCOMPILE.EXE is not referenced in the PDF manual, so I thought I would mention it here in case anyone else is doing command line stuff and does not know about it.
By itself, it did not work for me -- for our compiler, I had to add +FD to tell it which one to use.
The rest of the parameters remained unchanged, which is good. I do not see the "BUILD=" option documented, and that is how you specify your project to run:
| Code: |
ccscompile +FD #COMPILE_PARTITION='*' #BOARD=MULTIPLEXER #BUILD_FOR_BOOTLOADER=1 I="C:\Program Files (x86)\PICC\Devices;C:\Program Files (x86)\PICC\Drivers;..\Common\" BUILD=Project.ccspjt
|
My build script builds 14 hex files for each of the boards (versions of the app that load at different areas, bootloaders, bootloader installers, etc.). I just converted my old BATCH file build script to PowerShell.
The CCSCOMPILE will also return an error code so you can check for that. It seems to return 1 if success, though running it multiple times shows it sometimes gives me 0 and 255. CCS provided me with an update to CCSCOMPILE related to exit codes, so this may be part of that fix.
Enjoy...
_________________
Allen C. Huffman, Sub-Etha Software (est. 1990) http://www.subethasoftware.com
Embedded C, Arduino, MSP430, ESP8266/32, BASIC Stamp and PIC24 programmer.
http://www.whywouldyouwanttodothat.com ?
Using: 24FJ256GA106, 24EP256GP202 and 24FJ64GA002. |
|
FAQ 
Search
Register
Profile 
Log in to check your private messages 
Log in
