Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Aptina Apbase Library Setup in MacOSX
Build/Test environments
MacOS 10.7, 10.8 and 10.9
Required run-time libraries
• libusb-1.0 (libusb website: www.libusb.org)

  • To download from MacOS (with Macports): 'sudo port install libusb'

• libtbb ( please check: http://www.threadingbuildingblocks.org).
• libpython3.3
To install Python library for MacOS Users:
Download the Mac dmg file from http://www.python.org/download/
(Note: MacOS default set to version 2.7. Remember create a symbolic link for libpython3.3m.dylib)
(e.g. sudo ln –s /Library/Frameworks/Python.framework/Versions/3.3/Python /usr/lib/libpython3.3m.dylib)
Optional developer libraries
• Qt Framework (Please check: qt-project.org for details).
Installation Instructions
Apbase Platform Setup Instructions:
• Download and run the Aptina DevSuite installer (Website: ????????).
• The libapbase and libmidlib2 library files for MacOS developer are installed in the "/Aptina_Imaging_Dev/" directory.
• The two library files in "/Aptina_Imaging_Dev/lib/" are for DevWareX Plug-in only, NOT for developer use.
• Verify the libusb, libtbb and libpython.3.3m run time library files are installed in the Mac.
Note: Aptina apbase and midlib2 libraries use LibUSB 1.0.9. It is bundled in the DevWareX.app.
Aptina DevWareX Directory Structure:
– /Aptina_Imaging_Dev/apps_data - contains Aptina sensor setting (.ini) files for the different supported sensors.
– /Aptina_Imaging_Dev /board_data - contains Aptina Demo boards (.cdat) files.
– /Aptina_Imaging_Dev /sensor_data - contains the Aptina sensor data (.sdat/.xsdat) files.
– /Aptina_Imaging_Dev /lib - contains Aptina shared object (.dylib) files for the DevWareX Plug-ins.
– /Aptina_Imaging_Dev /include - contains apbase and midlib2 C/C++ header (.h) files.
– /Aptina_Imaging_Dev /samples - contains C/Qt sample files which use Aptina apbase and midlib2 libraries.
Note: Please keep the same directory structure. Apbase use relative directory to search the data files if user does not specify the sensor data file in the code.
Required files in data directories: "sensor_data", "apps_data" and "board_data"
Test Application (SimpleQt) Build Instructions
./samples/SimpleQt/ is a sample test program that opens Aptina Demo kits and sensors, initializes it and display captured images. User needs Administrator account to access the USB devices. (sudo ./SimpleQt).

  • To build SimpleQt in Maco: Modify the SimpleQt.pro file and use qmake/make from the command-line. Please read Qt document (qt-project.org) for more information.
    The two .dylib files required for SimpleQt are:
    libmidlib2.dylib and libapbase.dylib.
    Note:
    1. Type 'export LD_LIBRARY_PATH=SimpleQt_directory' before execute the binary.
    2. Modify the SimpleQt.pro file based on your Mac System.
    3. The libmidlib2.dylib and libapbase.dylib files user should use is in the "/Aptina_Imaging_Dev/" not "/Aptina_Imaging_Dev/lib/" directory.
    4. If user wants to create bundled apps, please check MacOS developer document for how to change the library path in the library files.
    Test Application (SimpleCapture) Build Instructions
    ./samples/SimpleCapture/ is a sample test program that opens Aptina Demo kits and sensors, initializes it, captures one or more frames, save it and exists. User needs Admin right to access the USB devices. (sudo ./SimpleCapture).
  • To build SimpleCapture in MacOS:
    1. Modify SimpleCapture.cpp for the target sensor.
    2. Modify makefile.mac with the location of the apbase, midlib2 libraries and include files.
    3. Make sure the correct sensor data file (.xsdat file) is in the "/sensor_data/" directory and an INI file in the "/apps_data/" directory. Or user can specify the file locations in the C code.
    4. Create a section in the application to make sensor specific register calls if it is required.
    5. Build the test application by typing 'make -f makefile.mac'.
    6. Execute by typing 'sudo ./SimpleCapture'
    Note: SimpleCapture will capture a frame and store it in a file (something like img.raw).
  • No labels