Being able to add "#option" and "#variables" settings to the command line would be a great addition for other things as well....Or should the command line accept "#variables" rather than defines?
For example, right now I have a project .bas that supports different #options for different builds. To generate these I have to manually edit the options, compile, rename the resulting hex file, etc. If I could specify #options on the command line then all that could be automated with batch files and the command-line compiler.
I don't remember where i got this info from, but I don't think I ever found it in a file. It's not in the MPASM 8bit_device.info file, not in the .dev file, and not in the MPLAB internal .PIC file either.Alternatively, if the ICD_ROM and ICD_RAM could not be extracted from any microchip files when auto-generating the Swordfish device files
It's a linker function so you'd think it's controlled there, but I don't recall seeing the actual info in the .lkr files either. The .lkr files have a section in them that relies on various _DEBUGxxxxx symbols getting set, but for the life of me I have no idea where it gets this info.
I think maybe I just bit the bullet and sat down with the MPLAB help file and extracted it from there.
All of this raises a good point. MPLABX uses a different set of files for all this, different assembler, etc. If they don't keep MPASM up to date, then future devices may need to use that tool chain (mpasmx). Maybe a discussion for a different day...