Post 4 – Retro C IDE – Settings

In order to automate code generation, saving code, compiling and running in an emulator information about file locations, compiler switchers, emulator settings are needed.  This is going to be handled on the Settings form.  The form can be accessed from the Settings menu option or the Compiler and Emulator settings button on the tool bar.


When selected this form is displayed:


At this point there are three groups, CC65 compiler settings, Emulator settings and Utilities.  There is extra space as I have not yet decided how to incorporate  directory locations for the source code based on computer type.

Lets look at CC65 (compiler) settings :


The CC65 button brings up a file dialog to select the CL65 executable.  CL65 is a combined compiler and linker, taking source and creating the finished executable.

Under this are the files to type in Compiler switches and any file extensions for the compiled executable.  The VICE emulators for Commodore computers likes .PRG, Alitrra the Atari emulator uses .XEX, and CC65 creates a tape header on the Oric Atmos executable so .TAP is needed.  AppleWin is a bit of a different situation, it wants the program to be on a disk image.  This requires an extra step and the CiderPress utility to do so (see below),  but no file extension is needed.

The next group is to set up the emulators:


There is a button for each computer that will invoke a file dialog to select the emulator executable.  Of course one needs to have already installed the emulators for this to work.  Most of the emulators have some switches that allow them be to started with the compiled programs automatically,  (AppleWin, and Oricutron work slightly differently in that when the emulator is started with the applicate one needs to run the program).

This IDE will include the filename, the Prefix and Suffix are settings that are added to the command line before and after the filename:

<emulator executable> <prefix> <compiled program> <suffix>
for example : “vice64.exe -autostart myprog.prg”

The AppleII example above starts the emulator with the disk image in the drive, then one will type at the BASIC prompt BRUN myprog
For Oric the tape image will be automatically loaded, and just typing RUN will start the program.  I will post some videos to show this in action.

Finally, utility programs can be set up.  Right now only CiderPress has a place.  I will be added one for FileZilla, for easy access to move files to a Raspberry Pi.  Likely there will be a couple of spaces for user defined utilities.  The parameter given is for the disk image I want to add the newly compiled program.  I’m working to see if there is a way to automate this, but right now I need to add the file and change file type manually in CiderPress, A2Tools may be an alternate approach to this, but I need to focus on the IDE at this point.


The next post will begin the code building of a window!!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s