Author Topic: Compiling stuff for Prizm  (Read 69641 times)

0 Members and 2 Guests are viewing this topic.

Offline JonimusPrime

  • LV6 Super Member (Next: 500)
  • ******
  • Posts: 389
  • Rating: +25/-5
    • View Profile
    • Jonimoose.net
Re: Compiling stuff for Prizm
« Reply #75 on: October 05, 2011, 12:14:01 am »
I know this is a bit of a necro bump but I did release the "cemetech"(as Kerm so happily dubbed it) GCC PrizmSDK-0.2 a while back and would love to help anyone get it setup if needed.
 
As for using it on Mac OS X you would need to install xcode and then compile and install a gcc targetting the superh series processors. If you want I can help walk you through the process any time, just hop on irc, or use the chat box, and highlight me. You would just need some parts of my sdk and I have all those individual files available for download.
 
As to keeping this on par with Simons work I would really love to work with him on standardizing things a bit. I'm fine with the automated syscall generating and have written a script to duplicate its work for use with my SDK but the biggest issues I have are with the header and helper functions organization. As it stands right now you can't easily use the headers from one SDK with another or even reliably compile code written with one on another.
 
I'd like to fix that so that it is easier for the end users of either SDK to adapt them to their needs.
 
My first issue is the lack of clarity on whether or not C++ is really supported and why some headers and source files use hpp/cpp instead of h/c. IMO we should keep the SDK's and their API's pure C and leave it up to the users as to whether they want to use C or C++. Many of your headers are already encased in Extern "C" {} so why even bother having them use the .hpp extension?
 
My second issue also relates to the headers and it is the fact that you mix equates and structs used by syscalls with custom functions you have added. This increase the amount of work for me greatly and adds to user confusion because they can't tell what is a syscall and what is something you added to the SDK yourself.
 
My last issue is that darn chm file. :P Yes its nice that there is some documentation but damn is it a pain in the arse to find any of it in there. Omnimaga was kind enough to host the prizmwiki at http://prizmwiki.omnimaga.org we should use it. I have been trying to update it with some of the things I have found but its just not all that useful as it currently stands. I think the first step would be to start getting the syscalls on there. The documentation for them is scattered about this forum, your .chm file and our heads. Getting on in a centralized location would help everyone move forward and allow one to much easier find the information they need.

"Always code as if the person who will maintain your code is a maniac serial killer that knows where you live" -Unknown

"If you've done something right no one will know that you've done anything at all" -Futurama

"Have a nice day, or not, the choice is yours." Tom Steiner

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: Compiling stuff for Prizm
« Reply #76 on: October 08, 2011, 01:51:20 am »
That would really be great if we could get the wiki updated. I believe Jos Juice currently is the wiki admin and controls all of the major changes. In fact what I had in mind for the syscalls page was an organization system similar to wikiti.brandonw.net so that full documentation could be provided for each call. Right now the only syscall documentation is just copied from the .chm and is geared more towards asm coders and provides little insight to those who code in C. What we'll need in the discussion is an explanation of what each call does exactly, what all the args do, the use of the return value, ram locations destroyed, and how to effectively use it in a program.

But then again we aren't as reliant on syscalls for the Prizm as we were on the 83+. So far the only reason why I use a syscall is to draw the screen or depending on the program draw text. But they will become more important in the future as we start experimenting with some of the hardware such as the usb.

List of stuff I need to do before September:
1. Finish the Emulator of the Casio Prizm (in active development)
2. Finish the the SH3 asm IDE/assembler/linker program (in active development)
3. Create a partial Java virtual machine  for the Prizm (not started)
4. Create Axe for the Prizm with an Axe legacy mode (in planning phase)
5. Develop a large set of C and asm libraries for the Prizm (some progress)
6. Create an emulator of the 83+ for the Prizm (not started)
7. Create a well polished game that showcases the ability of the Casio Prizm (not started)

Offline JosJuice

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1344
  • Rating: +66/-14
    • View Profile
Re: Compiling stuff for Prizm
« Reply #77 on: October 08, 2011, 07:38:31 am »
Making separate wiki articles for the syscalls will make it much easier to find information. I'll create the category, links to it and such right now, but I'll need some help with adding information about the syscalls since there are so many of them.

EDIT: I've added a few syscalls, and they can be accessed by hexadecimal number from [prizm]Category:Prizm syscalls[/prizm]. Maybe there should also be categories that are based on what syscalls are used for (displaying things, file management, etc.) or lists with names of syscalls?
« Last Edit: October 08, 2011, 08:16:08 am by JosJuice »

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: Compiling stuff for Prizm
« Reply #78 on: October 11, 2011, 12:39:39 am »
I don't think the syscalls should be organized by number as it has little relevance to its actual use. A good way to have them organized could be by the library file each is stored in such as "display.h". But for the time being I'll see how well I can get the current list filled with important information.

List of stuff I need to do before September:
1. Finish the Emulator of the Casio Prizm (in active development)
2. Finish the the SH3 asm IDE/assembler/linker program (in active development)
3. Create a partial Java virtual machine  for the Prizm (not started)
4. Create Axe for the Prizm with an Axe legacy mode (in planning phase)
5. Develop a large set of C and asm libraries for the Prizm (some progress)
6. Create an emulator of the 83+ for the Prizm (not started)
7. Create a well polished game that showcases the ability of the Casio Prizm (not started)

Offline JosJuice

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1344
  • Rating: +66/-14
    • View Profile
Re: Compiling stuff for Prizm
« Reply #79 on: October 11, 2011, 08:48:10 am »
I was planning to do it like on WikiTI, in which the article names use numbers and the lists use names. I haven't figured out how to use names within the automatically generated lists, though.

Offline JonimusPrime

  • LV6 Super Member (Next: 500)
  • ******
  • Posts: 389
  • Rating: +25/-5
    • View Profile
    • Jonimoose.net
Re: Compiling stuff for Prizm
« Reply #80 on: October 12, 2011, 09:43:26 pm »
I agree that the numbers are generally useless, but I disagree with using the header file name as the organizational method, a simple category based method would be just fine. The issue with going by the header file name is that is one of the issues I have with simonlothar's SDK is the naming and setup of the headers. The stdlib related headers could be organizer as such but even there simon didn't follow the C standard and I really think that should be fixed.

Since we don't have official naming conventions from Casio I would see if we can standardize them, unless the naming we have been using is based off of the older Casio calcs. If that is the case then fine but it still irks me.

"Always code as if the person who will maintain your code is a maniac serial killer that knows where you live" -Unknown

"If you've done something right no one will know that you've done anything at all" -Futurama

"Have a nice day, or not, the choice is yours." Tom Steiner

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: Compiling stuff for Prizm
« Reply #81 on: October 13, 2011, 02:21:17 am »
We also need to modify the header files from both SDK's to have proper #ifndef blah_h, #define blah_h, #endif statements so that other libraries don't end up being accidently included twice once more third party libraries become available. 

List of stuff I need to do before September:
1. Finish the Emulator of the Casio Prizm (in active development)
2. Finish the the SH3 asm IDE/assembler/linker program (in active development)
3. Create a partial Java virtual machine  for the Prizm (not started)
4. Create Axe for the Prizm with an Axe legacy mode (in planning phase)
5. Develop a large set of C and asm libraries for the Prizm (some progress)
6. Create an emulator of the 83+ for the Prizm (not started)
7. Create a well polished game that showcases the ability of the Casio Prizm (not started)

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: Compiling stuff for Prizm
« Reply #82 on: October 13, 2011, 02:26:51 am »
Quote
The stdlib related headers could be organized as such but even there simon didn't follow the C standard and I really think that should be fixed.
Agreed. If there are C99/C1x functions in the OS, but these functions are not defined in the appropriate headers, it makes it harder to port programs to the new platform :)

In GCC4TI, I had to improve several things in the library and in the toolchain for the quite portable p14p and Lua code bases to be easier to compile. No official (I have posted the patches) release of p14p for TI-68k and the modified Lua89 can occur until the next official release of GCC4TI, otherwise Windows users wouldn't be able to compile them. *nix users can build from GCC4TI Git.
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline JonimusPrime

  • LV6 Super Member (Next: 500)
  • ******
  • Posts: 389
  • Rating: +25/-5
    • View Profile
    • Jonimoose.net
Re: Compiling stuff for Prizm
« Reply #83 on: October 18, 2011, 04:17:14 pm »
What I think would be really cool is if we could somehow make it so the syscall and general routine library could be portable between the compilers. For syscalls the asm.h header just needs to use the proper macro for the platform, along with the asm source files but the C sources should easily be portable between them with a little clean up.

I already have libfxcg hosted on github so that is a start but many of simon's helper routines don't even compile with gcc due to header file case errors, syntax differences and a few other issues.

"Always code as if the person who will maintain your code is a maniac serial killer that knows where you live" -Unknown

"If you've done something right no one will know that you've done anything at all" -Futurama

"Have a nice day, or not, the choice is yours." Tom Steiner

Offline Eiyeron

  • Urist McEiyolobster
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1430
  • Rating: +130/-10
  • (-_(//));
    • View Profile
    • Rétro-Actif : Rétro/Prog/Blog
Re: Compiling stuff for Prizm
« Reply #84 on: October 22, 2011, 08:26:30 am »
Hello!
I want to begin coding for Prizm, but i don't understand any micro/mini/nano/shufle sdk...
COud you help me, please?

Offline bynary_man

  • LV2 Member (Next: 40)
  • **
  • Posts: 24
  • Rating: +1/-0
    • View Profile
Re: Compiling stuff for Prizm
« Reply #85 on: October 22, 2011, 09:56:54 am »
I have the same problem... I don't know how can I build some g3a.

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: Compiling stuff for Prizm
« Reply #86 on: October 24, 2011, 03:21:14 pm »
Hello!
I want to begin coding for Prizm, but i don't understand any micro/mini/nano/shufle sdk...
COud you help me, please?
I have the same problem... I don't know how can I build some g3a.
I find that the easiest way to get started is to the gcc SDK hosted on cemetech at http://cemetech.net/forum/viewtopic.php?t=6613&start=0
start with the default project and compile it by running make.bat
To start your own project use the included makefile as a template and modify the sections that read default to that of your own project. Or for the time being while you learn, just modify the code of default and see what you can do. If you have any questions I recommend that you start a help topic here for your projects.

List of stuff I need to do before September:
1. Finish the Emulator of the Casio Prizm (in active development)
2. Finish the the SH3 asm IDE/assembler/linker program (in active development)
3. Create a partial Java virtual machine  for the Prizm (not started)
4. Create Axe for the Prizm with an Axe legacy mode (in planning phase)
5. Develop a large set of C and asm libraries for the Prizm (some progress)
6. Create an emulator of the 83+ for the Prizm (not started)
7. Create a well polished game that showcases the ability of the Casio Prizm (not started)

Offline Eiyeron

  • Urist McEiyolobster
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1430
  • Rating: +130/-10
  • (-_(//));
    • View Profile
    • Rétro-Actif : Rétro/Prog/Blog
Re: Compiling stuff for Prizm
« Reply #87 on: October 24, 2011, 03:54:26 pm »
I made a french tutorial to use mini-SDK, inspired by the Cemetech's...

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55941
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: Compiling stuff for Prizm
« Reply #88 on: October 24, 2011, 03:56:33 pm »
Nice. Is it available for download somewhere?

Offline Eiyeron

  • Urist McEiyolobster
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1430
  • Rating: +130/-10
  • (-_(//));
    • View Profile
    • Rétro-Actif : Rétro/Prog/Blog
Re: Compiling stuff for Prizm
« Reply #89 on: October 25, 2011, 10:47:40 am »
http://www.planet-casio.com/Fr/forums/topic10062-1-[C]-Du-C-sur-la-Prizm-Du-monochrome-a-la-couleur.html
Enjoy!
« Last Edit: October 25, 2011, 12:06:15 pm by Eiyeron »