From: kbongers Date: Mon, 2 Jul 2001 06:02:34 +0000 (+0000) Subject: go to single .html X-Git-Url: https://git.gag.com/?a=commitdiff_plain;h=a935c26bf201705b353d7262328bd6e35c1b9816;p=fw%2Fsdcc go to single .html git-svn-id: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk/sdcc@991 4a8a32a2-be11-0410-ad9d-d568d2c75423 --- diff --git a/doc/SDCCUdoc-2.html b/doc/SDCCUdoc-2.html deleted file mode 100644 index 5820d30c..00000000 --- a/doc/SDCCUdoc-2.html +++ /dev/null @@ -1,267 +0,0 @@ - - - - - SDCC Compiler User Guide: Installation - - - - - -Next -Previous -Contents -
-

2. Installation

- -

What you need before you start installation of SDCC ? A C Compiler, not -just any C Compiler, gcc to be exact, you can get adventurous and try another -compiler , I HAVEN'T tried it. GCC is free , and is available for almost all -major platforms, if you are using linux you probably already have it, if you -are using Windows 95/NT go to www.cygnus.com and download CYGWIN32 you will -need the full development version of their tool (full.exe), follow their instructions -for installation (this is also free and is very easy to install), Windows 95/NT -users be aware that the compiler runs substantially slower on the Windows platform, -I am not sure why. -

After you have installed gcc you are ready to build the compiler (sorry -no binary distributions yet). SDCC is native to Linux but can be ported to -any platform on which GCC is available . Extract the source file package (.zip -or .tar.gz) into some directory , which we shall refer to as SDCCDIR from now -on. -

2.1 Components of SDCC -

- -

gc ( a conservative garbage collector)

- -

SDCC relies on this component to do all the memory management, this excellent -package is copyrighted by Jans J Boehm(boehm@sgi.com) and Alan J Demers but -can be used with minimum restrictions. The GC source will be extracted into -the directory SDCCDIR/gc. -

cpp ( C-Preprocessor)

- -

The preprocessor is extracted into the directory SDCCDIR/cpp, it is a modified -version of the GNU preprocessor. -

asxxxx & aslink ( The assembler and Linkage Editor)

- -

This is retargettable assembler & linkage editor, it was developed -by Alan Baldwin, John Hartman created the version for 8051, and I (Sandeep) -have some enhancements and bug fixes for it to work properly with the SDCC. -This component is extracted into the directory SDCCDIR/asxxxx. -

SDCC - The compiler.

- -

This is the actual compiler, it uses gc and invokes the assembler and linkage -editor. All files with the prefix SDCC are part of the compiler and is extracted -into the the directory SDCCDIR. -

S51 - Simulator

- -

Version 2.1.8 onwards contains s51 a freeware , opensource simulator developed -by Daniel Drotos <drdani@mazsola.iit.uni-miskolc.hu>. The executable -is built as part of build process, for more information visit Daniel's website -at <http://mazsola.iit.uni-miskolc.hu/~drdani/embedded/s51/>. -

SDCDB - Source level Debugger.

- -

SDCDB is the companion source level debugger . The current version of the -debugger uses Daniel's Simulator S51, but can be easily changed to use other -simulators. -

2.2 Installation for Version <= 2.1.7 -

- -

After the package is extracted (Windows 95/NT users start CYGWIN shell), -change to the directory where you extracted the package and give the command. -

-

-./sdccbuild.sh
- 
-
-

This is a bash shell script, it will compile all the above mentioned components -and install the executables into the directory SDCCDIR/bin make sure you add -this directory to your PATH environment variable. This script will also compile -all the support routines ( library routines ) using SDCC. The support routines -are all developed in C and need to be compiled. -

2.3 Installation for Version >= 2.1.8a -

- -

The distribution method from Version 2.1.8a has been changed to be conforment -with the "autoconf" utility. The source is now distributed as sdcc-<version -number>.tar.gz format , instead of the older .zip format. The steps for -installation are as follows. -

Unpack the sources.

- -

This is usually done by the following command "gunzip -c sdcc-<version -number>.tar.gz | tar -xv -" -

Change to the main source directory (usually sdcc or sdcc-<version number>)

- -

Issue command to configure your system

- -

The configure command has several options the most commonly used option -is --prefix=<directory name>, where <directory name> is the final -location for the sdcc executables and libraries, (default location is /usr/local). -The installation process will create the following directory structure under -the <directory name> specified. -

-

-bin/ - binary exectables (add to PATH environment variable) 
-share/ 
-      sdcc51inc/
- - include header files 
-      sdcc51lib/ - 
-             small/ - Object &
- Library files for small model library 
-             large/ - Object & library
- files for large model library
- 
-
-

The command -

'./configure --prefix=/usr/local" -

will create configure the compiler to be installed in directory /usr/local/bin. -

make

- -

After configuration step issue the command -

"make" -

This will compile the compiler -

"make install"

- -

Will install the compiler and libraries in the appropriate directories. -

Special Notes for Windows Users. Provided by Michael Jamet[ mjamet@computer.org]

- -

-

How to install SDCC from source on a Windows 95 or Windows NT 4 system -

-

-

This document describes how to install SDCC on a Win 95 or Win NT 4 system. -

-

These instructions probably work for Win 98 as well, but have not been -

-

tested on that platform. -

-

There are lots of little differences between UNIX and the Win32 Cygnus -

-

environment which make porting more difficult than it should be. If -

-

you want the details, please contact me. Otherwise just follow these -

-

instructions. -

-

1. Install the Cygnus Software -

Go to http://sourceware.cygnus.com/cygwin. Cygnus provides a UNIX like -

-

environment for Win 32 systems. Download "full.exe" and -install. You -

MUST install it on your C drive. "full.exe" contains a shell -AND many -

common UNIX utilities. -

-

2. Download and Extract the Latest SDCC -

The latest version can be found at -

www.geocities.com/ResearchTriange/Forum/1353. -

It can be uncompressed with winzip. -

-

3. Start a Cygnus Shell -

There should be an entry in the Start Menu for Cygnus. Invoke the shell. -

-

This gives you a UNIX like environment. FROM THIS POINT ON, DIRECTORIES -

-

MUST BE SPECIFIED WITH FORWARD SLASHES (/) NOT THE DOS STYLE BACK -

SLASHES (\) BECAUSE THIS IS WHAT UNIX EXPECTS. - -

ex. "\winnt" would be "/winnt" under the -shell. -

-

4. Change Directory to Where SDCC was extracted (referred to as INSTALLDIR) -

-

-

ex. cd /sdcc218Da. If you extracted to a drive OTHER THAN C, the drive -

-

must be specified as part of the path. For example, if you extracted -to -

your "g drive", type the following: "cd //g/mydir". -You must use "//" -

to specify the drive. -

-

5. Make Dirs Which are Automatically Made During the UNIX Installation -

-

From the INSTALLDIR, -

-

mkdir -p bin (not a typo, just "bin") -

mkdir -p /bin -

mkdir -p /usr/local/bin -

mkdir -p /usr/local/share -

mkdir -p /usr/local/share/sdcc51lib -

mkdir -p /usr/local/share/sdcc51inc -

mkdir -p /tmp -

-

(When a path from the root directory is specified WITHOUT a drive, the -

-

drive defaults to c. For example /michael/newuser => c:\michael\newuser) -

-

-

6. Add Programs to /bin Expected by the Installation Process -

- Look at your path: echo $PATH -

One of the fields is the diretory with the CYGNUS programs. -

ex. /CYGNUS/CYGWIN~1/H-I586/BIN -

-

- cd to the directory found above. You may have to fiddle with the -

-

case (upper or lower) here because the PATH is SHOWN as all upper -

-

case, but is actually mixed. To help you along, you may type -

a letter or 2 followed by the escape key. The shell will fill -

out the remaining letters IF THEY describe a unique directory. -

If you have problems here, cd one directory and type "ls". -"ls" -

is the equivalent of "dir/w". -

-

- Copy the following: -

cp sh.exe /bin -

cp pwd.exe /bin -

cp echo.exe /bin -

-

7. Go back to the INSTALLDIR -

cd INSTALLDIR -

ex. cd //d/sdcc218Da -

-

8. Run the configure Program -

./configure -

The "./" is important because your current directory is NOT -in your path. -

Under DOS, your current directory was implicitly always the first entry -

-

in your path. -

-

9. Run make -

make -

-

This process takes quite some time under Win 32. -

-

10. Install the Newly Built Software -

make install -

-

This will partially install the software into the /usr/local directories -

-

created in step 5. What it actually doing is copying the .c, .h and -

-

library files to directories under /usr/local/share. -

-

It will NOT be able to install the actual programs (binaries) because -

-

it does not know programs on Win32 systems have ".exe" extensions. -

-

For example, it tries to install sdcc instead of sdcc.exe. -

-

After the automated part is finished, you must manually copy the binaries: -

-

cd bin (This is the bin directory in your INSTALLDIR) -

cp * /usr/local/bin -

-

11. Make sure /usr/local/bin is in Your PATH -

You may add c:\usr\local\bin to your path however your -Win32 system allows. For -

example you may add it to the PATH statement in autoexec.bat. -

-

Good luck. If you have any questions send them to me or post them -

to the list. -

-Next -Previous -Contents - - diff --git a/doc/SDCCUdoc-3.html b/doc/SDCCUdoc-3.html deleted file mode 100644 index ef2fc5b9..00000000 --- a/doc/SDCCUdoc-3.html +++ /dev/null @@ -1,100 +0,0 @@ - - - - - SDCC Compiler User Guide: Compiling. - - - - - -Next -Previous -Contents -
-

3. Compiling.

- -

3.1 Single Source file projects. -

- -

For single source file projects the process is very simple. Compile your -programs with the following command -

-

-sdcc sourcefile.c
- 
-
-

The above command will compile ,assemble and link your source file. Output -files are as follows. -

-

-

3.2 Projects with multiple source files. -

- -

SDCC can compile only ONE file at a time. Let us for example assume that -you have a project containing the following files. -

-

-foo1.c ( contains some functions )foo2.c (contains some more functions)foomain.c (contains more functions and the function main)
- 
-
-

The first two files will need to be compiled separately with the commands -

-

-sdcc -c foo1.csdcc -c foo2.c
- 
-
-

Then compile the source file containing main and link the other files together -with the following command. -

-

-sdcc foomain.c foo1.rel foo2.rel
- 
-
-

Alternatively foomain.c can be separately compiled as well -

-

-sdcc -c foomain.c sdcc foomain.rel foo1.rel foo2.rel
- 
-
-

The file containing the main function MUST be the FIRST file specified -in the command line , since the linkage editor processes file in the order -they are presented to it. -

3.3 Projects with additional libraries. -

- -

Some reusable routines may be compiled into a library, see the documentation -for the assembler and linkage editor in the directory SDCCDIR/asxxxx/asxhtm.htm -this describes how to create a .lib library file, the libraries created in -this manner may be included using the command line, make sure you include the --L <library-path> option to tell the linker where to look for these files. -Here is an example, assuming you have the source file 'foomain.c' and a library -'foolib.lib' in the directory 'mylib'. -

-

-sdcc foomain.c foolib.lib -L mylib
- 
-
-

Note here that 'mylib' must be an absolute path name. -

The view of the way the linkage editor processes the library files, it -is recommended that you put each source routine in a separate file and combine -them using the .lib file. For an example see the standard library file 'libsdcc.lib' -in the directory SDCCDIR/sdcc51lib. -

-Next -Previous -Contents - - diff --git a/doc/SDCCUdoc-4.html b/doc/SDCCUdoc-4.html deleted file mode 100644 index 92f8bbe1..00000000 --- a/doc/SDCCUdoc-4.html +++ /dev/null @@ -1,263 +0,0 @@ - - - - - SDCC Compiler User Guide: Command Line options - - - - - -Next -Previous -Contents -
-

4. Command Line options

- -

-

-

The following options are provided for the purpose of retargetting and -debugging the compiler . These provided a means to dump the intermediate code -(iCode) generated by the compiler in human readable form at various stages -of the compilation process. -

-

-

Note that the files created for the dump are appended to each time. So -the files should be deleted manually , before each dump is created. -

When reporting bugs, it will be very helpful if you could include these -dumps along with the portion of the code that is causing the problem. -

-Next -Previous -Contents - -