Debian packaging utilities for Truecrypt source helps to get Truecrypt running with a minimum of effort under Debian-based Linux systems (Debian and Ubuntu are officially supported). Truecrypt is an open source disk encryption software which uses a concept of containers to store encrypted data. The containers (or volumes) can be read transparently under Linux and Windows. The utilities create installable *.deb packages from the sources and those debs can be used in turn to install the encryption software.
GCC-MELT is a high-level domain specific language that eases the development of plugin-like extensions for GCC, the Gnu Compiler Collection. These extensions can analyze or modify GCC internal representations, and can be used for static source code analysis, refactoring, specific warnings, optimizations, etc. The MELT language provides high-level features. Notably, MELT code is translated to C or C++, and can even contain C or C++ code. It includes powerful pattern matching facilities and can manipulate dynamically typed values and raw GCC structures. It enables functional/applicative, object-oriented, reflective programming styles and has a familiar Lisp-like syntax.
The GNU Modula-2 compiler is one of a number of front end languages to GCC (the GNU Compiler Collection). As such, it has been designed to coexist with other GCC languages. For example, it can be used in mixed language projects and it can catch C++ exceptions and throw exceptions which can be caught by C++. Users can also exploit conditional compilation and full gcc backend optimization and architecture coverage. GNU Modula-2 can produce position independent code and can easily produce shared libraries from modules. The compiler provides a swig interface file generator option, which allows scripting languages such as Python to import modules written in Modula-2 and also catch exceptions thrown by Modula-2. The compiler translates PIM2, PIM3, PIM4, and ISO dialects of Modula-2.
Generic Makefile for C Projects is a generic makefile that builds a binary from C source code files. Any number of build modes are supported - Release and Debug are predefined. The CFlags and LFlags variables can be defined in a mode dependent way, i.e. CFlags_Debug. File dependencies are generated by the compiler (-MMD flag for preconfigured GNU compiler) and included by the makefile automatically. All output is written under a single target directory. It supports source files with the same name that are located in different directories. You can use wildcards to add any number of source files.
JCGO (pronounced as "j-c-go") translates (converts) programs written in Java into platform-independent C code that can be compiled (by third-party tools) into highly-optimized native code for the target platform. JCGO is a powerful solution that enables your desktop, server-side, embedded, mobile, and wireless Java applications to take full advantage of the underlying hardware. In addition, JCGO makes your programs, when compiled to native code, as hard to reverse engineer as if they were written in C/C++. The JCGO translator uses some optimization algorithms that allow, together with optimizations performed by a C compiler, the resulting executable code to reach better performance compared with the traditional Java implementations (based on the Just-In-Time technology). The produced executable does not contain nor require a Java Virtual Machine to execute, so its resource requirements are smaller than that required by a typical Java VM. This also simplifies the process of deployment and distribution of an application.
SDLbits is a very lightweight SDL wrapper for Java. This library was designed to be very small and simple. It does not use Swig, but goes directly from "native" Java definitions to the sdlbits C wrapper library to SDL or OpenGL (in C). All symbols are exposed as they would be in C, except the "SDL_" prefix has been removed, since all names are inside the SDL class. The SDL structures from C are translated to very simple Java classes, such as SDL.VideoInfo. Most fields are exposed as read-only "get" methods, but "set" methods for writable members are supported as well. These classes simply interface to the actual C data with a ByteBuffer "pointer".