
	Where results make sense

Topic: GNU build system

Related Topics

GNU toolchain

GNU Compiler Collection

In the News (Tue 29 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	GNU build system - Wikipedia, the free encyclopedia
		The GNU build system is widely used in many free software and open source packages.
		While the tools comprising the GNU build system themselves are GPL-ed free software, there are no restrictions in using them in making non-free software portable.
		GNU Autoconf, Automake and Libtool, by Gary V. Vaughan, Ben Elliston, Tom Tromey, and Ian Lance Taylor.
	en.wikipedia.org /wiki/GNU_build_system (180 words)

	Libtool - Wikipedia, the free encyclopedia
		GNU Libtool is a GNU programming tool from the GNU build system used for creating portable software libraries.
		GNU Libtool simplifies the developer's job by encapsulating both the platform-specific dependencies, and the user interface, in a single script.
		GNU Libtool is designed so that the complete functionality of each host type is available via a generic interface, but nasty quirks are hidden from the programmer.
	en.wikipedia.org /wiki/Libtool (226 words)

	GNU build system - Wikipedia, the free encyclopedia
		The GNU build system, also called the GNU Autotools is a suite of tools produced by the GNU project that assist in making packages portable to many UNIX-like systems.
		The book GNU Autoconf, Automake and Libtool, by Gary V. Vaughan, Ben Elliston, Tom Tromey, and Ian Lance Taylor.
		The GNU Coding Standards (http://www.gnu.org/prep/standards.html) (especially the chapter on The Release Process).
	www.encyclopedia-online.info /GNU_build_system (160 words)

	Developing software with GNU: Preface (Site not responding. Last check: 2007-10-20)
		The GNU project was founded in 1984 by Richard Stallman in response to the increasing obstacles to cooperation imposed on the computing community by the owners of proprietary software.
		The goal of the GNU project is to remove these obstacles by developing a complete software system, named GNU (1) and distributing it as free software.
		Proprietary systems often do not bundle such tools with their distributions because their developers regard the users as a market that buys software licenses and treats the computer as an appliance.
	www.ugcs.caltech.edu /manuals/devtool/autotoolset-0.11.4 (1129 words)

	The GNU configure and build system - Introduction
		The system permits the developer to concentrate on writing the program, simplifying many details of portability across Unix and even Windows systems, and permitting the developer to describe how to build the program using simple rules rather than complex Makefiles.
		The X Window system is built using the imake tool, which uses a database of rules to eliminate the duplication.
		However, building a tool which was developed using imake requires that the builder have imake installed, violating one of the goals of the GNU system.
	www.airs.com /ian/configure/configure_1.html (1182 words)

	Automake
		GNU Automake is a programming tool that produces portable makefiles for use by the make program, used in compiling software.
		This attempts to avoid the problem with some static dependency systems, where the dependencies are detected only once when the programmer starts working on the project.
		In such a case, if a source file gains a new dependency (e.g., if the programmer adds a new #include directive in a C source file), then a discrepancy is introduced between the real dependencies and those that are used by the compilation system.
	www.brainyencyclopedia.com /encyclopedia/a/au/automake.html (577 words)

	Introducing the GNU tools (Site not responding. Last check: 2007-10-20)
		The GNU build tools are meant to be used in the development of free software, therefore if you have a working build system in place for your programs, you can create a source code distribution out of it by running
		The GNU build system needs to be installed only when you are developing programs that are meant to be distributed.
		Also, by setting up the GNU build system such that it creates programs that don't require the build system to be present during their installation, it becomes possible to use the build system to bootstrap itself.
	www.bilmuh.gyte.edu.tr /gokturk/introcpp/gnutools/node64.html (519 words)

	GNU build system: Encyclopedia topic (Site not responding. Last check: 2007-10-20)
		GNU Automake (Automake: automake is a programming tool that produces portable makefiles for use by the make...
		The GNU build system is widely used in many free software (free software: free software, as defined by the free software foundation (fsf), is software which...
		While the tools comprising the GNU build system themselves are GPL (GPL: the gnu general public license (gnu gpl or simply gpl) is a free software license,...
	www.absoluteastronomy.com /reference/gnu_build_system2 (355 words)

	Learning the GNU development tools: Preface (Site not responding. Last check: 2007-10-20)
		The purpose of this document is to introduce you to the GNU build system, and show you how to use it to write good code.
		In fact, one of the reasons for the elaborate GNU build system was to make software portable between GNU and other similar operating systems.
		Ultimately I want this document to be both a unified introduction of the GNU build system as well as documentation for the Autotools package.
	www.ugcs.caltech.edu /manuals/devtool/autotoolset-tutorial (1317 words)

	Autoconf: The GNU build system (Site not responding. Last check: 2007-10-20)
		Autoconf solves an important problem--reliable discovery of system-specific build and runtime information--but this is only one piece of the puzzle for the development of portable software.
		To this end, the GNU project has developed a suite of integrated utilities to finish the job Autoconf started: the GNU build system, whose most important components are Autoconf, Automake, and Libtool.
		In this chapter, we introduce you to those tools, point you to sources of more information, and try to convince you to use the entire GNU build system for your software.
	www.dis.com /gnu/autoconf/autoconf_2.html (101 words)

	DevChannel \| Maturing GNU Build System's ctof sample application
		The goal of that article was to introduce the GNU Build System and show the user how to make applications portable across different platforms by using the automake and autotools packages.
		It should be equally straightforward to do with the GNU Build System, but some readers did not find it easy to do, especially if users do not want to rely on automated scripts that put together the configure.ac and Makefile.am files for you; there ends up being a lot of bloat in these files.
		Unlike with CMake, the GNU Build System automatically abides by the shared library naming conventions, meaning it creates a real library called libconvert.so.1.0.2 and two symlinks that point to it: a run-time symlink named libconvert.so.1 and a compile-time symlink named libconvert.so.
	tools.devchannel.org /devtoolschannel/04/01/26/0143221.shtml?tid=46 (1738 words)

	The GNOME Build Environment (Site not responding. Last check: 2007-10-20)
		This build system employs macros and scripts to deal with the repetitive drudgery that software projects normally require.
		The GNU build system can produce a complete, full-blooded compilation environment for your project with as little as three files and a dozen handwritten lines of text.
		The three main components of the GNU build system are autoconf, automake, and libtool.
	developer.gnome.org /doc/books/WGA/gnome-build.html (1662 words)

	Developing software with GNU
		GNU Autoconf is part of the GNU build system and we first introduce in in section The GNU build system.
		The GNU build system in general requires that all the object files that build a specific library be under the same directory.
		Because on Unix systems, the system libraries are proprietary, their terms also may not allow you to distribute executables derived from them.
	www.amath.washington.edu /~lf/tutorials/autoconf/toolsmanual.html (17807 words)

	Learning the GNU development tools: (Site not responding. Last check: 2007-10-20)
		GNU Autoconf is part of the GNU build system and we first introduce in in 5.
		In a vpath build, the source distribution is stored in a, possibly read-only, directory, and the actual building takes place in a different directory where all the generated files are being stored.
		The C programming language is the native language of GNU, and the GNU coding standards encourage you to program in C. The main advantages of C are that it can be compiled with the system's native compiler, many people know C, and it is easy to learn.
	autotoolset.sourceforge.net /tutorial.html (12469 words)

	DevChannel \| Simplifying program packaging with the GNU Build System
		Anybody who has compiled a program from source has undoubtedly seen the fruits of the Autoconf and Automake packages that make up the core of the GNU Build System.
		The driving force behind the build system is portability.
		When you have verified that everything builds properly, you can use a very handy feature of the GNU Build System to package up your source tree for distribution.
	tools.devchannel.org /devtoolschannel/03/11/14/1615230.shtml?tid=46 (2145 words)

	[No title] (Site not responding. Last check: 2007-10-20)
		The included build system assumes GNU build system and make tools (m4, automake, autoconf, libtool and gmake).
		To build using GNU tools, type in the source directory:./autogen.sh make Currently, the source implements playback in pure C on all platforms except ARM, where a [currently] small amount of assembly (see asm_arm.h) is used to implement 64 bit math operations and fast LSP computation.
		If building on ARM without the benefit of GNU build system tools, be sure that '_ARM_ASSEM_' is #defined by the build system if this assembly is desired, else the resulting library will use whatever 64 bit math builtins the compiler implements.
	svn.xiph.org /trunk/Tremor/README (289 words)

	Info: (dir) Top (Site not responding. Last check: 2007-10-20)
		GNU Gettext Utilities * Gettext GNU gettext utilities.
		GNU admin * Autoconf Create source code configuration scripts * Automake14 Making Makefile.in's Library of useful routines for 'C' programing * GLIB useful routines for 'C' programming Miscellaneous * File utilities GNU file utilities.
		GNU lightning, a library for dynamic code generation * Using and porting GNU lightning Version Control * PRCS The Project Revision Control System.
	bernstein-plus-sons.com /cgi-sys/cgiwrap/yaya/info2html?... (1038 words)

	Autoconf - The GNU build system
		Libtool handles all the requirements of building shared libraries for you, and at this time seems to be the only way to do so with any portability.
		As your software is distributed to more and more users, however, you will otherwise quickly find yourself putting lots of effort into reinventing the services that the GNU build tools provide, and making the same mistakes that they once made and overcame.
		There are a number of places that you can go to for more information on the GNU build tools.
	www.linuxselfhelp.com /gnu/autoconf/html_chapter/autoconf_2.html (672 words)

	Sægiri, the Taprobane GNU/Linux Build System (Site not responding. Last check: 2007-10-20)
		Sægiri is the build system used to create Taprobane GNU/Linux ISOs.
		Sægiri is a Free Software (Open Source) released under the GNU General Public License.
		Build can be run once in a while to keep the live CD `up to date'.
	taprobane.org /saegiri.php (267 words)

	Autoconf
		This manual is for GNU Autoconf (version 2.59, 5 November 2003), a package for creating scripts to configure source code packages using templates and an M4 macro package.
		Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with the Front-Cover texts being “A GNU Manual,” and with the Back-Cover Texts as in (a) below.
		Its lack of support for automatic dependency tracking, recursive builds in subdirectories, reliable timestamps (e.g., for network filesystems), and so on, mean that developers must painfully (and often incorrectly) reinvent the wheel for each project.
	www.tug.org /texinfohtml/autoconf.html (6472 words)

	CPS: Overall Code Structure.
		The core of this standard automatic configuration system is the developer's configure script `configure.in' (in the root./phys/ directory of the CPS).
		You should be warned, however, that the configure script stores a record of the build options in a file called config.status or config.cache.
		The GNU version of make is used simply because it has a little more functionality that standard make programs.
	www.epcc.ed.ac.uk /~ukqcd/cps/structure/structure.html (541 words)

	NewsForge \| Integrating QT Designer and the GNU Build System with KDevelop
		Recently, I wrote about putting QT Designer and the GNU Build System to good use.
		You would have to apply the GNU Build System principals to the package manually after the fact.
		You cannot exert much control over the GNU Build System without resorting to manually editing files from the command line, but KDevelop does a more than adequate job, so there should be no need to do so.
	www.newsforge.com /programming/03/12/04/1816241.shtml?tid=105&tid=140 (256 words)

	gmane.comp.sysutils.mtools.devel
		Hello, I am writing you about the GNU mtools project, as part of by effort to help GNU projects provide a better, more consistent build system.
		The system do not seem to cache reading of floppies (as it did in linux 2.2), if I do a second "mdir a:" it reads the floppy disk again.
		This was disastrous since the disk image creation failed but the build would silently continue in the face of it.
	blog.gmane.org /gmane.comp.sysutils.mtools.devel (1249 words)

	Autoconf
		Autoconf solves an important problem--reliable discovery of system-specific build and run-time information--but this is only one piece of the puzzle for the development of portable software.
		Developers who are used to the simplicity of @command{make} for small projects on a single system might be daunted at the prospect of learning to use Automake and Autoconf.
		On those few processors without a native arithmetic shift (for instance Cray vector systems) zero bits may be shifted in, the same as a shift of an unsigned type.
	computing.ee.ethz.ch /sepp/autoconf-2.54-et (9784 words)

	Encyclopedia Search
		Chess underwent a transition to version 5.Version 5 was essentially a...
		build system is a suite of tools...produced by the
		Manifesto was written by Richard Stallman...of the goals ofthe
	www.encyclopedian.com /search.php?searWords=GNU (174 words)

	Libtool: Encyclopedia topic (Site not responding. Last check: 2007-10-20)
		He also had to design a configuration interface so that the package installer could choose what sort of libraries were built.
		users don't need to read obscure documentation in order to have their favorite source package build shared libraries.
		Part of GNU build system (GNU build system: the gnu build system, also called the gnu autotools is a suite of tools produced by...
	www.absoluteastronomy.com /reference/libtool (205 words)

	phpMan: autoreconf() (Site not responding. Last check: 2007-10-20)
		File: autoconf.info, Node: autoreconf Invocation, Prev: autoconf Invocation, Up: Making configure Scripts Using `autoreconf' to Update `configure' Scripts ================================================ Installing the various components of the GNU Build System can be tedious: running `gettextize', `automake' etc. in each directory.
		It may be needed either because some tools such as `automake' have been updated on your system, or because some of the sources such as `configure.ac' have been updated, or finally, simply in order to install the GNU Build System in a fresh tree.
		It runs `autoconf', `autoheader', `aclocal', `automake', `libtoolize', and `gettextize' (when appropriate) repeatedly to update the GNU Build System in specified directories, and their subdirectories (*note Subdirectories::).
	www.ournet.md /~freebsd/divers/man.php/info/autoreconf (272 words)

Try your search on: Qwika (all wikis)