Hello all! I'm happy to announce that version 1.0 of the C development SDK for the TI84+CE and TI83PCE is available on GitHub now. Rather than going through this crazy process, you can now simply download the zip file, copy the folder to somewhere on your computer, set up your environment variables specific to your OS, and then use make in order to build your programs locally. Of course, it uses the ZDS compiler which is only natively supported on Windows, but works perfectly under Wine. If you wish to avoid even more hassle and you have access to the onlines, you can also use TI Planet's C Project Builder, available here: https://tiplanet.org/pb/ (You will need an account if you don't have one)

Now, ignoring all the craziness that happened with licenses, some standard CE C libraries have also been released. Currently there are 2; one for graphics and one for interfacing with the keypad. Included in each you will also find example programs in C using these libraries, and ASM source code licensed under the BSD 2 Clause. These libraries outperform their direct C equivalent as they are written in assembly and can behave however they want. Since they are still in version 1.0, there's a long way to go. But since things are easy to add to now, hopefully I can get some help Anywho, here are the links so you can build your own programs, along with a screenshot using the C graphics library just for fun.

C Development SDK: https://github.com/CE-Programming/toolchain/releases/latest
C Standard Libraries: https://github.com/CE-Programming/libraries/releases/latest

Enjoy everyone, and please post any pull requests/bug reports and comments you may have! This has been a long ride



Note:To install libraries so you can use them in development, simply read the readme provided on GitHub or in the zip. It's really easy.

Yay! Now all I need is an actual CE...

Great job as always. Can't wait to see more in the future!

Ditto.

Congrats on all your hard work Mateo! It's been great seeing this project progress. I can't wait to see what the community makes with this SDK.

I'll have to get a CE now. (do I need a rom to use CEmu?) I could port Catylizm!

This is absolutely fantastic, Mateo! This is what I've been waiting for to start on Minesweeper

Great work Mateo! We should also consider starting a data-structures and algorithms library. I currently have a singly-linked-list + merge sort implementation, and also found a Red/Black tree implementation which I've improved to a polymorphic version that can be used as the backing store for both a map and a set.

I also plan on releasing my scan-line renderer once I finish working out the kinks and the API, and would be willing to incorporate that into your graphics API.

Sure, sounds great. There's a minor bug when drawing lines with the library right now, but shouldn't be too much of a problem to fix by tomorrow. Luckily ZDS also outputs the ASM source so libraries can easily be created with C code. (Which can also later be optimized )

Note: Unfortunately ZDS is really limited in how it outputs things, so libraries can't be directly created in C. But it is pretty much a copy/paste for the library structure.

You do. There are two ways to dump your ROM:
* the off-line partial ROM dumper (rom8x-type) provided by CEmu, made by Mateo;
* the connected whole ROM dumper provided by TILP beta (libticalcs), made by jacobly (calculator side) and myself (computer side), which does not interfere with the Flash memory's contents. It uses a relatively slow method, because USB communication is not yet documented in such a way that we can use an arbitrary protocol, but it works well too, at least under Linux.

A few small bugs have been fixed in the graphics library, along with the addition of 3 general purpose sprite routines. You can use ConvPNG to convert your images into data arrays that you can then use with the library routines if you wish. Please note that library header files include limited documentation of the routines; hopefully I can finish the online reference at some point Anywho, since nothing has been created with the libraries yet, the graphics library shall remain as version 1. Version 2 will add clipping to all the NoClip routines, which will be backwards compatible with verison 1 as well, as per the library setup. More routines as well, because why not, and probably some cool optimizations. Thanks everyone!

Also, if anyone is interested in how to actually create assembly libraries, simply navigate your way to this page:
http://ce-programming.github.io/documentation/tutorials/asm/lib-creation/

You can also use the standard libraries in order to get started, as those should be helpful guides.

Edit:Work has begun on a simple I/O file library that use native OS functions. For example; "f_CreateAppVar("AppVar",100);" will create a 100 byte AppVar if possible, and return a pointer to the data. If it fails for some reason, it will return NULL. Other functions are available to find, write, and read to AppVars, and later support will be for any variable type.

So I seem to have run into a bit of a roadblock.

Unfortunately ez80cc seems to crash under wine for me, and PB reports compile errors but won't display them (it's a multifile project)...

Need a little more information please What project, errors, links, etc. Thanks!4

Note: Try modifying the makefile to include source in multiple directories if you have a project that has sources files in multiple directories.

The PB version is here (I assume adri has to poke at it?).

As for ez80cc, I doubt there's much you can do, but...

Code:

For reference, the compiler is spitting crazy internal errors on a trivial macro invocation, then a function call... and who knows what else it could yield on other parts of your code.

Specifically:

Code:
and invocations of

Code:

CE SDK has been updated to 1.1 in order to use an improved makefile from jacobly, in addition to be able to use the exit() function to jump out of your program.

I somehow can't get it working. I follow your steps, by creating a User Variable in the System, etc.
That will look like this:

I've set the PATH variable like that:

With that, I opened Command Prompt, and type "make" which should work, but it gives me always this:


I'm sure it is the right folder.

Can someone help me get it working?

Windows 10 (probably that's enough.. )

You need "" around the PATH variable. Try "C:\Users\Peter\My Documents\ez80\CEdev\bin"; instead.

Many, many thanks for this, and your help over SAX!
I moved the folder to somewhere else, which has no spaces in the directory file, and now it works

Cool, sounds good I'll update the readme a little more to be a bit more guideful.

Also, I am done with version 1.0 of the File I/O library. Rather than tell you all about it, here is the header file for your amusement. It operates almost identically to the standard fread, fwrite, etc, just that the type is an unsigned int rather than a FILE*.

EDIT: Here's the library routines so far in case anyone is interested in not doing things the super hard way anymore: (Seriously though, you can make pretty much anything now. It's so easy, it's kind of ridiculous no one has )

All this information will be made into an a webpage on the documentation page with clickable links for each function. I would be much obliged if someone could test some of these functions to make sure they are all working properly. Beta testers, anyone?

File IO library:

Code:


Graphics Library:

Code:


Keypad library:


Code:

Another question: how can I display a string in Ans on the screen? I think it should be something with _RclAns, and _CreateTempString, but I've no idea. Or in pseudo-code:

Code: