Imake - Revision history

Jsummers: Removed from Software category, for consistency (article is significantly about Imake's file formats, plus it's not listed in the Software hierarchy).

2017-06-11T15:25:32Z

Removed from Software category, for consistency (article is significantly about Imake's file formats, plus it's not listed in the Software hierarchy).

Jsummers at 20:26, 5 May 2016

2016-05-05T20:26:52Z

Jsummers at 16:11, 19 March 2016

2016-03-19T16:11:07Z

Dan Tobias: Add infobox

2014-12-27T19:46:05Z

Add infobox

Alanc: Created page with "Imake was a build tool used to generate Makefiles for software to be portable to a range of operating systems. It was originally developed to build the X Window System, ..."

2014-12-27T19:18:23Z

Created page with "Imake was a build tool used to generate Makefiles for software to be portable to a range of operating systems. It was originally developed to build the X Window System, ..."

New page

Imake was a build tool used to generate Makefiles for software to be portable to a range of operating systems. It was originally developed to build the [[X Window System]], and was adopted by many X applications, and some non-X software such as the tcsh shell. It required maintaining a per-platform config file containing all the information about which interfaces were used on each platform, and thus did not scale well from the commercial Unix world it was designed for to the explosion of free OS distros, nor to handling interface choices that were needed by new programs. The X Window System itself moved from Imake to the GNU autotools (autoconf, automake, libtool, pkg-config) in 2005, and while X.Org still provides Imake for existing software that needs it, has deprecated it and recommends against using it in new software.

== File Format ==

Software that was to be built with imake distributed files named ''Imakefile'', one in each directory that needed a Makefile. The file was basically a Makefile format file in which certain sections or text would be generated using C language style macros which were expanded via the ''cpp'' preprocessor.

To build such software, users would usually run the command ''xmkmf'' which is a shell script wrapper around the ''imake'' command. ''imake'' in turn determined which platform specific defines needed to be passed to ''cpp'', set up the include paths for the imake config files which ''cpp'' would include to find the macro defintions, and then used ''cpp'' to generate ''Makefile'' files in each subdirectory. Users could then run "make" or "make install" as necessary to build and install the software.

== Software ==

* [http://www.x.org/releases/individual/util/ X.Org download site for imake & config file releases]
* [http://cgit.freedesktop.org/xorg/util/imake X.Org git repo for imake]
* [http://cgit.freedesktop.org/xorg/util/cf/ X.Org git repo for imake config files]

== References ==

* [http://shop.oreilly.com/product/9781565922266.do ''Software Portability with imake, 2nd Edition''] by Paul DuBois, ISBN 978-1-56592-226-6
* [http://www.kitebird.com/imake-book/ Archive for "Software Portability with imake" (2nd edition)]
* [http://www.snake.net/software/imake-stuff/ imake-Related Software and Documentation]

[[Category:Software]]
[[Category:X Window System]]

← Older revision		Revision as of 20:26, 5 May 2016
Line 25:		Line 25:
	[[Category:Software]]		[[Category:Software]]
	[[Category:X Window System]]		[[Category:X Window System]]
		+	[[Category:File formats with a distinctive filename]]

@@ Line 3: / Line 3: @@
 |subcat=Development
 }}
-'''Imake''' was a build tool used to generate Makefiles for software to be portable to a range of operating systems.   It was originally developed to build the [[X Window System]], and was adopted by many X applications, and some non-X software such as the tcsh shell.   It required maintaining a per-platform config file containing all the information about which interfaces were used on each platform, and thus did not scale well from the commercial Unix world it was designed for to the explosion of free OS distros, nor to handling interface choices that were needed by new programs.   The X Window System itself moved from Imake to the GNU autotools (autoconf, automake, libtool, pkg-config) in 2005, and while X.Org still provides Imake for existing software that needs it, has deprecated it and recommends against using it in new software.
+'''Imake''' was a build tool used to generate Makefiles for software to be portable to a range of operating systems.   It was originally developed to build the [[X Window System]], and was adopted by many X applications, and some non-X software such as the tcsh shell.   It required maintaining a per-platform config file containing all the information about which interfaces were used on each platform, and thus did not scale well from the commercial Unix world it was designed for to the explosion of free OS distros, nor to handling interface choices that were needed by new programs.   The X Window System itself moved from Imake to the [[Autotools|GNU autotools]] (autoconf, automake, libtool, pkg-config) in 2005, and while X.Org still provides Imake for existing software that needs it, has deprecated it and recommends against using it in new software.
 == File Format ==

@@ Line 9: / Line 9: @@
 Software that was to be built with imake distributed files named ''Imakefile'', one in each directory that needed a Makefile.  The file was basically a Makefile format file in which certain sections or text would be generated using C language style macros which were expanded via the ''cpp'' preprocessor.
-To build such software, users would usually run the command ''xmkmf'' which is a shell script wrapper around the ''imake'' command.   ''imake'' in turn determined which platform specific defines needed to be passed to ''cpp'', set up the include paths for the imake config files which ''cpp'' would include to find the macro defintions, and then used ''cpp'' to generate ''Makefile'' files in each subdirectory.   Users could then run "make" or "make install" as necessary to build and install the software.
+To build such software, users would usually run the command ''xmkmf'' which is a shell script wrapper around the ''imake'' command.   ''imake'' in turn determined which platform specific defines needed to be passed to ''cpp'', set up the include paths for the imake config files which ''cpp'' would include to find the macro definitions, and then used ''cpp'' to generate ''Makefile'' files in each subdirectory.   Users could then run "make" or "make install" as necessary to build and install the software.
 == Software ==
@@ Line 23: / Line 23: @@
 * [http://www.snake.net/software/imake-stuff/ imake-Related Software and Documentation]
 [[Category:X Window System]]
 [[Category:File formats with a distinctive filename]]

@@ Line 1: / Line 1: @@
-Imake was a build tool used to generate Makefiles for software to be portable to a range of operating systems.   It was originally developed to build the [[X Window System]], and was adopted by many X applications, and some non-X software such as the tcsh shell.   It required maintaining a per-platform config file containing all the information about which interfaces were used on each platform, and thus did not scale well from the commercial Unix world it was designed for to the explosion of free OS distros, nor to handling interface choices that were needed by new programs.   The X Window System itself moved from Imake to the GNU autotools (autoconf, automake, libtool, pkg-config) in 2005, and while X.Org still provides Imake for existing software that needs it, has deprecated it and recommends against using it in new software.
+{{FormatInfo
 == File Format ==
@@ Line 6: / Line 10: @@
 To build such software, users would usually run the command ''xmkmf'' which is a shell script wrapper around the ''imake'' command.   ''imake'' in turn determined which platform specific defines needed to be passed to ''cpp'', set up the include paths for the imake config files which ''cpp'' would include to find the macro defintions, and then used ''cpp'' to generate ''Makefile'' files in each subdirectory.   Users could then run "make" or "make install" as necessary to build and install the software.
 == Software ==