[Coco] BASIC compiler for Rainbow IDE ?

[Roger Taylor]

At 10:13 PM 5/14/2008, you wrote:
>:-O :-X :-D !!!!!!!!
>I would get a new job just to be able to pay for it!
>
>Diego


Coders, read on...

Here's a Rainbow IDE trick:

Anyone can try it now to get an idea of how to work with existing 
compilers or what I plan on doing.  Ofcourse, a later version of 
Rainbow will simplfy all of this so you won't have to have source 
files in a certain build order.
----

I make it sound complex, but it's rather simple once you do it once.

Start a new project, create a new Source Component, call it 
"compiler.bas", select "Copy" for the Output Object, type 
"..\test.asm" for the Output Filename (without the quotes).  Why 
"Copy" ?  No compiler is being used yet so we just fake-make an output file.

Click "+" to create 2 default virtual disks.

Create a new Source Component, call it "make.asm".  Somewhere in the 
file: include test.asm (do not put quotes around test.asm).  Select 
multi-origin for the Output Object, type "test.bin" for the Output 
Filename, select CCASM_RogerTaylor for the assembler.  Select "Disk1" 
for the virtual disk.

Click Go.

compiler.asm will copy into a file called test.asm
   (we can pretend that compiler.asm is compiling into test.asm)

test.asm will copy onto the virtual disk (Rainbow does this because 
there's no way to Not select at least one of the available virtual 
disks to receive the output object)

main.asm will include test.asm and assemble into test.bin

test.bin will copy onto the virtual disk

So what we've done is pretend-compiled "compiler.bas" into "test.asm" 
then assemble "test.asm" into "test.bin", which ends up on a virtual 
disk ready to run (if it were an actual program).

When a BASIC compiler becomes available, Rainbow will detect it and 
add it to the list of available "assemblers".  For any .bas file, 
you'd choose the compiler for that file, and go through the other 
steps I mentioned above.  That's it!

The solution is that you have to use Boisy's DECB.EXE disk imager if 
you're building onto a virtual disk.  IMGTOOL.EXE can't handle the 
Files\..\test.asm path.
Just choose DECB.EXE in the left sidebar.  In fact, for anybody not 
using Rainbow, *everything* I mentioned above can be selected from 
the left sidebar and there's no getting lost in the IDE or wandering 
through confusing menus.

It's really very simple, and here is the project container file (.bow)


project_author          "Roger Taylor"
project_description             ""
mess_system             "coco3h"
image_name              "disk1"
image_name              "disk2"
image_type              "coco_jvc_rsdos"
imager_index            "1"
image_format            "SS35"

[projectfiles]
"asm","test.bas","..\test.asm","copy","E","0","0","","","CCASM_RogerTaylor"
"asm","make.asm","test.bin","multi-origin","E","0","0","","","CCASM_RogerTaylor"


SO... the big question now is... what 6809 compilers are out there 
that can generate CCASM or EDTASM compatible source code?  If you 
find one and do what I suggested above, PLEASE post your results here?

Thanks