mars_nwe/mars-flaim
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added INSTALL.W32 docs, update Makefile.ams appropriately.

Browse Source 
git-svn-id: https://svn.code.sf.net/p/flaim/code/trunk@1067 0109f412-320b-0410-ab79-c3e0c5ffbbe6
This commit is contained in:
jcalcote
2008-06-30 18:30:41 +00:00
parent d4eff861a0
commit 51cd985ef5
10 changed files with 696 additions and 74 deletions
Download Patch File Download Diff File Expand all files Collapse all files

251
INSTALL Normal file
View File

@@ -0,0 +1,251 @@
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
The flaim-projects Autotools Build System
=========================================
This project is actually an umbrella project for several smaller
projects that are all part of the FLAIM database suite. This project
is designed to simply configure and build each of the four sub-projects
in the flaim-projects suite (flaim, ftk, sql, and xflaim) as separate
projects. By using an umbrella project in this fashion, we have the
ability to allow interproject dependencies.
The three project build systems for flaim, sql, and xflaim have been
designed to attempt to locate the ftk (flaim toolkit) in several
locations including as a sub-directory of the current directory, as
a sibling directory to themselves, and as an installed library sdk.
For more detailed information, please read the README files found
in each of the four sub-projects.
Windows
=======
For Microsoft Windows building and installation information, please
refer to INSTALL.W32.
Basic Installation
==================
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, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
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 you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' 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. Run `./configure --help'
for details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
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 support 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' cannot figure out
automatically, but needs to determine by the type of machine the package
will run on. Usually, assuming the package is built to be run on the
_same_ architectures, `configure' can figure that out, but if it prints
a message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS KERNEL-OS
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 machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
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.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).
`configure' Invocation
======================
`configure' recognizes the following options to control how it
operates.
`--help'
`-h'
Print a summary of the options to `configure', and exit.
`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.
`--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.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.

109
INSTALL.W32 Normal file
View File

@@ -0,0 +1,109 @@
Building on Windows
===================
Visual C++ 2008 Express is good, but more to the point, it's free.
To build the FLAIM projects, you will need to download and install
Visual C++ 2008 Express (which now thankfully comes with a reasonably
late version of the Windows Platform SDK).
You can get Visual C++ 2008 Express here:
http://www.microsoft.com/express/vc
The ">> Download Now!" link on that page, and decide whether you want to
install from the web (slow) or install off-line (also slow - there's no
fast solution, sorry).
Once Visual C++ 2008 Express has been installed you may simply double
click on any of the flaim project solution files to bring up the flaim
project in the Visual C++ 2008 IDE. Use the main or context menu options
to build the desired targets.
The flaim project solution files are located in the win32 directories
in the following locations:
flaim-projects
flaim
win32 - flaim.sln
ftk
win32 - flaimtk.sln
sql
win32 - flaimsql.sln
xflaim
win32 - xflaim.sln
win32 - flaim-projects.sln
The projects may be build individually from each of the lower-level
solution files, or all at once from the flaim-projects solution file.
WARNING: The flaim-projects solution file refers to the same project
files as the individual lower-level solution files, so if you make
changes in one of these, they'll be reflected in the other.
FLAIM Runtime Library Use
=========================
FLAIM libraries - both static and dynamic - and the flaim utilities
consume the dynamic (DLL) form of the Visual C++ 2008 runtime libraries.
This is in alignment with the use of runtime libraries on Unix platforms.
It's more efficient and flexible to use the DLL versions of these libraries,
and it allows Microsoft to update these libraries as necessary to fix
security holes and defects which may be found in the future.
With each new version of Windows and Microsoft tools, Microsoft
platforms become more security minded - and more secure. This is
generally done by copying features from Unix platforms into the Windows
operating system and into the tools themselves. Visual Studio 2008 is no
exception. The most significant security feature in Visual C++ 2008 (IMHO)
is secure package deployment and executable module manifests. This is nothing
less than the direct equivalent of RPATH's in Unix and Linux, and the usual
security features - and annoying issues - come along with it.
The Visual C++ 2008 runtime libraries include MSVCR90.DLL, MSVCP90.DLL and
MSVCM90.DLL, which represent the C standard library, the C++ standard
library, and the C math library, respectively. These libraries may no
longer be simply dropped into the same directory as your executable and
consumed. Executables and consumer DLL's need to be configured to build
with a manifest file (a default setting for new projects), and the runtime
libraries need to be "deployed". Deployment consists of running a
significant algorithm to determine platform requirements and features,
and making the right decisions to install these runtime libraries.
Developers (like you) will not have a problem executing your own
projects built against the FLAIM libraries because you've installed VC8,
which consumes the VC8 runtime libraries, and so deploys it during its
install process. For more information, see this excellent article on
the CodeProjects website:
http://www.codeproject.com/cpp/vcredists_x86.asp
Legacy Makefile
===============
There is also a legacy makefile (GNUMakefile) that has been hand written
to target flaim for all of the platforms that flaim currently supports. If you
don't want to use autotools, and you don't feel comfortable in the Visual C++
2008 IDE, then you may build for windows by simply running make from the root
of the FLAIM project. This makefile accepts multiple auxilliary targets, which
modify the build in various ways. These auxilliary targets include:
debug
release
32bit
64bit
verbose
usegcc
flm_dbg_log
True build targets include:
libs (default) - flaim libraries (static and dynamic)
checkdb - checkdb.exe
rebuild - rebuild.exe
view - view.exe
ut_basictest - basic unit tests
sample - sample.exe
CAVEAT: We're trying to phase out the legacy GNU makefile build system, so:
1) Don't expect it to last forever, and
2) Don't be surprised if it doesn't work all the time
Enjoy!

2
Makefile.am
View File

@@ -1,6 +1,6 @@
ACLOCAL_AMFLAGS = -I m4
EXTRA_DIST = tools win32
EXTRA_DIST = INSTALL.W32 tools win32
SUBDIRS = ftk flaim sql xflaim

88
flaim/INSTALL.W32
View File

@@ -1,46 +1,64 @@
Building on Windows
===================
Visual C++ 8.0 Express is good, but more to the point, it's free.
To build FLAIM, you will need to download and install VC8 Express and the
latest Windows Platform SDK, as VC8 Express only comes with .NET libraries.
You can get VC8 Express here:
Visual C++ 2008 Express is good, but more to the point, it's free.
To build the FLAIM projects, you will need to download and install
Visual C++ 2008 Express (which now thankfully comes with a reasonably
late version of the Windows Platform SDK).
http://msdn.microsoft.com/vstudio/express/visualC/default.aspx
You can get Visual C++ 2008 Express here:
Click the Download link on the right, and CAREFULLY follow steps 1 through
4 on that page. The 4th step links to a page that indicates how to install
the Windows Platform SDK. It looks painful, but it's really rather simple.
http://www.microsoft.com/express/vc
Once VC8 Express and the Platform SDK have been installed and configured
to work correctly with each other (and after the obligatory set of reboots),
you can simply double click on the flaim solution (flaim.sln) file to bring
up the flaim project in the VC8 IDE. Use the main or context menu options
The ">> Download Now!" link on that page, and decide whether you want to
install from the web (slow) or install off-line (also slow - there's no
fast solution, sorry).
Once Visual C++ 2008 Express has been installed you may simply double
click on any of the flaim project solution files to bring up the flaim
project in the Visual C++ 2008 IDE. Use the main or context menu options
to build the desired targets.
At some near future point, we hope to be able to build with autotools under
Cygwin. Of course, VC8 Express (or Professional) will still be required, but
at least the build process will be the same for all platforms.
The flaim project solution files are located in the win32 directories
in the following locations:
flaim-projects
flaim
win32 - flaim.sln
ftk
win32 - flaimtk.sln
sql
win32 - flaimsql.sln
xflaim
win32 - xflaim.sln
win32 - flaim-projects.sln
The projects may be build individually from each of the lower-level
solution files, or all at once from the flaim-projects solution file.
WARNING: The flaim-projects solution file refers to the same project
files as the individual lower-level solution files, so if you make
changes in one of these, they'll be reflected in the other.
FLAIM Runtime Library Use
=========================
FLAIM libraries - both static and dynamic - and the flaim utilities
consume the dynamic (DLL) form of the VC8 runtime libraries. This is in
alignment with the use of runtime libraries on Unix platforms. It's more
efficient and flexible to use the DLL versions of these libraries, and
it allows Microsoft to update these libraries as necessary to fix security
holes and defects which may be found in the future.
consume the dynamic (DLL) form of the Visual C++ 2008 runtime libraries.
This is in alignment with the use of runtime libraries on Unix platforms.
It's more efficient and flexible to use the DLL versions of these libraries,
and it allows Microsoft to update these libraries as necessary to fix
security holes and defects which may be found in the future.
With each new version of Windows and Microsoft tools, Microsoft
platforms become more security minded - and more secure. This is
generally done by copying features from Unix platforms into the Windows
operating system and into the tools themselves. Visual Studio 2005 is no
exception. The most significant security feature in VC8 (IMHO) is secure
package deployment and executable module manifests. This is nothing less
than the direct equivalent of RPATH's in Unix and Linux, and the usual
operating system and into the tools themselves. Visual Studio 2008 is no
exception. The most significant security feature in Visual C++ 2008 (IMHO)
is secure package deployment and executable module manifests. This is nothing
less than the direct equivalent of RPATH's in Unix and Linux, and the usual
security features - and annoying issues - come along with it.
The VC8 runtime libraries include MSVCR80.DLL, MSVCP80.DLL and
MSVCM80.DLL, which represent the C standard library, the C++ standard
The Visual C++ 2008 runtime libraries include MSVCR90.DLL, MSVCP90.DLL and
MSVCM90.DLL, which represent the C standard library, the C++ standard
library, and the C math library, respectively. These libraries may no
longer be simply dropped into the same directory as your executable and
consumed. Executables and consumer DLL's need to be configured to build
@@ -57,15 +75,14 @@ the CodeProjects website:
http://www.codeproject.com/cpp/vcredists_x86.asp
Legacy Makefile
===============
There is also a legacy makefile that has been hand written to target
flaim for all of the platforms that flaim currently supports. If you don't
want to use autotools, and you don't feel comfortable in the VC8 IDE, then
you may build for windows by simply running make from the root of the FLAIM
project. This makefile accepts multiple auxilliary targets, which modify
the build in various ways. These auxilliary targets include:
There is also a legacy makefile (GNUMakefile) that has been hand written
to target flaim for all of the platforms that flaim currently supports. If you
don't want to use autotools, and you don't feel comfortable in the Visual C++
2008 IDE, then you may build for windows by simply running make from the root
of the FLAIM project. This makefile accepts multiple auxilliary targets, which
modify the build in various ways. These auxilliary targets include:
debug
release
@@ -84,4 +101,9 @@ True build targets include:
ut_basictest - basic unit tests
sample - sample.exe
CAVEAT: We're trying to phase out the legacy GNU makefile build system, so:
1) Don't expect it to last forever, and
2) Don't be surprised if it doesn't work all the time
Enjoy!

2
flaim/Makefile.am
View File

@@ -1,6 +1,6 @@
ACLOCAL_AMFLAGS = -I m4
EXTRA_DIST = GNUMakefile debian netware win32
EXTRA_DIST = GNUMakefile INSTALL.W32 debian netware win32
SUBDIRS = $(subdirs) src util sample docs obs

109
ftk/INSTALL.W32 Normal file
View File

@@ -0,0 +1,109 @@
Building on Windows
===================
Visual C++ 2008 Express is good, but more to the point, it's free.
To build the FLAIM projects, you will need to download and install
Visual C++ 2008 Express (which now thankfully comes with a reasonably
late version of the Windows Platform SDK).
You can get Visual C++ 2008 Express here:
http://www.microsoft.com/express/vc
The ">> Download Now!" link on that page, and decide whether you want to
install from the web (slow) or install off-line (also slow - there's no
fast solution, sorry).
Once Visual C++ 2008 Express has been installed you may simply double
click on any of the flaim project solution files to bring up the flaim
project in the Visual C++ 2008 IDE. Use the main or context menu options
to build the desired targets.
The flaim project solution files are located in the win32 directories
in the following locations:
flaim-projects
flaim
win32 - flaim.sln
ftk
win32 - flaimtk.sln
sql
win32 - flaimsql.sln
xflaim
win32 - xflaim.sln
win32 - flaim-projects.sln
The projects may be build individually from each of the lower-level
solution files, or all at once from the flaim-projects solution file.
WARNING: The flaim-projects solution file refers to the same project
files as the individual lower-level solution files, so if you make
changes in one of these, they'll be reflected in the other.
FLAIM Runtime Library Use
=========================
FLAIM libraries - both static and dynamic - and the flaim utilities
consume the dynamic (DLL) form of the Visual C++ 2008 runtime libraries.
This is in alignment with the use of runtime libraries on Unix platforms.
It's more efficient and flexible to use the DLL versions of these libraries,
and it allows Microsoft to update these libraries as necessary to fix
security holes and defects which may be found in the future.
With each new version of Windows and Microsoft tools, Microsoft
platforms become more security minded - and more secure. This is
generally done by copying features from Unix platforms into the Windows
operating system and into the tools themselves. Visual Studio 2008 is no
exception. The most significant security feature in Visual C++ 2008 (IMHO)
is secure package deployment and executable module manifests. This is nothing
less than the direct equivalent of RPATH's in Unix and Linux, and the usual
security features - and annoying issues - come along with it.
The Visual C++ 2008 runtime libraries include MSVCR90.DLL, MSVCP90.DLL and
MSVCM90.DLL, which represent the C standard library, the C++ standard
library, and the C math library, respectively. These libraries may no
longer be simply dropped into the same directory as your executable and
consumed. Executables and consumer DLL's need to be configured to build
with a manifest file (a default setting for new projects), and the runtime
libraries need to be "deployed". Deployment consists of running a
significant algorithm to determine platform requirements and features,
and making the right decisions to install these runtime libraries.
Developers (like you) will not have a problem executing your own
projects built against the FLAIM libraries because you've installed VC8,
which consumes the VC8 runtime libraries, and so deploys it during its
install process. For more information, see this excellent article on
the CodeProjects website:
http://www.codeproject.com/cpp/vcredists_x86.asp
Legacy Makefile
===============
There is also a legacy makefile (GNUMakefile) that has been hand written
to target flaim for all of the platforms that flaim currently supports. If you
don't want to use autotools, and you don't feel comfortable in the Visual C++
2008 IDE, then you may build for windows by simply running make from the root
of the FLAIM project. This makefile accepts multiple auxilliary targets, which
modify the build in various ways. These auxilliary targets include:
debug
release
32bit
64bit
verbose
usegcc
flm_dbg_log
True build targets include:
libs (default) - flaim libraries (static and dynamic)
checkdb - checkdb.exe
rebuild - rebuild.exe
view - view.exe
ut_basictest - basic unit tests
sample - sample.exe
CAVEAT: We're trying to phase out the legacy GNU makefile build system, so:
1) Don't expect it to last forever, and
2) Don't be surprised if it doesn't work all the time
Enjoy!

2
ftk/Makefile.am
View File

@@ -1,6 +1,6 @@
ACLOCAL_AMFLAGS = -I m4
EXTRA_DIST = GNUMakefile debian netware win32
EXTRA_DIST = GNUMakefile INSTALL.W32 debian netware win32
SUBDIRS = src util obs

109
sql/INSTALL.W32 Normal file
View File

@@ -0,0 +1,109 @@
Building on Windows
===================
Visual C++ 2008 Express is good, but more to the point, it's free.
To build the FLAIM projects, you will need to download and install
Visual C++ 2008 Express (which now thankfully comes with a reasonably
late version of the Windows Platform SDK).
You can get Visual C++ 2008 Express here:
http://www.microsoft.com/express/vc
The ">> Download Now!" link on that page, and decide whether you want to
install from the web (slow) or install off-line (also slow - there's no
fast solution, sorry).
Once Visual C++ 2008 Express has been installed you may simply double
click on any of the flaim project solution files to bring up the flaim
project in the Visual C++ 2008 IDE. Use the main or context menu options
to build the desired targets.
The flaim project solution files are located in the win32 directories
in the following locations:
flaim-projects
flaim
win32 - flaim.sln
ftk
win32 - flaimtk.sln
sql
win32 - flaimsql.sln
xflaim
win32 - xflaim.sln
win32 - flaim-projects.sln
The projects may be build individually from each of the lower-level
solution files, or all at once from the flaim-projects solution file.
WARNING: The flaim-projects solution file refers to the same project
files as the individual lower-level solution files, so if you make
changes in one of these, they'll be reflected in the other.
FLAIM Runtime Library Use
=========================
FLAIM libraries - both static and dynamic - and the flaim utilities
consume the dynamic (DLL) form of the Visual C++ 2008 runtime libraries.
This is in alignment with the use of runtime libraries on Unix platforms.
It's more efficient and flexible to use the DLL versions of these libraries,
and it allows Microsoft to update these libraries as necessary to fix
security holes and defects which may be found in the future.
With each new version of Windows and Microsoft tools, Microsoft
platforms become more security minded - and more secure. This is
generally done by copying features from Unix platforms into the Windows
operating system and into the tools themselves. Visual Studio 2008 is no
exception. The most significant security feature in Visual C++ 2008 (IMHO)
is secure package deployment and executable module manifests. This is nothing
less than the direct equivalent of RPATH's in Unix and Linux, and the usual
security features - and annoying issues - come along with it.
The Visual C++ 2008 runtime libraries include MSVCR90.DLL, MSVCP90.DLL and
MSVCM90.DLL, which represent the C standard library, the C++ standard
library, and the C math library, respectively. These libraries may no
longer be simply dropped into the same directory as your executable and
consumed. Executables and consumer DLL's need to be configured to build
with a manifest file (a default setting for new projects), and the runtime
libraries need to be "deployed". Deployment consists of running a
significant algorithm to determine platform requirements and features,
and making the right decisions to install these runtime libraries.
Developers (like you) will not have a problem executing your own
projects built against the FLAIM libraries because you've installed VC8,
which consumes the VC8 runtime libraries, and so deploys it during its
install process. For more information, see this excellent article on
the CodeProjects website:
http://www.codeproject.com/cpp/vcredists_x86.asp
Legacy Makefile
===============
There is also a legacy makefile (GNUMakefile) that has been hand written
to target flaim for all of the platforms that flaim currently supports. If you
don't want to use autotools, and you don't feel comfortable in the Visual C++
2008 IDE, then you may build for windows by simply running make from the root
of the FLAIM project. This makefile accepts multiple auxilliary targets, which
modify the build in various ways. These auxilliary targets include:
debug
release
32bit
64bit
verbose
usegcc
flm_dbg_log
True build targets include:
libs (default) - flaim libraries (static and dynamic)
checkdb - checkdb.exe
rebuild - rebuild.exe
view - view.exe
ut_basictest - basic unit tests
sample - sample.exe
CAVEAT: We're trying to phase out the legacy GNU makefile build system, so:
1) Don't expect it to last forever, and
2) Don't be surprised if it doesn't work all the time
Enjoy!

2
sql/Makefile.am
View File

@@ -1,6 +1,6 @@
ACLOCAL_AMFLAGS = -I m4
EXTRA_DIST = GNUMakefile win32
EXTRA_DIST = GNUMakefile INSTALL.W32 win32
SUBDIRS = $(subdirs) src obs

96
xflaim/INSTALL.W32
View File

@@ -1,46 +1,64 @@
Building on Windows
===================
Visual C++ 8.0 Express is good, but more to the point, it's free.
To build XFLAIM, you will need to download and install VC8 Express and the
latest Windows Platform SDK, as VC8 Express only comes with .NET libraries.
You can get VC8 Express here:
Visual C++ 2008 Express is good, but more to the point, it's free.
To build the FLAIM projects, you will need to download and install
Visual C++ 2008 Express (which now thankfully comes with a reasonably
late version of the Windows Platform SDK).
http://msdn.microsoft.com/vstudio/express/visualC/default.aspx
You can get Visual C++ 2008 Express here:
Click the Download link on the right, and CAREFULLY follow steps 1 through
4 on that page. The 4th step links to a page that indicates how to install
the Windows Platform SDK. It looks painful, but it's really rather simple.
http://www.microsoft.com/express/vc
Once VC8 Express and the Platform SDK have been installed and configured
to work correctly with each other (and after the obligatory set of reboots),
you can simply double click on the xflaim solution (xflaim.sln) file to bring
up the xflaim project in the VC8 IDE. Use the main or context menu options
The ">> Download Now!" link on that page, and decide whether you want to
install from the web (slow) or install off-line (also slow - there's no
fast solution, sorry).
Once Visual C++ 2008 Express has been installed you may simply double
click on any of the flaim project solution files to bring up the flaim
project in the Visual C++ 2008 IDE. Use the main or context menu options
to build the desired targets.
At some near future point, we hope to be able to build with autotools under
Cygwin. Of course, VC8 Express (or Professional) will still be required, but
at least the build process will be the same for all platforms.
The flaim project solution files are located in the win32 directories
in the following locations:
XFLAIM Runtime Library Use
flaim-projects
flaim
win32 - flaim.sln
ftk
win32 - flaimtk.sln
sql
win32 - flaimsql.sln
xflaim
win32 - xflaim.sln
win32 - flaim-projects.sln
The projects may be build individually from each of the lower-level
solution files, or all at once from the flaim-projects solution file.
WARNING: The flaim-projects solution file refers to the same project
files as the individual lower-level solution files, so if you make
changes in one of these, they'll be reflected in the other.
FLAIM Runtime Library Use
=========================
XFLAIM libraries - both static and dynamic - and the xflaim utilities
consume the dynamic (DLL) form of the VC8 runtime libraries. This is in
alignment with the use of runtime libraries on Unix platforms. It's more
efficient and flexible to use the DLL versions of these libraries, and
it allows Microsoft to update these libraries as necessary to fix security
holes and defects which may be found in the future.
FLAIM libraries - both static and dynamic - and the flaim utilities
consume the dynamic (DLL) form of the Visual C++ 2008 runtime libraries.
This is in alignment with the use of runtime libraries on Unix platforms.
It's more efficient and flexible to use the DLL versions of these libraries,
and it allows Microsoft to update these libraries as necessary to fix
security holes and defects which may be found in the future.
With each new version of Windows and Microsoft tools, Microsoft
platforms become more security minded - and more secure. This is
generally done by copying features from Unix platforms into the Windows
operating system and into the tools themselves. Visual Studio 2005 is no
exception. The most significant security feature in VC8 (IMHO) is secure
package deployment and executable module manifests. This is nothing less
than the direct equivalent of RPATH's in Unix and Linux, and the usual
operating system and into the tools themselves. Visual Studio 2008 is no
exception. The most significant security feature in Visual C++ 2008 (IMHO)
is secure package deployment and executable module manifests. This is nothing
less than the direct equivalent of RPATH's in Unix and Linux, and the usual
security features - and annoying issues - come along with it.
The VC8 runtime libraries include MSVCR80.DLL, MSVCP80.DLL and
MSVCM80.DLL, which represent the C standard library, the C++ standard
The Visual C++ 2008 runtime libraries include MSVCR90.DLL, MSVCP90.DLL and
MSVCM90.DLL, which represent the C standard library, the C++ standard
library, and the C math library, respectively. These libraries may no
longer be simply dropped into the same directory as your executable and
consumed. Executables and consumer DLL's need to be configured to build
@@ -50,22 +68,21 @@ significant algorithm to determine platform requirements and features,
and making the right decisions to install these runtime libraries.
Developers (like you) will not have a problem executing your own
projects built against the XFLAIM libraries because you've installed VC8,
projects built against the FLAIM libraries because you've installed VC8,
which consumes the VC8 runtime libraries, and so deploys it during its
install process. For more information, see this excellent article on
the CodeProjects website:
http://www.codeproject.com/cpp/vcredists_x86.asp
Legacy Makefile
===============
There is also a legacy makefile that has been hand written to target
xflaim for all of the platforms that xflaim currently supports. If you don't
want to use autotools, and you don't feel comfortable in the VC8 IDE, then
you may build for windows by simply running make from the root of the XFLAIM
project. This makefile accepts multiple auxilliary targets, which modify
the build in various ways. These auxilliary targets include:
There is also a legacy makefile (GNUMakefile) that has been hand written
to target flaim for all of the platforms that flaim currently supports. If you
don't want to use autotools, and you don't feel comfortable in the Visual C++
2008 IDE, then you may build for windows by simply running make from the root
of the FLAIM project. This makefile accepts multiple auxilliary targets, which
modify the build in various ways. These auxilliary targets include:
debug
release
@@ -77,11 +94,16 @@ the build in various ways. These auxilliary targets include:
True build targets include:
libs (default) - xflaim libraries (static and dynamic)
libs (default) - flaim libraries (static and dynamic)
checkdb - checkdb.exe
rebuild - rebuild.exe
view - view.exe
ut_basictest - basic unit tests
sample - sample.exe
CAVEAT: We're trying to phase out the legacy GNU makefile build system, so:
1) Don't expect it to last forever, and
2) Don't be surprised if it doesn't work all the time
Enjoy!