can't get catalina c and code:blocks to play nice

b.p.m.

hey everyone,
i decided to try catalina c with code:blocks, but i'm not having
much success. i followed the installation instructions to the
letter, but no go. i did have to modify 'default.conf' so the
master path for catalina was instead of C: because i have
four partitions and XP is on with code:blocks and catalina.

now code:blocks finds catalina c seemingly okay; it finally
started showing up in the compiler list. but, when i build (or
rebuild) i always get the same message about the object file
for the program can not be found (it says 'no file or directory
can not be found). is this a code:blocks problem or a catalina
problem?

any help would be appreciated as i am dying to try coding
the prop in C (i need that goto statement). any wild off the
wall suggestions would also be considered.

blake

Heater.

b.p.m.

i need that goto statement

Cant' help with your problem but I'm really intrigued to know why you need that goto.

RossH

Hi b.p.m

This issue was recently discussed recently in another thread. If you have installed Catalina into a directory other than the default (on windows this is C:\Program Files\Catalina), then there are a couple more installation steps you will need to do for Code::Blocks to work:

1. Set your LCCDIR environment variable. To do this in Windows XP, enter Start->Settings->Control Panel->System and then select the Advanced tab. Press the Environment Variables button and then New. Add a new variable LCCDIR with the appropriate value (e.g. C:\Program Files\Catalina2). Then close the dialog box and restart Code::Blocks so it sees the change.
2. In Code::Blocks, select Settings->Compiler and Debugger..., then select Catalina as the compiler (I suggest making this the default). Then select the Toolchain executables tab and update the Compiler's installation directory to the location you have chosen for Catalina (e.g. C:\Program Files\Catalina2).

Of course, the example workspaces I provide also have the default Catalina path hardcoded into them - unfortunately there is nothing I can do about this - but you can simply create new workspaces from within Code::Blocks as required and everything should now work correctly.

I'll update the documentation in the next release. Let me know if you have any more trouble.

Ross.

b.p.m.

hey ross h
thanks for the info. i just had to change that system variable described in step 1. now code:blocks and catalina work together fine. i compiled the othello demo (after setting DEMO board as the default, ain't got no fancy hydra) and it works perfectly. thanks again for a great compiler. i can't wait to really get into it.

@heater: ok i don't 'need' the goto statement, but i sure want it. i'm an old school coder use to working in fortran and c (and asselmbly), i just find OOP almost an alien concept to me. if spin had gotos or jumps and address labels i could get into it. also using a compiler as opposed to a on chip interpreter i imagine would speed up execution times (why has no one come up with a spin compiler?).

blake