Managing Multiple Targets with Catalina
fake_name
Posts: 3
Basically what the title says.
I have multiple different pieces of hardware. They have various crystal-frequencies (5, 6, 10, 12 Mhz, generally, depending on what I have on hand).
Right now, the crystal frequency is specified in `C:\Program Files (x86)\Catalina\target\Custom_DEF.inc`
This is in the Program Files directory, by default (where the installer places it). As such, on W7/Vista, it's a giant pain to edit (you need administrator permission).
Right now, I have overwritten the Demo_DEF.inc with the contents of the Custom_DEF.inc and changed the XTALFREQ in the updated file to give me two configuration options, but this solution seems kind of ridiculous.
Is there any way I can override the settings in the .inc file by adding things to my .c file? Or alternatively, is there any way I can have a local .inc file for every project?
For that matter, how would I even go about adding new targets? There seems to be a grand-total of one `Custom` profile.
I have a similar problem with the libserial4 library. All the pin definitions are hard-coded in the `Extras.spin` file, which is again in the Program Files` directory.
I don't have the serial interfaces in the same place in every project.
How can I have per-project configuration for the libserial4 library?
Better yet, is there anyway I can just specify the pin numbers for the serial interface in my C source? I'd be happy to have to call an initialization library, much as you have to with the spin FullDuplexSerial library.
Basically, putting platform-definition files somewhere *other* then in the actual project files seems like a terrible idea. Furthermore, the Catalina installer places all the definition files in the Program Files directory, which requires administrator permission to modify.
*Note that I'm doing this from within the Code::Blocks IDE (and want to continue doing so).
I have multiple different pieces of hardware. They have various crystal-frequencies (5, 6, 10, 12 Mhz, generally, depending on what I have on hand).
Right now, the crystal frequency is specified in `C:\Program Files (x86)\Catalina\target\Custom_DEF.inc`
This is in the Program Files directory, by default (where the installer places it). As such, on W7/Vista, it's a giant pain to edit (you need administrator permission).
Right now, I have overwritten the Demo_DEF.inc with the contents of the Custom_DEF.inc and changed the XTALFREQ in the updated file to give me two configuration options, but this solution seems kind of ridiculous.
Is there any way I can override the settings in the .inc file by adding things to my .c file? Or alternatively, is there any way I can have a local .inc file for every project?
For that matter, how would I even go about adding new targets? There seems to be a grand-total of one `Custom` profile.
I have a similar problem with the libserial4 library. All the pin definitions are hard-coded in the `Extras.spin` file, which is again in the Program Files` directory.
I don't have the serial interfaces in the same place in every project.
How can I have per-project configuration for the libserial4 library?
Better yet, is there anyway I can just specify the pin numbers for the serial interface in my C source? I'd be happy to have to call an initialization library, much as you have to with the spin FullDuplexSerial library.
Basically, putting platform-definition files somewhere *other* then in the actual project files seems like a terrible idea. Furthermore, the Catalina installer places all the definition files in the Program Files directory, which requires administrator permission to modify.
*Note that I'm doing this from within the Code::Blocks IDE (and want to continue doing so).