Free various windows platforms software for linux

SIMD Cross-platform headers is a cross- platform, cross-compiler, cross CPU C/C++ header collection that aids the creation portable vectorized (SIMD) C/C++ code.
SIMD Cross-platform headerst supports (or partially supports) x86 (MMX/SSE/SSE2) GCC and MSVC, PPC Altivec GCC and CodeWarrior, ARM GCC, and software-emulated SIMD.
NOTE: Code must be 16-byte aligned. Align to 16 when allocating memory.
X86/XSCALE (Intel) vs. PowerPC/MIPS
While the PowerPC and MIPS SIMD instructions take 2 source vectors and a destination vector, the Intel platforms only take a source and destination. Example:
PPC/MIPS can do:
C = A + B
X86 can only do:
A = A + B (or A+=B)
Code written either way will work on the X86, and still be faster than 387 math, but preserving the registers takes significant overhead (Disassemble the test program for an example. The prints preserve, the disassembly test does not.) For the fastest code between systems, write your SIMD math as the X86 expects, manually preserving SIMD variables.
At least GCC for PPC doesnt seem to have any issues figuring out how to deal with a source and destination memory address being the same.
Enhancements:
- Created file with some i386, GCC dialect

Cross Platform Toolkit Library (xtklib) is a C++ based framework for highly object-oriented cross-platform programming.
In particular, the library provides a full abstraction layer between its API and the main services offered by the underlying operating system(Thread, processes,GUI,Filesystem,etc.) plus a set of generic utilities (Strings,Data structures,etc.).
Unlike other famous libraries, xtklib makes full use of all features of C++ like RTTI, Templates, Exceptions thus obtaining a strongly object-oriented design with a Java-like sensation.
The library is composed by two main modules: "Base" and "Widgets". The target operating systems are Windows and Unix(Linux and BSD in primis) with a plan to move also towards other systems.
Main features:
- Use of modern C++ - use of many powerfull features offered by modern C++ like exceptions,RTTI,templates and namespaces allows faster development,improves code readability,and reduces programming errors.
- Strong Object-Oriented design - designed to meet requirements of modern software industry: modularity, low coupling, high cohesion,information hiding. Design patterns and advanced class hierarchies are extensively used in all the library.
- Ease of use - Clean and intuitive programming interface with a Java-like sensation.
- Complete - Features supported includes:
- Basic services: Thread, Synchronization, Filesystem access, Processes, Networking.
- Advanced services: I/O Streams, Logging.
- Debugging tools: Stack tracing, Memory Leak detection.
- Gui widgets (Work in progress): Windows,Frames,Layout managers,common controls,advanced controls.
- Generic utilities: complete data structures framework, String class with unicode support.
- Full unicode support: native support to unicode, conversion to/from different charsets.
- And many others: the list is too much long to enumerate all minor but extremely usefull features.
- Cross Platform - Supports various systems and compilers.
- XTKlib is known to work under:
- Windows XP (x86)
- Visual C++ versions 7.1, 8.0
- MinGW32
- Linux (x86, x86_64)
- GCC 3.4
- Compatibility with other platforms and compilers are not excluded.(If you can compile/use xtklib with a non listed compiler/platform let us know about that, thanks)
- Fast - Although performance are not the main goal of this library (exceptions and RTTI have a tradeoff in this meaning), code agility and execution speed are often taken in consideration during development, thus leaving a performance advantage compared to interpreted programming languages(eg. Java,C#) or scripting languages(eg. Python,Ruby,Perl).
Enhancements:
- This is the first release with a working "Widgets" module, although it has only basic features.
- This release is provided for testing and development only.

Apache Hello World Benchmarks is a benchmarking tool that seeks to give a sense of Web application execution speed on various software platforms running under the Apache Web server.

Benchmarks can vary greatly from system to system, so this tool allows one to get numbers on ones own platform. Applications tested include mod_perl, mod_php, Tomcat, and Apache::ASP, with over 62 benchmarks in all.

Benchmark Descriptions:

Hello World 2000 ( 2000 )

The 2000 benchmark tries to emulate a heavy web page template. It is typically 3K+ in program length that results in output of over 20K. While this does not properly reflect any web applications speed of back end business logic execution, it does show a template heavy request with some application logic and loops, some HTTP parameter passing, and much variable interpolation in the output stream.

Hello World ( hello )

The Hello World benchmark merely prints "Hello World" and as such is a good test for the fastest a web page could ever run under the given web application environment. For historical reasons, the benchmarks are written to print "Hello" and then add to the output World as a raw string.

HelloDB ( hellodb )

The HelloDB benchmark merely queries the database for the string "Hello World", and as such represents the fastest a web application can process a request when talking to a database. This is a new benchmark with only MySQL supported for now, but more environments and databases will be added over time.

XSLT Big ( xsltbig )

This benchmark hits an XSLT rendering engine hard with 18K+ XML being transformed with a 1K+ XSL stylesheet for over 20K output. Though XSLT is generally slow, many applications will use XSLT caching to speed up response times. This benchmark should emulate well a real world XSLT usage scenario, with perhaps the XSL itself being too trivial.

Hello XSLT ( xslt )

Like the Hello World benchmark, the XSLT version just outputs "Hello World", or the closest we can get when doing XSLT, so it too demonstrates the fastest an application can render a page with XSLT. Benchmarks should be similarly configured between xsltbig and xslt, so a slow caching layer that benefits the former might slow down this benchmark.

OSSP sa is an abstraction library for the Unix socket application programming interface (API) featuring stream and datagram oriented communication over Unix Domain and Internet Domain (TCP and UDP) sockets.
It provides the following key features: address abstraction (local, IPv4, and IPv6), type abstraction, I/O timeouts, I/O stream buffering and convenience I/O functions.
Main features:
Stand-Alone, Self-Contained, Embeddable
- Although there are various Open Source libraries available which provide a similar abstraction approach, they all either lack important features or unfortunately depend on other companion libraries. OSSP sa fills this gap by providing all important features (see following points) as a stand-alone and fully self-contained library. This way OSSP sa can be trivially embedded as a sub-library into other libraries. It especially provides additional support for namespace-safe embedding of its API in order to avoid symbol conflicts.
Address Abstraction
- Most of the ugliness in the Unix Socket API is the necessity to have to deal with the various address structures (struct sockaddr_xx) which exist because of both the different communication types and addressing schemes. OSSP sa fully hides this by providing an abstract and opaque address type (sa_addr_t) together with utility functions which allow one to convert from the traditional struct sockaddr or URI specification to the sa_addr_t and vice versa without having to deal with special cases related to the underlying particular struct sockaddr_xx. OSSP sa support Unix Domain and both IPv4 and IPv6 Internet Domain addressing.
Type Abstraction
- Some other subtle details in the Unix Socket API make the life hard in practice: socklen_t and ssize_t. These two types originally were (and on some platforms still are) plain integers or unsigned integers while POSIX later introduced own types for them (and even revised these types after some time again). This is nasty, because for 100% type-correct API usage (especially important on 64-bit machines where pointers to different integer types make trouble), every application has to check whether the newer types exists, and if not provide own definitions which map to the still actually used integer type on the underlying platform. OSSP sa hides most of this in its API and for socklen_t provides a backward-compatibility definition. Instead of ssize_t it can use size_t because OSSP sa does not use traditional Unix return code semantics.
I/O Timeouts
- Each I/O function in OSSP sa is aware of timeouts (set by sa_timeout(3)), i.e., all I/O operations return SA_ERR_TMT if the timeout expired before the I/O operation was able to succeed. This allows one to easily program less-blocking network services. OSSP sa internally implements these timeouts either through the SO_{SND,RCV}TIMEO feature on more modern Socket implementations or through traditional select(2). This way high performance is achieved on modern platforms while the full functionality still is available on older platforms.
I/O Stream Buffering
- If OSSP sa is used for stream communication, internally all I/O operations can be performed through input and/or output buffers (set by sa_buffer(3)) for achieving higher I/O performance by doing I/O operations on larger aggregated messages and with less required system calls. Additionally if OSSP sa is used for stream communication, for convenience reasons line-oriented reading (sa_readln(3)) and formatted writing (see sa_writef(3)) is provided, modelled after STDIOs fgets(3) and fprintf(3). Both features fully leverage from the I/O buffering.
Enhancements:
- Removed SA_SYSCALL_GETHOSTBYNAME because gethostbyname(3) cannot be overridden as at is use point (function sa_addr_u2a) the sa_t object is not available.
- Additionally, for IPv6 getaddrinfo(3) would have been overridden, too.
- This fixed compilation on platforms without IPv6 APIs.

Ivy is a simple protocol and a set of open-source libraries and programs that allows applications to broadcast information through text messages, with a subscription mechanism based on regular expressions.
Ivy libraries are available in C, C++, Java and Perl, on Windows and Unix boxes and on Macs. Several Ivy utilities and hardware drivers are available too.
Ivy is currently used in research projects in the air traffic control and human-computer interaction research communities as well as in commercial products. It is also taught to CS students.
Ivy is a CENA product.
Main features:
- Ivy is not based on a centralised server. Actually, Ivy is mostly a communication convention, implemented through a collection of libraries for various languages and platforms. The current version of the Ivy protocol is version 3, which has been stable for the last 3 years.
- Language bindings are available in C (Unix and Windows), C++ (Mac, Unix, Windows), Java and Perl. There have been successful uses through the C library
- Messages are formatted in text, and subscriptions are based on regular expressions. Plans to move to an XML-based subscription language are on their way.
- From the programmers point of view, Ivy is an information broadcasting channel. The main functions are:
- connecting to a bus. Example: IvyInit (b, "192.126:2011")
- sending a message. Example: IvySend (b, "HELLO %s", world)
- binding a message pattern to a callback function. Example: IvyBind (b, "HELLO (.*)", cb)
- the main loop. Example : IvyLoop ()
- Subscriptions are managed on the emitters side, which limits the actual network traffic.
- Direct point-to-point messages are also available.
- Ivy was designed by a research group in Human-Computer Interaction, with the goals of connecting applications written on different toolkits/languages/platforms (such as an OpenGL application on a SGI connected to a PerlTk application on a Linux box), while keeping it simple: no server to be lauched and supervised, a simplistic API, and a communication model compatible with classical event-based GUI progamming. We think we have somewhat reached our goal...
Enhancements:
- This release mostly contains bugfixes and code cleanup.

ioquake3 project (or ioq3 for short) aims to build upon id Softwares Quake 3 source code release. The source code was released on August 20, 2005 under the GPL. Since then, we have been cleaning up, fixing bugs, and adding features.

Our permanent goal is to create the open source Quake 3 distribution upon which people base their games and projects. We also seek to have the perfect version of the engine for playing Quake 3: Arena, Team Arena, and all popular mods.

This distribution of the engine has been ported to many new platforms and has had a slew of new features added, along with massive bug extermination. While we dont have PunkBuster (and never will), we do have more security for servers and clients from various bugfixes which arent in ids client.