Tiny C Compiler is perhaps the smallest ANSI C compiler, by Fabrice Bellard.
- It is small: you can compile and execute C code everywhere, for example
on rescue disks;
- It is fast! TCC generates optimized x86 code. No byte code overhead.
Compile, assemble, and link about 7 times faster than 'gcc -O0';
- Any C dynamic library can be used directly. TCC is heading towards
full ISO C99 compliance. TCC can of course compile itself;
- It is safe! TCC includes 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 is
necessary. Full C preprocessor included;
- C script supported: just add '#!/bin/env tcc -run' at the first line
of your C source, and execute it directly from the command line.
===> The following configuration options are available for tcc-0.9.26_7:
DOCS=on: Build and/or install documentation
EXAMPLES=on: Build and/or install examples
===> Use 'make config' to modify these settings
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Install texinfo files (GNU info) into ${PREFIX}/share/info
After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.
Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.
Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them
Bump revision of all impacted ports
PR: 232907
exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D17816
Github cleanup.
- Use the version tag instead of commit hash when they're the same.
- Remove unnneeded variables.
- Simplify go- ports when possible.
- Various fixes.
Sponsored by: Absolight
- Fetch from GITHUB
- Update MAINTAINER to my @FreeBSD.org address
- Fix tcc-doc.html generation
- Remove CONFLICTS because TenDRA port was deprecated some time ago
- Use post-install-DOCS-on target
- Use post-install-EXAMPLES-on target
- Bump PORTREVISION
Reviewed by: amdmi3, junovitch (mentors)
Approved by: amdmi3, junovitch (mentors)
Differential Revision: D6314
- Fix plist
- Add INFO macro and USES=makeinfo to make it also work on revent head
- Clean up Makefile
PR: 192137
Submitted by: Carlos Jacobo Puga Medina <cjpugmed@gmail.com> (maintainer)
Update files/README.tccelf files/patch-libtcc.c to reflect some
fixes i made recently.
Add files/patch-z1-preproc which implements -include, -M and some
related preprocessing macros to improve portability
Bump portrevision accordingly
Should close PR/141185
Tiny C Compiler
Features:
* SMALL! You can compile and execute C code everywhere, for example on rescue
disks (about 100KB for x86 TCC executable, including C preprocessor,
C compiler, assembler and linker).
* FAST! tcc generates x86 code. No byte code overhead. Compile, assemble and
link several times faster than GCC.
* UNLIMITED! Any C dynamic library can be used directly. TCC is heading torward
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 and GNU-like assembler 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.
* With libtcc, you can use TCC as a backend for dynamic code generation.
WWW: http://bellard.org/tcc/
A new port for TinyCC, a small and fast C compiler.
Tcc's features include:
* Small: You can compile and execute C code everywhere, for
example on rescue disks (about 100KB for x86 TCC executable,
including C preprocessor, C compiler, assembler and linker).
* Fast: tcc generates optimized x86 code. No byte code overhead.
Compile, assemble and link several times faster than GCC.
* Unlimited: Any C dynamic library can be used directly. TCC is
heading torward 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 and GNU-like assembler 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.
* With libtcc, you can use TCC as a backend for dynamic code
generation.
