grischka e5eedc0cda Revert "tcc.h: Extend search path for include, lib and crt"
This reverts commit 2507c71704.

Why crowd up search-paths for the normal native compiler with
all sort of invalid stuff.  Why -UCONFIG_TRIPLET if it isn't
set at all for cross-compilers.  Also, the patch still didn't
do anything useful "out of the box".

Instead I'd suggest to do something more simple and more effective.
See Makefile:
- set search paths for cross-compilers to /usr/<triplet> by default
- Install any built "xxx-tcc" and "xxx-libtcc1.a", even if not listed
  with PROGS_CROSS/LIBTCC1_CROSS
- Support ELF-<target> = ... to set the elf interpreter

Some common gnu-triplets are supported by default
  TRIPLET-i386 ?= i386-linux-gnu
  TRIPLET-x86_64 ?= x86_64-linux-gnu
  TRIPLET-arm ?= arm-linux-gnueabihf
  TRIPLET-arm64 ?= aarch64-linux-gnu
  TRIPLET-riscv64 ?= riscv64-linux-gnu

Other triplets can be given explicitly, for example like this:
  $ make cross-arm-eabi TRIPLET-arm-eabi=arm-linux-gnueabi
  $ sudo make install
2022-09-24 10:09:12 +02:00
2022-07-24 09:51:32 +02:00
2022-07-24 09:51:32 +02:00
2022-05-09 22:19:15 +02:00
2022-08-16 17:54:42 +02:00
2022-07-24 09:44:50 +02:00
2022-05-09 22:19:15 +02:00
2022-07-24 09:44:50 +02:00
2022-07-24 09:44:50 +02:00
2021-02-13 01:03:41 +01:00
2022-05-09 22:37:25 +02:00
2017-09-24 18:57:48 +02:00
2017-05-07 21:38:09 -07:00
2022-09-24 02:33:46 +02:00
2022-07-24 09:51:32 +02:00
2003-05-24 14:18:56 +00:00
2022-05-05 09:10:37 +02:00
2022-07-24 09:44:50 +02:00
2022-08-16 15:59:41 +02:00
2022-08-16 15:59:41 +02:00
2022-05-05 09:10:37 +02:00
2022-07-24 09:44:50 +02:00
2022-08-16 15:59:41 +02:00
2017-05-07 21:38:09 -07:00
2022-07-24 09:44:50 +02:00
2020-12-20 10:50:07 +01:00
2021-04-27 11:56:43 +02:00
2022-06-07 20:53:14 +02:00
2022-05-05 09:10:37 +02:00
2022-07-24 09:44:50 +02:00
2022-06-07 20:53:14 +02:00
2022-05-09 22:19:15 +02:00
2022-08-16 15:59:41 +02:00
2022-07-24 09:30:41 +02:00
2022-07-24 09:45:48 +02:00
2022-07-24 09:51:32 +02:00
2017-04-29 22:09:10 +02:00
2020-07-11 20:00:37 +02:00
2017-02-08 19:56:15 +01:00
2022-08-16 15:59:41 +02:00
2022-07-24 09:44:50 +02:00

Tiny C Compiler - C Scripting Everywhere - The Smallest ANSI C compiler
-----------------------------------------------------------------------

Features:
--------

- SMALL! You can compile and execute C code everywhere, for example on
  rescue disks.

- FAST! tcc generates optimized x86 code. No byte code
  overhead. Compile, assemble and link about 7 times faster than 'gcc
  -O0'.

- UNLIMITED! Any C dynamic library can be used directly. TCC is
  heading toward full ISOC99 compliance. TCC can of course compile
  itself.

- SAFE! tcc includes an optional memory and bound checker. Bound
  checked code can be mixed freely with standard code.

- Compile and execute C source directly. No linking or assembly
  necessary. Full C preprocessor included.

- C script supported : just add '#!/usr/local/bin/tcc -run' at the first
  line of your C source, and execute it directly from the command
  line.

Documentation:
-------------

1) Installation on a i386/x86_64/arm/aarch64/riscv64
   Linux/macOS/FreeBSD/NetBSD/OpenBSD hosts.

   ./configure
   make
   make test
   make install

   Notes: For FreeBSD, NetBSD and OpenBSD, gmake should be used instead of make.
   For Windows read tcc-win32.txt.

makeinfo must be installed to compile the doc.  By default, tcc is
installed in /usr/local/bin.  ./configure --help  shows configuration
options.


2) Introduction

We assume here that you know ANSI C. Look at the example ex1.c to know
what the programs look like.

The include file <tcclib.h> can be used if you want a small basic libc
include support (especially useful for floppy disks). Of course, you
can also use standard headers, although they are slower to compile.

You can begin your C script with '#!/usr/local/bin/tcc -run' on the first
line and set its execute bits (chmod a+x your_script). Then, you can
launch the C code as a shell or perl script :-) The command line
arguments are put in 'argc' and 'argv' of the main functions, as in
ANSI C.

3) Examples

ex1.c: simplest example (hello world). Can also be launched directly
as a script: './ex1.c'.

ex2.c: more complicated example: find a number with the four
operations given a list of numbers (benchmark).

ex3.c: compute fibonacci numbers (benchmark).

ex4.c: more complicated: X11 program. Very complicated test in fact
because standard headers are being used ! As for ex1.c, can also be launched
directly as a script: './ex4.c'.

ex5.c: 'hello world' with standard glibc headers.

tcc.c: TCC can of course compile itself. Used to check the code
generator.

tcctest.c: auto test for TCC which tests many subtle possible bugs. Used
when doing 'make test'.

4) Full Documentation

Please read tcc-doc.html to have all the features of TCC.

Additional information is available for the Windows port in tcc-win32.txt.

License:
-------

TCC is distributed under the GNU Lesser General Public License (see
COPYING file).

Fabrice Bellard.
Languages
C 96.8%
Assembly 1%
Makefile 1%
C++ 0.5%
Prolog 0.3%
Other 0.4%