Commit 4071eeec authored by Andreas B. Mundt's avatar Andreas B. Mundt

Imported Upstream version 3.03-nogdb+dfsg

parents
This diff is collapsed.
The TiEmu project is managed by the TiEmu team.
The TiEmu team includes the following people:
!!! For problems, questions, ... use the TiEmu mailing list:
<gtktiemu-users@lists.sf.net>. Don't mail authors directly !!!
Romain Lievin (roms): main developer, Win32 port
================================================
web: http://lpg.ticalc.org
mail: roms@lievin.net
Julien Blache (jb): GTK2 upgrade of TiEmu-I
===========================================
web: http://jblache.org
mail: jb@jblache.org
Kevin Kofler (kkofler): gdb integration, fixed and patches
==========================================================
web: http://tigcc.ticalc.org
mail: Kevin@tigcc.ticalc.org
Christian Walther (cw): Mac OS-X port
=====================================
web: ??
mail: cwalther@gmx.ch
Jaime Fernando Meza Meza (jf): icon & skin design
=================================================
web: ?
mail: jaimezacalcs@yahoo.com
Packagers:
==========
- Julien Blache <jb@jblache.org>: Linux/Debian
- Romain Lievin <roms@lievin.net>: Win32
- Kevin Kofler <Kevin@tigcc.ticalc.org>: Linux/Fedora ?
All the others who have contributed to
======================================
Some contributions have been brought about this software by people:
- code: Kevin Kofler
- help: Olivier Armand and Lionel Debroux
- pedrom: Patrick Pelissier
- logo: hibou (real name ?)
*------------ Previous releases ----------------*
Roms aka Romain Lievin
web: http://www.lievin.net
mail: roms@lievin.net
Tom aka Thomas Corvazier
web: http://lpg.ticalc.org/prj_tiemu
mail: corvazier@yahoo.com
The libti68k library is based on the Jonas Minnberg's emulator
named (X)Tiger. He has recently released its emulator under GPL licence.
See the LICENSES file for more informations.
\ No newline at end of file
List of known bugs to fix:
SF.net's bug list
=================
2489443 Screen Elements Ignored by TiEmu
1891657 TiEmu can't find glib-2.0-0.dll from Glib 2.14.3
1649068 Keyboard layout under Linux
1569553 pc-TiEmu link
1555602 Missed key presses w/ TabletPC Stylus
1305067 "busy" flickers
1249087 Key mapping failed
Kevin
=====
* Il y a un bogue avec le débogueur et les touches: prends un AMS 2.0x ou 3.0x, mets
un breakpoint sur le trap #11, lance un programme ASM (même Exec "4e750000" suffit),
quitte le débogueur, appuie sur n'importe quelle touche, il réagit comme si c'était ENTER.
Seulement après avoir désactivé le BP sur le trap 11 et appuyé sur ENTER une autre fois,
TiEmu reprend son comportement normal.
Ce problème est apparemment causée par le fait qu'une touche (ENTER) est appuyée au moment
où on entre dans le débogueur. (Le BP sur le trap 11 s'active au moment où ENTER est encore
appuyé.)
* transferts lents
Lionel
======
* Un bug bizarre, dont les instructions de
reproduction semblent être:
* utiliser un AMS "récent" (2.07+), sur une 92+ ou
V200 (peut-être 89 aussi ?).
* aller dans la fenêtre de debug, partie sélection
des ROM_CALLs, sélectionner l'un d'entre eux
(_bcd_math par exemple).
* passer à un AMS 2.05 (testé: ROM dump de 89 avec
certificate).
* aller dans la fenêtre de debug: TIEmu est parti
dans le décor, je ne sais pas s'il exécute ou pas
roms
====
* MOVEA.W dis-assembled as MOVEA.L (HeapDeref)
* pressing Ctrl+Alt+Supp makes emu unresponsive. Press Ctrl again.
* CPU consumption may be high
folco
=====
* debugger crash when double-clicking stack value (http://yaronet.com/posts.php?s=115405)
-------------
+ done
- in progress
* to do...
This diff is collapsed.
This diff is collapsed.
Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
The file `configure.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.
Installation Names
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
CPU-COMPANY-SYSTEM
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Operation Controls
==================
`configure' recognizes the following options to control how it
operates.
`--cache-file=FILE'
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.
`--help'
Print a summary of the options to `configure', and exit.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`--version'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.
*----------------- XTiger ----------------------*
Original author of (X)tiger: Jonas Minnberg
Homepage for Tiger: http://www.nada.kth.se/~md94-jmi/tiger/
License: GPL
*------------------- UAE -----------------------*
Original author of UAE: Bernd Schmidt
Homepage for UAE: http://freiburg.linux.de/~uae/
License: GPL
*----------------- PedRom ----------------------*
Author: PpHd
Homepage: http://www.timetoteam.fr.st
License: GPL (version 2 or later)
Fully-GPL version by Kevin Kofler: <www.tigen.org/kevin.kofler/ti89prog/pedrom-ld-tigcc.zip>
--------------- GDB / Insight ------------------*
Copyright holder: Free Software Foundation
Homepage for GDB: http://sourceware.org/gdb/
Homepage for Insight: http://sourceware.org/insight/
License: GPL (version 2 or later)
-------------- Tcl / Tk / itcl -----------------*
Copyright holders: Regents of the University of
California, Sun Microsystems, Inc.,
Scriptics Corporation, ActiveState Corporation,
Cadence Design Systems, Inc. and other parties
Homepage: http://tcl.tk
License: Tcl/Tk License (GPL-compatible)
## Process this file with automake to produce Makefile.in
# subdirectories to scan
SUBDIRS = build glade help misc pedrom pixmaps po skins src
if USE_GROFF
SUBDIRS += man
endif
dist_pkgdata_DATA = COPYING RELEASE AUTHORS LICENSES
EXTRA_DIST = BUGS README.* TODO docs desktop sdk po/copy.bat po/TRANSLATORS install.bat
# install hook to install prebuilt Manpage.txt if groff is not available
install-data-local:
if !USE_GROFF
$(mkinstalldirs) $(DESTDIR)$(pkgdatadir)
$(INSTALL_DATA) $(srcdir)/man/Manpage.txt $(DESTDIR)$(pkgdatadir)/Manpage.txt
endif
# custom targets
install-without-tcl-tk:
if NO_GDB
$(MAKE) install DESTDIR="$(DESTDIR)"
else
if USE_GROFF
$(MAKE) install SUBDIRS="build glade help misc pedrom pixmaps skins man" DESTDIR="$(DESTDIR)"
else
$(MAKE) install SUBDIRS="build glade help misc pedrom pixmaps skins" DESTDIR="$(DESTDIR)"
endif
cd src && $(MAKE) install-without-tcl-tk DESTDIR="$(DESTDIR)"
endif
install-without-tcl-tk-itcl:
if NO_GDB
$(MAKE) install DESTDIR="$(DESTDIR)"
else
if USE_GROFF
$(MAKE) install SUBDIRS="build glade help misc pedrom pixmaps skins man" DESTDIR="$(DESTDIR)"
else
$(MAKE) install SUBDIRS="build glade help misc pedrom pixmaps skins" DESTDIR="$(DESTDIR)"
endif
cd src && $(MAKE) install-without-tcl-tk-itcl DESTDIR="$(DESTDIR)"
endif
regsvr:
cd src && $(MAKE) regsvr DESTDIR="$(DESTDIR)"
ACLOCAL_AMFLAGS = -I m4
This diff is collapsed.
See <http://lpg.ticalc.org/prj_tiemu>
\ No newline at end of file
*************
* TiEmu 3 *
*************
List of text files:
- AUTHORS: list of authors
- COPYING: license
- LICENSES: list of program included
- README.linux: specific linux instructions
- README.win32: specific windows instructions
- RELEASE: what's changed in this release
- TODO: work to do or planned
Texas Instruments and TI are trademarks of Texas Instruments Incorporated.
For more informations: <http://education.ti.com/educationportal/sites/US/nonProductSingle/global_trademarks.html>
This document has been written independantly of Texas Instruments.
\ No newline at end of file
*****************
* TiEmu *
* Linux version *
*****************
REQUIREMENTS
------------
- A UNIX computer (Intel x86 or PPC) and C compiler (gcc)
- X11 (X Window System)
- GTK+ 2.6 from <http://www.gtk.org>
- ticables2, tifiles2 and ticalcs2 libraries from the
TiLP 2 project <http://tilp.info>
INSTALLATION
------------
At first, you must have the ticables and ticalcs libraries installed. See
the documentation of these libraries for the installation procedure.
Untar the tiemu-X.XX.tar.gz archive (tar -xvzf), change directory to
tiemu directory.
Go the tiemu directory and type './configure' in order to be sure
that all it is OK. If you want to use KDE file dialogs, run
'./configure --with-kde' instead.
Next, type 'make' to make a binary for your machine.
If you want does not want to use GDB as debugger or use the odl one (tiemu2),
run './configure --disable-gdb'.
If the compile suceeds without any errors, you can type 'make install' to
install the binary in /usr/local/bin. This will also copy some necessary
files to /usr/local/share/tiemu and will install the manpage and the
help.
If you already have some TiEmu images, you will have to manually copy them
to the /usr/locale/share/tiemu/images directory.
USAGE
-----
Type 'tiemu' for using it. TiEmu accepts some command line parameters.
Do 'tiemu --help' or read the manpage by 'man tiemu'.
AVAILABILITY
------------
http://lpg.ticalc.org/prj_tiemu/index.html
COPYRIGHT
---------
TiEmu is Copyright (C) 2000-2009 by the TiEmu team <tiemu-users@lists.sf.net>
Copying is allowed under the terms of GNU General Public License (LGPL).
See the file COPYING for more details.
---------------------------------------------------------------------------
Please report any bugs, questions, ... (please give us your platform, your
calculator type (with ROM version) and your link cable model).
The TiEmu team <tiemu-users@lists.sf.net>
*****************
* TiEmu *