Thread: Z80 Compiler (for Ti)

Then if someone can suggest anything better except for Dev-C++/GCC or whatever it was, then I'll happily listen. I can't even figure out what the resulting linked file is and what the Ti actually accepts.

I'm not under the impression that it supports additional compilers.
It wasn't designed to compile for other platforms than Windows.

Yes, that's what I did, since I have no need for the compiler.

Originally Posted by Elysia

Then if someone can suggest anything better except for Dev-C++/GCC or whatever it was, then I'll happily listen.

Did you look into tigcc?

Originally Posted by Dave_Sinkula

http://www.ticalc.org/programming/ ?

Originally Posted by Elysia

I can't even figure out what the resulting linked file is and what the Ti actually accepts.

It looked like you were trying to build an Intel hex file that you were calling it an .exe.

sdcc.exe --out-fmt-ihx -mz80 --profile --verbose --debug --out-fmt-ihx -mz80 --profile --verbose --stack-auto --debug -ID:\Program\SDCC\include -c main.c -o obj\Debug\main.rel
sdcc: Calling preprocessor...
sdcc: Generating code...
sdcc: Calling assembler...
sdcc.exe -LD:\Program\SDCC\lib -o bin\Debug\Test.exe --out-fmt-ihx -mz80 --profile --verbose --debug --out-fmt-ihx -mz80 --profile --verbose --stack-auto --debug obj\Debug\main.rel
obj\Debug\main.o: cannot open.
sdcc: Calling linker...
sdcc: Calling linker...
Process terminated with status 1 (0 minutes, 0 seconds)
0 errors, 0 warnings

I though this was saying to compile the .c into a .rel, and then link the .rel into an ".exe", and having no errors or warnings.

I would normally expect some .a type of file output from the linker which is then later translated into a .hex file for use with programming into the calculator. But then I'm not familiar with your system.

Originally Posted by Dave_Sinkula

Did you look into tigcc?

Nope, but I will. It looks interesting. Thanks.

It looked like you were trying to build an Intel hex file that you were calling it an .exe.
I though this was saying to compile the .c into a .rel, and then link the .rel into an ".exe", and having no errors or warnings.

I would normally expect some .a type of file output from the linker which is then later translated into a .hex file for use with programming into the calculator. But then I'm not familiar with your system.

Well, as I mentioned, since there's no documentation on the thing, I'm stabbing in the dark. Checking or unchecking the thing has no effect. The problem is that Code::Blocks doesn't supply the full path to the compiler.

Tigcc is indeed one might IDE, but it's for Ti-89+ and I have merely a Ti-84. Tried building n' compiling, but no luck in transferring any of the files it produced. Incompatible.
Perhaps it might work, perhaps not. I dunno.
I don't think the Ti-89 uses the same processor, does it?

Originally Posted by Elysia

I'm not under the impression that it supports additional compilers.
It wasn't designed to compile for other platforms than Windows.

of course it supports additional compilers. I was using Intel compiler with it
and Lint (which is not compiler itself, but operates as if it is...)

And destination platform depends on the compiler - not IDE

You're right. It does support other compilers.
But then, do tell me how to integrate another compiler into it, because I don't know.

Post on the codeblocks forums blasting them for their inadequacies (sp?)

Blasting the developers of an open source project (or the project itself, on its own forum) provided to you at zero price will only get you flamed, and rightly so. Asking for help, or reporting a bug/the lack of a declared feature might get you somewhere.

Originally Posted by Elysia

You're right. It does support other compilers.
But then, do tell me how to integrate another compiler into it, because I don't know.

Intel compiler adds itself into External tools menu and modifies the project files

PCLint is added into the External tools menu and creates some "Lint project file" based on the project


I would start with the mak-file type project and look here http://msdn2.microsoft.com/en-us/library/f2ccy3wt.aspx

to see If I can just replace several Envionment variables to point to the new compiler instead of Microsoft compiler, so that nmake will run these external tols instead of defualt ones...