Balluff mvHYPERION Series, Техническое руководство

Страница: 24 / 94

20
Note
Please declare the device e.g. HC
∗
or HC000000001
cd my_directory
LD_LIBRARY_PATH=‘pwd‘/lib/x86 apps/SingleCapture/x86/SingleCapture HC*
For 64-bit it will look like this...
LD_LIBRARY_PATH=‘pwd‘/lib/x86_64 apps/SingleCapture/x86_64/SingleCapture HC*
For ARM it will look like this...
LD_LIBRARY_PATH=‘pwd‘/lib/arm apps/SingleCapture/arm/SingleCapture HC*
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:
• install the wxWidget 3.x development files (headers etc.) supplied for your distribution. (See "Other
requirements" above).
• fetch, compile and install the wxWidget 3.x packet from source downloaded from the website (
http://www.wxwidgets.org ).
• alter the Makefiles so as to find the wxWidget configuration script called wx-config.
The files you may need to alter are to be found here:
apps/mvPropView/Makefile.inc
You will find the compiled test programs in the subdirectories
"apps/.../x86"
. For 64 bit systems
it will be
"apps/.../x86_64"
. For ARM systems it will be
"apps/.../arm"
.
If you cannot build the wxWidget test program you should, at least, be able to compile the text-based
test programs in
apps/SingleCapture , apps/SingleCapture , etc.
The Makefile will also attempt to configure itself so that the mvHYPERION kernel module can be built.
You should see the following message at the end of the compile block:
=============================================================
To install the mvHYPERION kernel module now make sure that you are root and type:
make install
=============================================================
If you are not already logged in as the "root" user you must now use "su" to change users and type
"make install" . On an Ubuntu system you might try "sudo make install" . The kernel
module will now be built and installed.
Now you will have to tell your system to use this kernel module and to associate it with a device
node. To do this you need to edit the file
"/etc/modprobe.conf"
. Depending on your system
you may have a directory called
"/etc/modules.d/"
, where you can put files that are included
automatically in
"/etc/modprobe.conf"
. Other systems (e.g. older SuSE) use a file called
"/etc/modprobe.conf.local" which the user may alter. Which ever way you do it, you need
to add some lines like this:
alias char-major-64 hyperion
options hyperion major_dev_num=64
Afterwards, please use
"depmod -a"
to tell the system about this change. The lines above tell the
system to use a device called
"/dev/hyperion"
with a major number of 64.
(d) If you are using a system with an up-to-date version of udev you might be interested in the file "
←
-
Scripts/50-udev-hyperion.rules". By including this file in your udev rules directory you can tell your
system to create a device node for the mvHYPERION automatically when loading the kernel module.
← -
You will need to edit the file to fit your system. As delivered, all entries are commented out.
If you do not use udev then you will have to create a device node yourself by hand. For example, you
could do the following to use major device number 64:
mknod /dev/hyperion c 64 0
MATRIX VISION GmbH