aboutsummaryrefslogtreecommitdiffstats
path: root/fbench/INSTALL
blob: 2bbd9fb9fc2663390ef770500f754195462a4bd2 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
******************
* fbench INSTALL *
******************

fbench uses 'FastOS'. In the following instructions, let %FASTOS_DIR%
denote the install directory for FastOS, also let %FBENCH_DIR% denote
the install directory for fbench. A resonable selection of install
directories would be:
  %FASTOS_DIR% = '/usr/fastsearch/fastos'
  %FBENCH_DIR% = '/usr/fastsearch/fbench'

Install FastOS:
- checkout the fastos CVS module
- go to fastos/src/fastos
- ./configure --install-dir %FASTOS_DIR% [<config parameters>]
  (run ./configure --help for help)
- make install

Install fbench:
- checkout the fbench CVS module
- go to fbench/src
- ./configure --fastos-dir %FASTOS_DIR% \
              --install-dir %FBENCH_DIR% [<config parameters>]
  (run ./configure --fastos-dir %FASTOS_DIR% --help for help)
- make install

This will install all needed binaries and scripts into
%FBENCH_DIR%/bin. It will also copy the README file into
%FBENCH_DIR%. The README file contains a step by step description of
how to perform benchmarking.

NOTE: When building on Win32, FastOS may have trouble resolving paths
to directories that do not exist; If you want to use a relative path
as install directory, Win32 users must create the install directory
before running the configure script in the fbench directory.