README.linux 8.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232
  1. LINUX/UNIX/OS X PLATFORM SPECIFIC NOTES FOR TIGCC:
  2. ==================================================
  3. Note
  4. ----
  5. The current release SHOULD WORK on all Linux/Unix platforms, including
  6. MacOS X.
  7. Official binaries are provided ONLY for Linux/x86, so you will need to
  8. compile TIGCC from source on other platforms, unless an unofficial
  9. binary is made available for your platform.
  10. Copyright of the port:
  11. ----------------------
  12. The following copyright applies to the compilation and to the platform-
  13. specific tools:
  14. TIGCC for Linux/Unix - GCC port targeting the TI89/89Ti/92+/V200
  15. Copyright (C) 2000 Henri Moilanen
  16. Copyright (C) 2001-2002 Romain Liévin
  17. Copyright (C) 2002-2005 Kevin Kofler
  18. Some parts from John David Ratliff (TechnoPlaza tutorials)
  19. History
  20. -------
  21. Henri Moilanen:
  22. I like Linux. TIGCC wasn't available as a Linux version, so I had to
  23. create it. It hadn't source included, so I couldn't do any changes,
  24. and I had to start from scratch. Couple of days of hacking and
  25. searching the net, TIGCC For Linux was born. But as I worked alone - I
  26. had no hurry. It waited in the depths of my HD for a month until one
  27. person, Leonard Stiles, posted a question whether there is a ti-gcc
  28. for linux available.
  29. That was the push to get the job done. Like it or don't.
  30. Romain Liévin:
  31. I was developing TiLP (formerly GtkTiLink) when Henri was beginning
  32. to develop its TiGCC.
  33. Henri and some other people asked me whether I could develop a TI
  34. emulator for Linux. I have done it.
  35. Now, Henri asked me to take over the development of TiGCC/Linux.
  36. As you can see, I have accepted and I am now the official maintainer.
  37. John David Ratliff:
  38. Ported & tested on various UNIXes.
  39. Kevin Kofler:
  40. Since Romain no longer had the time to work on TIGCC for Linux, and
  41. since I always wanted it to be handled by someone of the TIGCC team, I
  42. decided to take over the project. I am planning to work on getting it
  43. to run again on platform/*nix combinations other than x86/Linux (now
  44. achieved), and to implement all features known from the Win32 version
  45. (IDE still missing, everything else done). See
  46. http://tigcc.ticalc.org/linux/ for the current status of the project.
  47. Installation
  48. ------------
  49. Installing from the binary RPM:
  50. -------------------------------
  51. * into /usr/local/tigcc (requires root privileges): rpm -ivh tigcc*.rpm
  52. * into ~/tigcc (user HOME dir): rpm -ivh tigcc*.rpm --prefix ~/tigcc
  53. Installing from binaries with the setup wizard:
  54. -----------------------------------------------
  55. * Download tigcc_bin.tar.bz2 and Install.sh into the same directory.
  56. * Make sure Install.sh is executable:
  57. chmod 755 Install.sh
  58. * Run Install.sh:
  59. ./Install.sh
  60. and follow the instructions. If you want a text-mode install on a
  61. system with KDE installed, you can use:
  62. DIALOG=dialog ./Install.sh
  63. to tell the script to use the text-mode (curses) dialog instead of
  64. kdialog.
  65. You will be prompted for the destination directory you want to install
  66. TIGCC to ($TIGCC). Then the wizard will extract the files there.
  67. When done, the wizard will ask you whether you want to add your $TIGCC
  68. setting to bashrc. If you answer "Yes", you are done here, you only
  69. need to restart bash. If you prefer to do things by hand, answer "No"
  70. and follow the instructions below. (If you selected "No", but changed
  71. your mind, you can also run envreg by hand afterwards.)
  72. Installing from binaries without the setup wizard:
  73. --------------------------------------------------
  74. First, copy your full tigcc binary package to '/'. You can use a
  75. directory of your chosing but you will have to move the uncompressed
  76. files.
  77. Then, install it by:
  78. bunzip2 tigcc_bin.tar.bz2
  79. tar xvf tigcc_bin.tar
  80. Now, set the environment variable TIGCC to the directory you
  81. extracted into. You need to set this variable in your profile,
  82. because the tigcc front-end needs it to find the header files.
  83. If you use bash, add it to your .bashrc file in your home
  84. directory. You could also use your .profile or .login if
  85. you have those. If you use tcsh or csh, put it in your
  86. .cshrc file (or if you use .tcshrc, put it there).
  87. I've never used korn shell. You're on your own if you do.
  88. For bash/sh users
  89. export TIGCC=/usr/local/tigcc
  90. export PATH=$PATH:$TIGCC/bin
  91. For csh/tcsh users
  92. setenv TIGCC /usr/local/tigcc
  93. set path=($path $TIGCC/bin)
  94. I've had problems using setenv to reset the path in tcsh.
  95. setenv path "$path ${TIGCC}/bin"
  96. doesn't seem to work.
  97. You may need to logout and log back in for that to take
  98. effect. Or you can resource your profile.
  99. source ~/.profile
  100. source ~/.bashrc
  101. source ~/.cshrc
  102. source ~/.tcshrc
  103. You only need to resource the file you changed.
  104. Compiling and installing from source:
  105. -------------------------------------
  106. See the INSTALL file for instructions for building from source.
  107. Note that I recommend to use the binary release when possible though.
  108. Available programs
  109. ------------------
  110. - a68k: AmigaOS assembler
  111. - as: GNU assembler
  112. - ar-tigcc: TIGCC archiver
  113. - gcc: GNU compiler
  114. - ld-tigcc: TIGCC linker
  115. - patcher: patches .s files generated by gcc (mainly for internal use)
  116. - tigcc: the front-end for using TIGCC
  117. - tprbuilder: a program for building .tpr files (Tigcc PRoject).
  118. - tt*: a lot of utilities from the TIGCC Tools Suite
  119. Only tigcc and tprbuilder are intended to be called directly. The TIGCC Tools
  120. Suite might be distributed separately in the future (as it is for Windows). Its
  121. continued presence as a part of the TIGCC for Linux/Unix package is not
  122. guaranteed. All other tools are intended to be called through the tigcc frontend
  123. only.
  124. In addition, there is a shell script called tigccdoc, which will open the HTML
  125. documentation in QT Assistant 3.2 or higher, a help viewer offering the same
  126. features Microsoft HTML Help offers under Windows: content hierarchy, alphabetic
  127. index and full-text search. The GPL version of QT Assistant can be obtained for
  128. free from http://www.trolltech.com . For binary packages, check with your
  129. Linux distributor or operating system vendor.
  130. For QT Assistant versions older than 3.2, you can manually add qt-assistant.dcf
  131. to your documentation sources. However, this has the disadvantage that the index
  132. and the full-text search will mix entries from the QT documentation with entries
  133. from the TIGCC documentation, so it is recommended to use QT Assistant 3.2 and
  134. tigccdoc instead.
  135. Usage
  136. -----
  137. Simply call tigcc and pass your filenames and any desired flags (the
  138. flags listed here are the minimum recommended flags for all TIGCC
  139. programs):
  140. 'tigcc -Os -ffunction-sections -fdata-sections --optimize-code
  141. --cut-ranges --reorder-sections --merge-constants --remove-unused
  142. -Wall -W -Wwrite-strings test.c'
  143. Once you have created your program, you can test it on an emulator
  144. (such as TiEmu) or directly on your calculator. For this, you have to
  145. transfer the program using a linking program (such as TiLP).
  146. Examples
  147. --------
  148. You will find in the examples directory some projects which come from
  149. the TIGCC/Win32 SDK. You can build them by:
  150. 'tprbuilder myproject.tpr'
  151. If you have installed TiLP (http://lpg.ticalc.org/prj_tilp), you can
  152. load the program. Simply do a 'tilp -cmdline foo.89z' (console) or
  153. 'tilp foo.89z) (X11).
  154. Development platform used for the binary release
  155. ------------------------------------------------
  156. Machine: Pentium III running Fedora Core 4
  157. Compiler: gcc version 4.0.1-4.fc4 (Fedora Core 4) (rpm -q gcc)
  158. Kernel: Linux 2.6.13-1.1526_FC4 for i686 (Fedora Core 4) (uname -a)
  159. Libc: glibc 2.3.5-10.3 for i686 (Fedora Core 4) (rpm -q glibc)
  160. Thanks
  161. ------
  162. By Romain Liévin:
  163. Rudolf Polzer He was the first guy to test my (Romain) first release
  164. of TIGCC and has helped me to understand the patch
  165. mechanism.
  166. Kevin Kofler Some information about the tipatch mechanism.
  167. By Kevin Kofler:
  168. I would like to thank my collegues from the TIGCC team (Sebastian
  169. Reichelt, Zeljko Juric, ...) and the previous maintainers of TIGCC for
  170. Linux (Henri Moilanen, Romain Liévin) for the excellent work done,
  171. which allows me to release this package.