xforms  1.2.4
About: XForms is a graphical user interface toolkit for X based on the X11 Xlib library.
  Fossies Dox: xforms-1.2.4.tar.gz  ("unofficial" and yet experimental doxygen-generated source code documentation)  

No Matches
xforms Documentation

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the steelblue colored "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies xforms-1.2.4.tar.gz contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).
			  XForms Version 1.2.0

This is the Free Software distribution of the XForms Library, a
graphical user interface toolkit for X Window Systems.

It should work under X11 R4, R5 & R6. XForms is free software. It is
licensed under the GNU LGPL (Lesser General Public License) version 2.1.
See the file COPYING.LIB for the gory details.

What's new?

XForms 1.2.0 is a new stable version of the library. Numerous
bugs have been fixed, new features have been added and the
documentation is now part of the package.

For more information, read the file ChangeLog.

Getting XForms

The XForms homepage is accessible at


The sources can be downloaded from the project page at


See the "Download Area" on that page. On this page you should
select the file named 'xforms.latest_stable.tar.gz' (which will
point to the latest stable release, including bug-fixes that may
have become necessary) to download the sources -  unless you're
prepared to take part in testing the "bleeding edge" versions
that have a name containing '-preX' (where X is some number),
indicating that it is a pre-release on the way to a new stable

Keeping in touch

There is a mailing list for XForms. To subscribe (or unsubscribe)
go to


or send an email to


with a subject line consisting of just 'subscribe' or 'unsubscribe'.

To use the mailing list, send your message to


Remember your message will be sent to many people. Please DO NOT send
subscribe/unsubscribe messages to the list, send it to

The archive of the mailing list can be found at


Messages sent to the mailing list before August 2009 are at


Compiling XForms

You should be able to compile XForms on any 'reasonable' flavour of

XForms relies on some other libraries, namely (for compiling
XForms you will need development versions, i.e. versions that
contain the header files for the libraries)

    * libX11
	* libXpm, version 4.7 or newer.
	* libjpeg, 6.0b or newer.
	* libGL (optional)

You will find generic installation instructions common to all
autoconf-based packages in the file INSTALL. In general, all it
takes to compile and install XForms is

	make install

There are some features that you may want to control by using
options when running the 'configure' script'. To find out about
all of them run 'configure' with the '--help' option. The more
commonly used include:

  o --disable-gl makes sure that gl support is not built even if
    you have proper GL libraries installed.

  o --enable-demos adds "demos/" to the list of directories to
    build. It contains various program demonstrating the use of the
    XForms library.

  o --enable-docs instructs the 'configure' script to also
    add the documentation (in info, HTML and PDF format) to
    the targets to be build. This requires some additional

For more complicated cases, ./configure takes the following specific

  o --with-extra-lib=DIRECTORY that specifies the path where XForms will
    find extra libraries (Xpm, jpeg...) it needs. Defaults to NONE
    (i.e. search in standard places). You can specify several
    directories, separated by colons.

  o --with-extra-inc=DIRECTORY that gives the place where XForms will find
    headers.  Defaults to NONE (i.e.  search in standard places).
    You can specify several directories, separated by colons.

  o --with-extra-prefix[=DIRECTORY] that is equivalent to
       --with-extra-lib=DIRECTORY/lib --with-extra-inc=DIRECTORY/include
    If DIRECTORY is not specified, the current prefix is used.

  o --enable-optimization=VALUE enables you to set optimization to a
    higher level as the default (-O), for example --enable-optimization=-O3.

  o --disable-optimization - you can use this to disable compiler
    optimization of LyX. The compile may be much quicker with some
    compilers, but XForms applications will run more slowly.

  o --enable-debug will add debug information to your binary. This
    requires a lot more disk space, but is a must if you want to try to
    debug problems in XForms. The default is to have debug information
    for development versions and prereleases only.

  o --enable-bwc-bs-hack enables some workarounds for incompatibilities
    that may keep very old programs using XForms from working correctly.
    Please only use as a last resort.

Moreover, the following generic configure flags may be useful:

  o --prefix=DIRECTORY specifies the root directory to use for
    installation. [defaults to /usr/local]

  o --enable-maintainer-mode enables some code that automatically
    rebuilds the configure script, makefiles templates and other useful
    files when needed. This is off by default, to avoid surprises.

Note that the --with-extra-* commands are not really robust when it
comes to use of relative paths.  If you really want to use a relative path
here, you can prepend it with "`pwd`/".

If you do not like the default compile flags used (-g -O on gcc), you can
set CFLAGS variable to other values as follows:

  ./configure CFLAGS='-O2' <other-options>

Similarly, if you want to force the use of some specific compiler, you can
give a value to the CC variable.

The following option might be useful in order to make the compiler
more verbose about potential problems:

  o --enable-warnings that make the compiler output more warnings during
    the compilation.  Opposite is --disable-warnings.