Menu
▾
▴
[Freepv-cvs] SF.net SVN: freepv: [136] freepv/branches/branch_leonox
|
From: <bru...@us...> - 2008-03-02 23:06:32
|
Revision: 136
http://freepv.svn.sourceforge.net/freepv/?rev=136&view=rev
Author: brunopostle
Date: 2008-03-02 15:06:34 -0800 (Sun, 02 Mar 2008)
Log Message:
-----------
Update build instructions
Modified Paths:
--------------
freepv/branches/branch_leonox/INSTALL
freepv/branches/branch_leonox/README
Modified: freepv/branches/branch_leonox/INSTALL
===================================================================
--- freepv/branches/branch_leonox/INSTALL 2008-03-02 22:48:51 UTC (rev 135)
+++ freepv/branches/branch_leonox/INSTALL 2008-03-02 23:06:34 UTC (rev 136)
@@ -1,167 +1,55 @@
-Basic Installation
-==================
+Using the CMake build system under Unix
+=======================================
- These are generic installation instructions.
+briefly, do the following:
- 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').
+cmake -DCMAKE_INSTALL_PREFIX=/usr/local .
+make
+make install
- 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.
+alternatively, you can also do an out of source build, if
+you don't want to clutter the source tree with object files etc.
- 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'.
+$ cd freepv
+$ mkdir mybuild
+$ cd mybuild
+$ cmake -DCMAKE_INSTALL_PREFIX=/usr/local ../
+$ make
+$ make install
-The simplest way to compile this package is:
+Please report any problems to the Freepv-devel mailing list:
+https://lists.sourceforge.net/lists/listinfo/freepv-devel
- 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 a while. While running, it prints some
- messages telling which features it is checking for.
+Missing dependencies
+=======================
+If cmake failed to pick up some dependencies, make sure you have
+installed the corresponding development packages (often named:
+libjpeg-dev and so on). If cmake still fails to find the libraries,
+for example if you have installed them into a non-standard directory,
+you can specify the path to libraries and include files using the
+ccmake program:
+$ cmake .
+[some failure]
+$ ccmake .
- 2. Type `make' to compile the package.
-
- 3. Type `make install' to install the programs and any data files and
- documentation.
-
- 4. You can remove the program binaries and object files from the
- source code directory by typing `make clean'.
-
-Compilers and Options
+Configuring the build
=====================
- 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
+Upon cmake invocation, several variables can be set with the -D command line
+parameter. Important variables include:
-Or on systems that have the `env' program, you can do it like this:
- env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
+CMAKE_INSTALL_PREFIX Destination directory of make install
+ (default: /usr/local)
+LIB_SUFFIX Specifies suffix used for library paths. For AMD64,
+ usually 64 is used as prefix. Default: empty.
+ Setting to 64 results in: $CMAKE_INSTALL_PREFIX/lib64
-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.
-
- 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
+For distributors:
=================
+CMake supports the DESTDIR variable during make install, this
+might be helpful to install into a temporary directory during
+package creation
- 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.
+$ make install DESTDIR=mytmp_package_dir
- 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.
-
-`--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.
-
Modified: freepv/branches/branch_leonox/README
===================================================================
--- freepv/branches/branch_leonox/README 2008-03-02 22:48:51 UTC (rev 135)
+++ freepv/branches/branch_leonox/README 2008-03-02 23:06:34 UTC (rev 136)
@@ -12,3 +12,19 @@
libxmu-dev
x11proto-xf86vidmode-dev
libxxf86vm-dev
+
+fedora f8:
+
+firefox-devel
+libjpeg-devel
+zlib-devel
+cmake
+pkgconfig
+gcc-c++
+libXxf86vm-devel
+freeglut-devel
+libXt-devel
+libXmu-devel
+libxml2-devel
+libpng-devel
+
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|