7.2 Linux 35
3. You can now install the mvBlueFOX libraries as follows:
• create a new directory somewhere on your system.
• copy the correct mvbluefox package file to this directory and change into this directory with "cd".
The mvBlueFOX libraries are supplied as a "tgz" archive with the extension ".tgz". The older
"autopackage" format is now deprecated since it cannot handle 64-bit libraries.
(a) Unpack the archive using "tar" e.g.:
tar xvzf mvBlueFOX-x86_ABI2-1.12.45.tgz
Note
Current versions of the ABI1 libraries were compiled using a SuSE 8.1 system for maximum com-
patibility with older Linux distributions. These libraries should work with all SuSE 8.x and SuSE
9.x versions as well as with Debian Sarge and older Red Hat / Fedora variants.
Current versions of the ABI2 libraries were compiled using a SuSE 10.1 system for maximum
compatibility with newer Linux distributions. These libraries should work with SuSE 10.x as well
as with Ubuntu 6.06 or newer, with up-to-date Gentoo or Fedora FC5.
(b) After installing the mvBlueFOX access libraries you will see something like the following directory struc-
ture in your directory (dates and file sizes will differ from the list below):
drwxr-xr-x 10 root root 4096 Jan 5 15:08 .
drwxr-xr-x 23 root root 4096 Jan 4 16:33 ..
drwxr-xr-x 3 root root 4096 Jan 5 15:08 DriverBase
-rw-r--r-- 1 root root 1079 Jan 5 15:08 Makefile
drwxr-xr-x 7 root root 4096 Jan 5 15:08 apps
drwxr-xr-x 4 root root 4096 Jan 5 15:08 common
drwxr-xr-x 3 root root 4096 Jan 5 15:08 lib
drwxr-xr-x 3 root root 4096 Jan 5 15:08 mvDeviceManager
drwxr-xr-x 2 root root 4096 Jan 5 15:08 mvIMPACT_CPP
drwxr-xr-x 3 root root 4096 Jan 5 15:08 mvPropHandling
drwxr-xr-x 1 root root 4096 Jan 5 15:08 scripts
The directory "lib/x86" contains the pre-compiled 32-bit libraries for accessing the mvBlueFOX.
If 64-bit libraries are supplied, they will be found in "lib/x86_64". The "apps" directory contains test
applications (source code). The other directories contain headers needed to write applications for the
mvBlueFOX.
Since the libraries are not installed to a directory known to the system i.e. not in the "ldconfig"
cache you will need to tell the system where to find them by...
• using the "LD_LIBRARY_PATH" environment variable,
• or copying the libraries by hand to a system directory like "/usr/lib" (or using some symbolic
links),
• or entering the directory in "/etc/ld.so.conf" and running "ldconfig".
e.g. to start the application called "LiveSnap":
Note
Please declare the device e.g. BF∗ or BF00001
cd my_mvbf_directory
LD_LIBRARY_PATH=‘pwd‘/lib/x86 apps/LiveSnap/x86/LiveSnap BF
*
For 64-bit it will look like this...
LD_LIBRARY_PATH=‘pwd‘/lib/x86_64 apps/LiveSnap/x86_64/LiveSnap BF
*
For ARM it will look like this...
LD_LIBRARY_PATH=‘pwd‘/lib/arm apps/LiveSnap/arm/LiveSnap BF
*
etc.
After installing the libraries and headers you may continue with "3." below as a normal user i.e. you do
not need to be "root" in order to compile the test applications. See also the note "4." below.
(c) To build the test applications type "make". This will attempt to build all the test applications contained
in "apps". If you have problems compiling the wxWidget library or application you may need to do one
or more of the following:
MATRIX VISION GmbH
To Next Page
Loading...
