Hello everyone, these past couple months have been very busy. Now with a little free time I have decided to start coding C for the prizm. I looked over some peoples code examples in other posts and reconize the format. I have coded C++ in the past and remember some of it. I have a prizm, but don't know where to start.
What compiler do I use? Any other programs I have to run it through to change it for the prizm? System calls? Where do I start?
Thanks, Zeldaking

There is 3 SDK for Prizm (all made by community members).
Prizm GCC SDK is the simplest and use GCC (others use Renesas Compiler include in fx-9860 SDK).
In each SDK, a lot of include files are provided, to use syscalls. And a good documentation is include in the mini-SDK.

So, in my opinion, you only need the Prizm GCC SDK, and the documentation include in the mini-SDK.
See also this topic for useful functions.

We haven't publicly announced it yet, but we're working on documenting a lot of the system calls in a more organized format organized by their proper names on WikiPrizm.

Saxjax talks about it all of the time

@zeldaking: If you are on linux, there is a post here that shows how to build gcc for the prizm. For tutorials... Not sure. I learned by mucking about with the functions and testing.

(Now that I think about it, the wiki should have a section dedicated to getting started with prizm development)

Heartily agreed. Perhaps it could just link to the Cemetech thread that walks you through setting up the PrizmSDK?

I was thinking the opposite - compile all of the information on the forums and put a polished version on the wiki.

The setup steps can be added to the prizm wiki, along with tutorials for using functions all in one spot.

ok. I have downloaded PrizmSDK-0.3 and I have a code::blocks. how do I use a prizm compiler? Do I have to change compiler directory or do I use MinGW?

I actually just suggest making a batch script to compile and use a text editor like Notepad++, but if you're set on C::B you're going to have to manually find the /bin folder of the PrizmSDK and choose that as the compiler, and toggle for your project to use a custom makefile (the one you modified for use with the prizm SDK)

I also absolutely suggest using Notepad++; you're going to be able to start developing much faster than with CodeBlocks, I think.

Personally, I would love to use notepad++ for c programming. However, I have no clue how to write a batch file to make it compile for prizm.

It's as simple as this:

compile.bat:

Code:


However, I'm very uncomfortable helping you with Prizm coding considering your immature behavior with this training that got you your Prizm.

Yes, I understand what I did and I feel sorry for doing such thing. I deeply apologize what I have done and I'll ensure that never happens again.



That's all I have to do? is the location of batch file important?

Yes, it needs to be in the same folder as the Makefile and your source files. I recommend making a folder in the /projects/ directory of the PrizmSDK for each project you make, and copy in and modify as necessary the Makefile file from the /projects/default/ folder.

Could I just use Microsoft Visual C as the compiler?

No, because that's built to compile into an x86 binary, not SH4.

How about Notepad++?

That's not a compiler, that's a text editor. The compiler must be the one that comes with the SDK; you can use an IDE or Text Editor of choice.

Oh, okay that makes more sense. Thanks, what is the name of the sdk?

I have another question. There is a long list of stuff after clicking into the SDK, which files do I need?
---------------------------------------------------------
crt0.s 04-Oct-2011 20:38 1.7K
default.bin 23-Apr-2011 01:57 632
DEFAULT.c 12-Oct-2011 23:26 561
default.g3a 01-Jun-2011 16:54 28K
fxCG_G3A_STARTUP.src 26-Apr-2011 23:33 1.6K
fxCG_RAM_STARTUP.src 02-May-2011 21:39 919
GoL.g3a 19-May-2011 16:55 34K
libc.a 26-Nov-2011 21:42 603K
libfxcg.a 26-Nov-2011 17:58 124K
libfxcg.zip 22-Apr-2011 03:57 5.5K
libgmp-10.dll 04-May-2011 21:52 336K
libiconv-2.dll 05-May-2011 12:11 1.0M
libintl-8.dll 05-May-2011 12:11 120K
libm.a 27-Oct-2011 22:31 381K
libmpc-2.dll 04-May-2011 21:52 65K
libmpfr-1.dll 04-May-2011 21:52 266K
Makefile 12-Oct-2011 23:52 719
Minesweeper.g3a 19-May-2011 16:56 32K
Oblitr8.g3a 19-May-2011 16:50 204K
prizm.ld 04-Oct-2011 20:38 1.1K
PrizmSDK-0.1.tar.gz 19-May-2011 22:25 39M
PrizmSDK-0.1.tar.xz 19-May-2011 22:12 11M
PrizmSDK-0.1.zip 19-May-2011 22:19 39M
PrizmSDK-0.2.tar.gz 11-Aug-2011 22:12 38M
PrizmSDK-0.2.tar.xz 11-Aug-2011 21:38 9.2M
PrizmSDK-0.2.zip 11-Aug-2011 21:57 38M
PrizmSDK-0.3.tar.gz 25-Nov-2011 14:37 42M
PrizmSDK-0.3.tar.xz 25-Nov-2011 14:40 11M
PrizmSDK-0.3.zip 25-Nov-2011 14:51 42M
PrizmSDK-no-GCC.tar.xz 02-May-2011 22:09 16K
PrizmSDK.tar.gz 25-Nov-2011 14:37 42M
PrizmSDK.tar.xz 25-Nov-2011 14:40 11M
PrizmSDK.zip 25-Nov-2011 14:51 42M
sh3eb-elf-as.exe 20-Apr-2011 20:18 6.5M
sh3eb-elf-gcc-4.6.0.zip 02-May-2011 22:55 103M
sh3eb-elf-ld.exe 27-Apr-2011 01:12 6.6M
sh3eb-elf.tar.gz 22-Apr-2011 01:59 107M
sh3eb-elf.tar.xz 22-Apr-2011 01:41 38M
smallestprogram.zip 26-Apr-2011 23:31 2.0K
test.g3a 08-Oct-2011 03:00 52K
--------------------------------------------------------------------------------

One of those three. Download and extract somewhere, it's not important where.