Difference between revisions of "Category/Program-build-automation"
(inserting Category-page template -- User:jgay)
|Line 1:||Line 1:|
Latest revision as of 13:25, 6 July 2011
Broaden your selection:
- ACDK is a development framework with a similar target of Microsoft's .NET or Sun's ONE platform, but instead of using Basic/C# or Java as programming language, it bases C++ as core implementation language. ACDK implements the standard library packages, including acdk::lang, acdk::lang::reflect, acdk::util, acdk::io, acdk::text (including regexpr), acdk::net, acdk::sql, acdk::xml and more, as well as technologies like flexible Allocator/Garbage Collection, Threading and Unicode. With the extensions of ACDK C++ objects are available for reflection, serialization, aspect oriented class attributes and [D]ynamic [M]ethod [I]nvocation. This DMI act as an universal object oriented call interface to connect C++ with scripting languages (Java, Perl, Tcl, Python, Lisp, Visual Basic, VBScript) and standard component technologies (CORBA, COM+).
- The Aap program executes recipes. It is a kind of super-make program. In a recipe you describe how to perform a certain task. Like a Makefile it contains dependencies and build commands. Additionally, many powerful features are included, so that you can use a recipe to:
- Build a program by just specifying the program name and the source files
- Maintain a web site (the A-A-P site is generated and uploaded with a recipe)
- Download the latest version of files
- Distribute files to several servers at once
- Obtain a module from CVS
- Commit changes to CVS; add and remove files automatically
- Generate and filter files
- Build several variants and on multiple platforms with little effort
- The A-A-P GUI IDE is a framework in which separate tools can work together. Like any other Integrated Development Environment it supports:
- Creating a project
- Building and executing a program
- Browsing files
- Debugging a program while displaying source code
- Framework Agide is not a monolitic application. Separate tools can be plugged in. Thus you are not forced to use one editor. Each tool implements part of the plugin interface. This interface makes it possible for a tool to communicate with other tools, without the need to know how the other tools work. For example, an editor can set a breakpoint in a file, without knowing what kind of debugger is being used. And the debugger can show the PC position in a source file, without knowing what editor is being used.
- Alexis Makes (amake)
- AMake is a make tool which uses powerful pattern transformation enabling a single makefile to automatically handle the compilation of any level of directory hierachy and have the possibility to add files in a project without having to modify even a character of the makefile thus saving a lot of time.
- Ant is a Java based build tool, similar to make, but with better support for the cross platform issues involved with developing Java applications. Instead of a model where the tool is extended with shell based commands, it is extended using Java classes. Instead of writing shell commands, the configuration files are XML based calling out a target tree where various tasks get executed. Each task is run by an object which implements a particular Task interface.
- AutoCodeGenerator is a tool which is able to generate other programs that insert, delete, or update database records for a number of different database programs. Programs can be generated in Python, bash, ksh, Java, C, or other languages; the package also generates code for various database servers via a plain text file.
- 'Autobuild' processes output from building software, primarily focused on packages using Autoconf and Automake, and generates HTML summaries. The output includes project name, version, build host types, build host name, and indication of success or failure. The output is indexed in many ways to simplify browsing.
- Extensible package of m4 macros that produce portable shell scripts to automatically configure software source code packages. These scripts can adapt the packages to many kinds of UNIX-like systems with minimal manual user intervention. Autoconf requires GNU M4. You must install GNU M4 1.4.5 or later before configuring Autoconf, so that Autoconf's configure script can find it. The configuration scripts produced by Autoconf are self-contained, so their users do not need to have Autoconf or GNU M4 installed.
- Contains hundreds of free autoconf macros that have been collected for easy reuse in other projects, without requiring any changes in licensing.
- 'Autodist' is a source distribution management system that lets users define what is included in and excluded from a distribution and what license is used. It is especially targeted at large software projects that create multiple distributions from a source tree. Autodist supports distribution management in directory, file, and file content level, and automatic relicensing of a distribution. Please note that Autodist is not a binary packaging system. It is specifically used to create source distributions. A binary packaging system, however can be hooked to the distribution creation process, if needed.