New TIGCC FAQs - TIGCC Programming - Active Forums - TI-Chess Team HQ - Message Board - Message Board - Yuku

RSS
Email

0 Kudo

<< Previous Topic Next Topic >>

New TIGCC FAQs

Author	Comment
Kevin Kofler	New TIGCC FAQs	Lead	[-]
Posts: 7040 (2005-11-25 23:58:55) Admin More My Recent Posts Message Me Connection Blocking Invite Report Post	Some new questions have popped up frequently recently, and they are candidates for addition to the TIGCC FAQ. In the meantime, here's a list of the questions and answers: 1. Warnings/Errors Q: When I try to compile my program, I get "Implicit declaration of 'atof'" (or some other function) warnings, and then a link-time unresolved reference or a run-time misbehavior. Why is that? A: You need to define a satisfactory minimum AMS version for the functions you intend to use. Many functions require a minimum AMS version above 1.00, if you do not define an appropriately high minimum AMS version, these functions will be unavailable. Note that the best way to set the minimum AMS version in TIGCC IDE or KTIGCC is through Project/Options/Compilation/Program Options/Operating System. This way, consistency between all your source files is guaranteed. Please don't use #define statements in the source code to set program options, as that can lead to inconsistencies in settings which can cause a broken executable to be produced. 2. Experimental targets Q: Can I compile programs for the plain TI-92 or the TI-92 II with TIGCC? A: Yes, you can compile programs for the TI-92 and TI-92 II, using the Fargo shell. You need to fetch the required support library at: www.tigen.org/kevin.kofler/ti89prog/libfargo.zip . Copy fargo.a to your TIGCC Lib directory to enable the Fargo target. Note that Fargo support is incomplete, there are no official headers or library routines for Fargo at this time. You can however find some useful definitions in the source code of Kevin Kofler's Backgammon for Fargo . Q: Can I compile custom operating systems with TIGCC? A: Yes, you can create Flash OSes with TIGCC. Note that the OSes will not be digitally signed, you have to use a third-party utility such as FreeFlash or the older TIB Receiver to send them to the calculator. (On the other hand, emulators load them just fine.) You need to fetch the required support library at: www.tigen.org/kevin.kofler/ti89prog/flashosa.zip. Copy flashos.a to your TIGCC Lib directory to enable the FlashOS target. Note that FlashOS support is currently very barebone. There are no library routines for FlashOSes at this time, not even startup code to initialize the hardware. However, you can find such code in the source code of Patrick Pélissier's PedroM (ld-tigcc version). [EDIT (11/25/05 11:45 pm): Thanks to Jonathan Holbrook for rephrasing some of my awkward sentences. ] [EDIT: Added note about how to set MIN_AMS properly in the IDE.] Last Edited By: Kevin Kofler 2008-05-03 11:07:09. Edited 1 time.
Kevin Kofler	Re: New TIGCC FAQs	#1	[-]
Posts: 7040 (2005-11-26 00:31:02) Admin More My Recent Posts Message Me Connection Blocking Invite Report Post	3. The TiEmu debugger Q: How do I debug a TIGCC program using the TiEmu 3 source-level debugger? A: Before following the instructions below, make sure you have a TIGCC-debugging-enabled version of TiEmu installed. You can get current snapshots of TiEmu 3 (which include TIGCC debugging support) at: sourceforge.net/project/showfiles.php?group_id=23169. (Note that TiEmu 2.0x does not have TIGCC debugging support, you have to use the 2.80 snapshots.) 1. Make sure your program is uncompressed and debugging information is enabled: 1.a. In the IDE, go to Project/Options, uncheck "Compress program" (under "General") and check "Generate debug information" (under "Compiler"). 1.b. In the command-line compiler, pass -g and omit the -pack option. 2. Rebuild your project so everything gets built with debugging information. 3. Run TiEmu. 4. Right-click on the TiEmu screen, select "Debug file with TiEmu..." and send your main executable (the 89z, 9xz or v2z file). 5. If any other files are required to run your program, right-click on the TiEmu screen, select "Send file to TiEmu..." and send the required files. (You can send multiple files at once in this step, the file dialog allows you to select multiple files by Ctrl-clicking.) 6. Run your program from the home screen. This will make the debugger pop up. 7. Unless you're trying to debug a problem within the TIGCCLIB startup code, click on the "Continue" icon in the "Source Window" to skip to your main function. This will position the debugger on the first line of your main function. 8. You can now use the functionality of the user-friendly Insight debugger. If you are familiar with GDB, you can also enter GDB commands in the Console window. In addition, the VTI-style assembly-level debugger windows are still available, and its disassembly has been enhanced to make use of the debugging information to show label names in addition to the addresses. Q: I've noticed TIGCC does not annotate assembly files with C code when I select "Generate debugging information" anymore since TIGCC 0.96 Beta 4. How can I view the correspondence between C and assembly code for my program? A: Load your program into the TiEmu debugger as per the previous question. In the Insight "Source Window", select your file and function from the dropdowns. Now click on the dropdown saying "SOURCE". Choose "MIXED" instead. The result looks like this. It is also possible to print the resulting annotated source code to a printer or a file (under Windows, use the "Generic/Plain Text" printer driver to get a plaintext output; under Linux, use this command: echo '#!/bin/sh' >/usr/local/bin/lpr;echo 'ps2ascii >~/lproutput.txt' >>/usr/local/bin/lpr).
Kevin Kofler	Re: New TIGCC FAQs	#2	[-]
Posts: 7040 (2006-08-13 06:04:53) Admin More My Recent Posts Message Me Connection Blocking Invite Report Post	4. KTIGCC Q: Why is KTIGCC using Qt 3 and not Qt 4? A: Because KTIGCC uses KDE and KDE 4 is not ready yet. KDE 3 requires Qt 3.
Samuel Stearley	Reply to thy	#3	[-]
Posts: 1206 (2006-08-16 06:07:25) More My Recent Posts Message Me Connection Blocking Invite Report Post	Ezboard supports sticky threads. I suggest a sticky thread telling people to read the FAQ. -Samuel S
Kevin Kofler	Re: Reply to thy	#4	[-]
Posts: 7040 (2006-08-16 12:57:57) Admin More My Recent Posts Message Me Connection Blocking Invite Report Post	No, only the paid version of ezBoard allows sticky threads. And this topic is not intended for discussion, but for questions&answers.
Kevin Kofler	Re: One more (and a followup)	#5	[-]
Posts: 7040 (2006-08-29 15:18:11) Admin More My Recent Posts Message Me Connection Blocking Invite Report Post	5. Header Files (This one has been asked by Lionel Debroux on an unnamed competing message board. As other people are confused about this too, here it is.) Q: What header files should I include to get access to AMS system calls (ROM_CALLs)? A: For programs not needing a kernel ("_nostub", recommended), in C: #include <tigcclib.h> in assembly (A68k, GNU as): include "os.h" resp. .include "os.h" For kernel-based programs (not recommended, because kernels are not really needed except on the old TI-92), in C: #include <tigcclib.h> and define USE_KERNEL either in the Program Options subdialog of Project/Options (TIGCC IDE, KTIGCC) or in the global CFLAGS you pass to all command-line tigcc invocations. (Please don't put the library options inside source files as #define instructions, because they need to be consistent across all compilation units.) in assembly (A68k only): include "doorsos.h" These also give access to the RAM_CALLs widely supported by kernels. Any other headers providing access to ROM_CALLs and/or RAM_CALLs (including, but not limited to, <kernel.h> in C and romcalls.h and tios.h in assembly) are not supported by the TIGCC Team and may not be fully compatible with ld-tigcc. (This is definitely the case for the aforementioned assembly headers and old versions of the C kernel.h.) Q: Are the versions of os.h and doorsos.h (and/or the TIGCCLIB C headers) provided with TIGCC outdated and/or unmaintained? A: No! This is an unfortunate rumor put into circulation by the maintainer of the unsupported headers mentioned in the previous question. Along with the TIGCCLIB C headers, our assembly headers (os.h for A68k, os.h for GNU as and doorsos.h for A68k) have been updated for new ROM_CALLs as recently as TIGCC 0.96 Beta 7, the current beta of TIGCC. They contain lots of ROM_CALLs the competing headers (which are still stuck at AMS 1.05 era ROM_CALLs) still don't contain.

<< Previous Topic Next Topic >>