Compiling the Nautilus-Actions package

## Compiling the Nautilus-Actions package Compiling the Nautilus-Actions Package — How to compile Nautilus-Actions |

## Building Nautilus-Actions™ on UNIX

On UNIX, Nautilus-Actions™ uses the standard GNU build system, using autoconf for package configuration and resolving portability issues, automake for building makefiles that comply with the GNU Coding Standards, and libtool for building shared libraries on multiple platforms. The normal sequence for compiling and installing the Nautilus-Actions™ package is thus:

`./configure`
`make`
`make install`

The standard options provided by GNU autoconf may be passed to the configure script. Please see the autoconf documentation or run ./configure --help for information about the standard options.

## Dependencies

Before you can compile the Nautilus-Actions™ package, you need to have various other tools and libraries installed on your system. The two main tools needed during the build process (as differentiated from the tools used in when creating Nautilus-Actions™ mentioned above such as autoconf) are pkg-config and GNU make.

- pkg-config is a tool for tracking the compilation flags needed for libraries that are used by the Nautilus-Actions™ package. (For each library, a small `.pc` text file is installed in a standard location that contains the compilation flags needed for that library along with version number information.)

- The Nautilus-Actions™ makefiles will mostly work with different versions of make. However, there tends to be a few incompatibilities, so the Nautilus-Actions™ team recommends installing GNU make if you don't already have it on your system and using it. (It may be called gmake rather than make.)

Nautilus-Actions™ depends on a number of other libraries.

- GLib and Gtk+ are fondamental libraries, both for user interface and for portability and internationalization management.

- libxml2 is used to manage XML imports and exports.

- libgtop2 is used to detect and identify running processes as part of the validation process of a candidate context.

- libSM and libICE are used as a session management libraries, in order to be sure the session will not terminate without at least proposing the user to save his modifications.

- libUUID is the universally unique ID library used to automatically generate a unique identifier at item creation.

- libunique is required so that the Nautilus-Actions Configuration Tool only executes one instance.

- And, of course, Nautilus™ extension is required because Nautilus-Actions™ is first a Nautilus™ extension.

## Extra Configuration Options

In addition to the normal options, the configure script in the Nautilus-Actions™ package supports these additional arguments:

`configure` [[--with-nautilus-extdir=DIR]] [[--with-default-io-provider=na-gconf|na-desktop]] [[--enable-html-manuals[=gdt|db2html]]] [[--enable-pdf-manuals[=dblatex]]]

`--with-nautilus-extdir=DIR`. With this option, one may define an alternate directory where our Nautilus™ extensions will be stored. This is most commonly useful:

- In development mode, we only have to install symlinks from Nautilus™ standard location to our development tree once. Then, each new version of our libraries will be automatically considered by Nautilus™.

- When running make distcheck, so that compiled libraries do not interfere with installed ones.

- When Nautilus™ is not installed itself in a standard location.

`--with-default-io-provider=na-gconf|na-desktop`. As of version 3.0, Nautilus-Actions™ may store menus and actions both in GConf, which is the historical behavior, or as `.desktop` files. This option lets the packager define which will be the default destination when a new menu or action will be created. This defaults to "na-desktop" which is the internal identifier of the I/O provider which manages `.desktop` files.

`--enable-html-manuals[=gdt|db2html]`. This option lets the packager regenerate user's manuals from the DocBook sources as HTML documents. All available translations are generated. Building HTML documents from DocBook source can be realized through gnome-doc-tool or db2html. Nautilus-Actions™ defaults to use gnome-doc-tool as the output format better sticks with those of Yelp. As this option is always set when running make distcheck, the packager can be mostly sure that the distributed manuals are up to date, and may safely ignore this option.

`--enable-pdf-manuals[=dblatex]`. This option lets the packager regenerate user's manuals from the DocBook sources as PDF documents. All available translations are generated. As this option is always set when running make distcheck, the packager can be mostly sure that the distributed manuals are up to date, and may safely ignore this option.