Windows Build Notes =================== To build GNUitar on Windows, you will need the following: o Microsoft Visual C++ 6.0 compiler (MSVC); o GTK 1.2 for Windows o Glib 1.2 for Windows o GNU libintl for Windows o GNU libiconv for Windows All the software except MSVC is free and can be downloaded from the site http://www.gimp.org/win32 OR http://www.gimp.org/~tml/gimp/win32 Currently, the exact links are: http://www.gimp.org/~tml/gimp/win32/libintl-0.10.40-tml-20020904.zip http://sourceforge.net/project/showfiles.php?group_id=25167 (general link for libiconv) http://prdownloads.sourceforge.net/gettext/libiconv-1.8-w32-1.bin.zip?download http://www.gimp.org/~tml/gimp/win32/glib-2.4.7.zip http://www.gimp.org/~tml/gimp/win32/glib-dev-2.4.7.zip http://www.gimp.org/~tml/gimp/win32/gtk+-1.3.0-20040315.zip http://www.gimp.org/~tml/gimp/win32/gtk+-dev-1.3.0-20030115.zip Please note that these links may change with the software updates. Another important note that since the first edition of this build guide, the original packages for GLib 2.2 and GTK 1.3 were removed. What I found are somewhat different versions, however I believe they should work. There is a certain doubt about compatibility of GLib 2.4 and libintl 0.10. In the case of any problems you should download all the latest packages for GLib and its dependencies (but NOT GTK 2.6 !) You can obtain free Microsoft Visual C compiler from these two links: .NET Framework SDK: http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true Platform SDK: http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ (The next two paragraphs is a quote from Forger's manual: http://winprog.org/tutorial). "Microsoft has quietly released it's command line compiler and linker tools as part of the .NET Framework SDK. The Framework SDK comes with everything you need to for .NET development (C# compiler etc...) including the command line compiler cl.exe which, while it's intended for use with the .NET framework, is the same compiler that comes with Visual C++ Standard. Since this is the .NET SDK, it doesn't come with the headers and libraries required for Win32 API development, as these are part of the Platform SDK. The Platform SDK is free as well. You only need the Core SDK, but feel free to download the other components as you desire. As a bonus, if you download the Platform SDK documentation (which I highly recommend) you will have a complete local and up to date Win32 reference which is MUCH easier to use than MSDN online." You need to prepare your build environment, before you start to compile. Most of the packages above contain 2 important directories: "lib" and "include". Copy the contents of the "lib" directory of each package to the folder C:\Program Files\Microsoft Visual Studio\VC98\Lib (adjust this path to the real path where your MSVC installed), and the contents of the "include" directory to C:\Program Files\Microsoft Visual Studio\VC98\Include. Rename include\glib-2.0 to include\glib, lib\glib-2.0 to lib\glib, move \lib\include\gtk+\gdkconfig.h to include\gtkconfig.h. Now, you are ready to build the program. Launch MS Visual Studio, choose File->Open, select file gnuitar.dsp. Select Build->Set Active Configuration and choose "Release" for Pentium Pro/II/III, or "Release 586" for Pentium processor, to make the benefit of Pentium CPU extended instructions set. Press F7 to start build. If all the above were done correctly, you should not get error messages (please note that it produces few dozens of warnings, it is ok). If you get something like "Linker error: cannot resolve external symbols ...", this means that you've done something wrong when preparing build environment. Command-line users should first run the file C:\Program Files\Microsoft Visual Studio\VC98\Bin\vcvars32.bat, to set environment variables, and then run: `nmake /f gnuitar.mak' If all went fine, you should pickup the file gnuitar.exe in the folder gnuitar\Release\ or gnuitar\Release 586\ depending on which configuration did you chose. Now, copy the gnuitar executable somewhere where you are going to keep it, and copy the files: iconv.dll libgdk-0.dll libglib-2.0-0.dll libgmodule-2.0-0.dll libgtk-0.dll libintl-1.dll to the same folder as gnuitar.exe. Ready. Windows Installation - Binary Package ===================================== GNUitar binary package does not require specific install on Windows - just unzip the package and run gnuitar.exe. Linux - Install From RPM ======================== RPM stands for RedHat Package Manager. Just download rpm file from the GNUitar site, and issue shell command as root: rpm -i gnuitar-x.y.z.i386.rpm Linux - Create Your RPM ======================= You can create your own rpm package on Linux. To do so, you need first to install the package "rpm-build" from your Linux CD (first check does the /usr/src/redhat/ directory exist, if yes then you already have it installed). Then, copy the file gnuitar.spec to /usr/src/redhat/SPECS, and gnuitar-x.y.z.tar.gz to /usr/src/redhat/SOURCES. Changde dir to /usr/src/redhat/specs and issue rpm -bb gnuitar.spec This should create the rpm package somewhere under /usr/src/redhat/RPMS. Basic UNIX Installation - Compilation From Sources (standard GNU blah blah) =========================================================================== These are generic installation instructions. The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile' in each directory of the package. It may also create one or more `.h' files containing system-dependent definitions. Finally, it creates a shell script `config.status' that you can run in the future to recreate the current configuration, a file `config.cache' that saves the results of its tests to speed up reconfiguring, and a file `config.log' containing compiler output (useful mainly for debugging `configure'). If you need to do unusual things to compile the package, please try to figure out how `configure' could check whether to do them, and mail diffs or instructions to the address given in the `README' so they can be considered for the next release. If at some point `config.cache' contains results you don't want to keep, you may remove or edit it. The file `configure.in' is used to create `configure' by a program called `autoconf'. You only need `configure.in' if you want to change it or regenerate `configure' using a newer version of `autoconf'. The simplest way to compile this package is: 1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're using `csh' on an old version of System V, you might need to type `sh ./configure' instead to prevent `csh' from trying to execute `configure' itself. Running `configure' takes awhile. While running, it prints some messages telling which features it is checking for. 2. Type `make' to compile the package. 3. Optionally, type `make check' to run any self-tests that come with the package. 4. Type `make install' to install the programs and any data files and documentation. 5. You can remove the program binaries and object files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'. There is also a `make maintainer-clean' target, but that is intended mainly for the package's developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution. Compilers and Options ===================== Some systems require unusual options for compilation or linking that the `configure' script does not know about. You can give `configure' initial values for variables by setting them in the environment. Using a Bourne-compatible shell, you can do that on the command line like this: CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure Or on systems that have the `env' program, you can do it like this: env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure Compiling For Multiple Architectures ==================================== You can compile the package for more than one kind of computer at the same time, by placing the object files for each architecture in their own directory. To do this, you must use a version of `make' that supports the `VPATH' variable, such as GNU `make'. `cd' to the directory where you want the object files and executables to go and run the `configure' script. `configure' automatically checks for the source code in the directory that `configure' is in and in `..'. If you have to use a `make' that does not supports the `VPATH' variable, you have to compile the package for one architecture at a time in the source code directory. After you have installed the package for one architecture, use `make distclean' before reconfiguring for another architecture. Installation Names ================== By default, `make install' will install the package's files in `/usr/local/bin', `/usr/local/man', etc. You can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. You can specify separate installation prefixes for architecture-specific files and architecture-independent files. If you give `configure' the option `--exec-prefix=PATH', the package will use PATH as the prefix for installing programs and libraries. Documentation and other data files will still use the regular prefix. In addition, if you use an unusual directory layout you can give options like `--bindir=PATH' to specify different values for particular kinds of files. Run `configure --help' for a list of the directories you can set and what kinds of files go in them. If the package supports it, you can cause programs to be installed with an extra prefix or suffix on their names by giving `configure' the option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. Optional Features ================= Some packages pay attention to `--enable-FEATURE' options to `configure', where FEATURE indicates an optional part of the package. They may also pay attention to `--with-PACKAGE' options, where PACKAGE is something like `gnu-as' or `x' (for the X Window System). The `README' should mention any `--enable-' and `--with-' options that the package recognizes. For packages that use the X Window System, `configure' can usually find the X include and library files automatically, but if it doesn't, you can use the `configure' options `--x-includes=DIR' and `--x-libraries=DIR' to specify their locations. Specifying the System Type ========================== There may be some features `configure' can not figure out automatically, but needs to determine by the type of host the package will run on. Usually `configure' can figure that out, but if it prints a message saying it can not guess the host type, give it the `--host=TYPE' option. TYPE can either be a short name for the system type, such as `sun4', or a canonical name with three fields: CPU-COMPANY-SYSTEM See the file `config.sub' for the possible values of each field. If `config.sub' isn't included in this package, then this package doesn't need to know the host type. If you are building compiler tools for cross-compiling, you can also use the `--target=TYPE' option to select the type of system they will produce code for and the `--build=TYPE' option to select the type of system on which you are compiling the package. Sharing Defaults ================ If you want to set default values for `configure' scripts to share, you can create a site shell script called `config.site' that gives default values for variables like `CC', `cache_file', and `prefix'. `configure' looks for `PREFIX/share/config.site' if it exists, then `PREFIX/etc/config.site' if it exists. Or, you can set the `CONFIG_SITE' environment variable to the location of the site script. A warning: not all `configure' scripts look for a site script. Operation Controls ================== `configure' recognizes the following options to control how it operates. `--cache-file=FILE' Use and save the results of the tests in FILE instead of `./config.cache'. Set FILE to `/dev/null' to disable caching, for debugging `configure'. `--help' Print a summary of the options to `configure', and exit. `--quiet' `--silent' `-q' Do not print messages saying which checks are being made. To suppress all normal output, redirect it to `/dev/null' (any error messages will still be shown). `--srcdir=DIR' Look for the package's source code in directory DIR. Usually `configure' can determine that directory automatically. `--version' Print the version of Autoconf used to generate the `configure' script, and exit. `configure' also accepts some other, not widely useful, options.