search

basler / pypylon

The official python wrapper for the pylon Camera Software Suite
http://www.baslerweb.com
BSD 3-Clause "New" or "Revised" License
565 stars 207 forks source link

Is it possible to cross compile pypylon. #428

Closed octonout closed 3 years ago

octonout commented 3 years ago

We want to add pypylon to our custom Yocto image for Jetson Nano.

On the Jetson Nano running the custom Yocto image, with pip version greater than 20.3, it is possible to install pypylon. But this is runtime installation. And we would rather have it added to the image at build time. To do so we will have to cross compile it via the Yocto build system.

From the readme these seem to be the build time dependencies:

You need a few more things to compile pypylon:

    - A compiler for your system (Visual Studio on Windows, gcc on linux)
    - Python development files (e.g. sudo apt install python-dev on linux)
    - swig >= 4.0

I can provide these on the Yocto build system. What else would be required to cross compile?

stefanklug commented 3 years ago

Hi @octonout ,

we include pypylon in the yocto layers for our embedded cameras. These should be easy to adopt for your usecase. The code is pretty simple: python3-pypylon_1.7.1.bb

LICENSE = "BSD-3-Clause"
LIC_FILES_CHKSUM = "file://LICENSE;md5=5209c60dd8406ab83075514af62800b6"

SUMMARY = "Python 3 bindings for pylon"

PR = "r0"

inherit setuptools3

# Github source drive
SRC_URI = "git://github.com/basler/pypylon.git;protocol=https"
SRCREV = "95d71195e9764c2179939bf674753111afa800ba"
S = "${WORKDIR}/git"

DEPENDS = "pylon python3 swig-native python3-setuptools-native"
RDEPENDS_${PN} = "python3-numpy"
INSANE_SKIP_${PN} += "already-stripped"

export PYLON_ROOT = "${WORKDIR}/recipe-sysroot/opt/pylon"

This assumes that you installed pylon before. The receipe is similar: pylon_6.2.0.bb

SUMMARY = "Basler pylon Camera Software Suite"
DESCRIPTION = "A software package comprised of an easy-to-use SDK and tools that you can use to operate any Basler camera."
LICENSE = "pylon & LGPLv3 & LGPLv2.1 & BSD-3-Clause & BSD-2-Clause & bzip2 & Libpng & Zlib & GenICam-1.1 & NI & xxHash & Apache-2.0"
LIC_FILES_CHKSUM = "file://share/pylon/licenses/License.html;md5=6a23d6496f15e590f32b3d3954297683 \
                    file://share/pylon/licenses/pylon_Third-Party_Licenses.html;md5=3ed299ffc665be3cebd634d25a41de80"

PR = "r0"

SRC_URI = "file://pylon_6.2.0.21487_aarch64.tar.gz;subdir=${S}"

RDEPENDS_${PN} = "fontconfig freetype libsm libdrm libxcb-glx"

FILES_${PN} += "/opt/ /usr/bin/pylon"

INSANE_SKIP_${PN} += "already-stripped"
INSANE_SKIP_${PN} += "dev-so"
INSANE_SKIP_${PN} += "dev-elf"

# Work around for RDEPENDS to avoid 'no libGL.so.1()(64bit) provider found' problem
SKIP_FILEDEPS_${PN} = "1"

# Without this option yocto checks every .so included in pylon and treats it as possible RPROVIDES.
# This lead to spurious dependencies of gstreamer packages on pylon.
EXCLUDE_FROM_SHLIBS = "1"

# We want the complete pylon inside the sysroot to be able to build against it
SYSROOT_DIRS = "/opt"

PACKAGES_${PN} = "${PN}"

do_install() {
    # Copy the contents of the source folder (pylon folder) to opt folder
    install -d "${D}/opt/pylon"
    cp -dR --preserve=mode,links,timestamps --no-preserve=ownership "${S}"/* "${D}/opt/pylon/"
}

Best regards, Stefan

lemmi25 commented 2 years ago

Hi Stefan,

many thanks for sharing your receipes. I tried what you did. To install pylon on my RPI4.

Unfortunately I get this error (when I run bitbake core-image-minimal):

ERROR: python3-pylon-0.1-r0 do_populate_sysroot: Fatal errors occurred in subprocesses:
Command '['arm-poky-linux-gnueabi-strip', '--remove-section=.comment', '--remove-section=.note', '/home/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-pylon/0.1-r0/sysroot-destdir/opt/pylon/bin/pylonviewer']' returned non-zero exit status 1.
Subprocess output:arm-poky-linux-gnueabi-strip: /home/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-pylon/0.1-r0/sysroot-destdir/opt/pylon/bin/pylonviewer: file format not recognized
Command '['arm-poky-linux-gnueabi-strip', '--remove-section=.comment', '--remove-section=.note', '/home/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-pylon/0.1-r0/sysroot-destdir/opt/pylon/bin/ipconfigurator']' returned non-zero exit status 1.
Subprocess output:arm-poky-linux-gnueabi-strip: /home/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-pylon/0.1-r0/sysroot-destdir/opt/pylon/bin/ipconfigurator: file format not recognized

ERROR: Logfile of failure stored in: /home/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-pylon/0.1-r0/temp/log.do_populate_sysroot.75656
ERROR: Task (/home/custom-layer/meta-custom-python/recipes-python/python/python3-pylon_0.1.bb:do_populate_sysroot) failed with exit code '1'
ERROR: python3-pylon-0.1-r0 do_package: Fatal errors occurred in subprocesses:
Command '['arm-poky-linux-gnueabi-objcopy', '--only-keep-debug', '/home/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-pylon/0.1-r0/package/opt/pylon/bin/pylonviewer', '/home/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-pylon/0.1-r0/package/opt/pylon/bin/.debug/pylonviewer']' returned non-zero exit status 1.
Subprocess output:arm-poky-linux-gnueabi-objcopy: /home/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-pylon/0.1-r0/package/opt/pylon/bin/pylonviewer: file format not recognized
Command '['arm-poky-linux-gnueabi-objcopy', '--only-keep-debug', '/home/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-pylon/0.1-r0/package/opt/pylon/bin/ipconfigurator', '/home/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-pylon/0.1-r0/package/opt/pylon/bin/.debug/ipconfigurator']' returned non-zero exit status 1.
Subprocess output:arm-poky-linux-gnueabi-objcopy: /home/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-pylon/0.1-r0/package/opt/pylon/bin/ipconfigurator: file format not recognized

ERROR: Logfile of failure stored in: /home/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-pylon/0.1-r0/temp/log.do_package.75655
ERROR: Task (/home/custom-layer/meta-custom-python/recipes-python/python/python3-pylon_0.1.bb:do_package) failed with exit code '1'

I have the exact same pylon version. The only thing I changed is the name of the receipe to python3-pylon_0.1.bb

I am using hardnott.

Maybe you can help me and make sense of this error?

Many thanks

Moritz

stefanklug commented 2 years ago

Hi Moritz,

did you use the correct pylon binaries? My receipe referenced the aarch64 pylon tarball. But it looks as if you are building for 32 bit arm (which is often used on the RPi). One thing that looks a bit strange: Your toolchain prefix is arm-poky-linux-gnueabi- which suggests a softfloat ABI. pylon 32bit is only available for hardfloat ABI/armhf (Which is also the better choice for your RPi4). You should double check your expected ABI settings.

Best regards, Stefan

lemmi25 commented 2 years ago

Hi Stefan,

I checked my binaries and I am using this version (tried both):

pylon_6.1.3.20159_aarch64.tar.gz pylon_6.2.0.21487_aarch64.tar.gz

The recipe looks like this:

SUMMARY = "Basler pylon Camera Software Suite"
DESCRIPTION = "A software package comprised of an easy-to-use SDK and tools that you can use to operate any Basler camera."

LICENSE = "pylon & LGPLv3 & LGPLv2.1 & BSD-3-Clause & BSD-2-Clause & bzip2 & Libpng & Zlib & GenICam-1.1 & NI & xxHash & Apache-2.0"
LIC_FILES_CHKSUM = "file://share/pylon/licenses/License.html;md5=6a23d6496f15e590f32b3d3954297683 \
                    file://share/pylon/licenses/pylon_Third-Party_Licenses.html;md5=3ed299ffc665be3cebd634d25a41de80"

PR = "r0"

SRC_URI = "file://pylon_6.1.3.20159_aarch64.tar.gz;subdir=${S}"

RDEPENDS_${PN} = "fontconfig freetype libsm libdrm libxcb-glx"

FILES_${PN} += "/opt/ /usr/bin/pylon"

INSANE_SKIP_${PN} += "already-stripped"
INSANE_SKIP_${PN} += "dev-so"
INSANE_SKIP_${PN} += "dev-elf"

# Work around for RDEPENDS to avoid 'no libGL.so.1()(64bit) provider found' problem
SKIP_FILEDEPS_${PN} = "1"

# Without this option yocto checks every .so included in pylon and treats it as possible RPROVIDES.
# This lead to spurious dependencies of gstreamer packages on pylon.
EXCLUDE_FROM_SHLIBS = "1"

# We want the complete pylon inside the sysroot to be able to build against it
SYSROOT_DIRS = "/opt"

PACKAGES_${PN} = "${PN}"

do_install() {
    # Copy the contents of the source folder (pylon folder) to opt folder
    install -d "${D}/opt/pylon"
    cp -dR --preserve=mode,links,timestamps --no-preserve=ownership "${S}"/* "${D}/opt/pylon/"

    # Create a script file which sets automatically the GENICAM_GENTL64_PATH env variable before it starts the pylon viewer.
    install -d "${D}/usr/bin"
    echo '#!/bin/sh' >"${D}"/usr/bin/pylon
    echo 'GENICAM_GENTL64_PATH=/opt/dart-bcon-mipi/lib exec /opt/pylon/bin/pylonviewer "${@}"' >>"${D}"/usr/bin/pylon
    chmod 755 "${D}"/usr/bin/pylon
}

SUMMARY = "Basler pylon Camera Software Suite"
DESCRIPTION = "A software package comprised of an easy-to-use SDK and tools that you can use to operate any Basler camera."
LICENSE = "pylon & LGPLv3 & LGPLv2.1 & BSD-3-Clause & BSD-2-Clause & bzip2 & Libpng & Zlib & GenICam-1.1 & NI & xxHash & Apache-2.0"
LIC_FILES_CHKSUM = "file://share/pylon/licenses/License.html;md5=6a23d6496f15e590f32b3d3954297683 \
                    file://share/pylon/licenses/pylon_Third-Party_Licenses.html;md5=3ed299ffc665be3cebd634d25a41de80"

PR = "r0"

SRC_URI = "file://pylon_6.2.0.21487_aarch64.tar.gz;subdir=${S}"

RDEPENDS_${PN} = "fontconfig freetype libsm libdrm libxcb-glx"

FILES_${PN} += "/opt/ /usr/bin/pylon"

INSANE_SKIP_${PN} += "already-stripped"
INSANE_SKIP_${PN} += "dev-so"
INSANE_SKIP_${PN} += "dev-elf"

# Work around for RDEPENDS to avoid 'no libGL.so.1()(64bit) provider found' problem
SKIP_FILEDEPS_${PN} = "1"

# Without this option yocto checks every .so included in pylon and treats it as possible RPROVIDES.
# This lead to spurious dependencies of gstreamer packages on pylon.
EXCLUDE_FROM_SHLIBS = "1"

# We want the complete pylon inside the sysroot to be able to build against it
SYSROOT_DIRS = "/opt"

PACKAGES_${PN} = "${PN}"

do_install() {
    # Copy the contents of the source folder (pylon folder) to opt folder
    install -d "${D}/opt/pylon"
    cp -dR --preserve=mode,links,timestamps --no-preserve=ownership "${S}"/* "${D}/opt/pylon/"
}

I think this is the correct version right?

My local.config looks like this (maybe I am missing something?):

#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling
# the option is a question of removing the # character and making any change to the
# variable as required.

#
# Machine Selection
#
# You need to select a specific machine to target the build with. There are a selection
# of emulated machines available which can boot and run in the QEMU emulator:
#
#MACHINE ?= "qemuarm"
#MACHINE ?= "qemuarm64"
#MACHINE ?= "qemumips"
#MACHINE ?= "qemumips64"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"
#
# There are also the following hardware board target machines included for 
# demonstration purposes:
#
#MACHINE ?= "beaglebone-yocto"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "edgerouter"
#
# This sets the default machine to be qemux86-64 if no other machine is selected:
MACHINE ??= "raspberrypi4"
ENABLE_UART = "1"

# Make faster
BB_NUMBER_THREADS = '12'
PARALLEL_MAKE = '-j 12'

# useful software
CORE_IMAGE_EXTRA_INSTALL += "htop openssh openssh-sftp openssh-sftp-server python3-pip python3-lxml python3-opencv python3-grpcio fontconfig freetype libsm libdrm libxcb-glx swig bash"

#IMAGE_INSTALL += ""

IMAGE_INSTALL_append = " python3 python3-flask python3-numpy python3-pylon hellosystemd"

# Add new user : pi/raspberry
# change password of root into root

EXTRA_USERS_PARAMS = " useradd robot; \
                       usermod  -p 'robot' robot; \
                       usermod  -a -G sudo robot;"

DISTRO_FEATURES_append = " systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"

#
# Where to place downloads
#
# During a first build the system will download many different source code tarballs
# from various upstream projects. This can take a while, particularly if your network
# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This directory
# is safe to share between multiple builds on the same machine too.
#
# The default is a downloads directory under TOPDIR which is the build directory.
#
#DL_DIR ?= "${TOPDIR}/downloads"

#
# Where to place shared-state files
#
# BitBake has the capability to accelerate builds based on previously built output.
# This is done using "shared state" files which can be thought of as cache objects
# and this option determines where those files are placed.
#
# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
# from these files if no changes were made to the configuration. If changes were made
# to the configuration, only shared state files where the state was still valid would
# be used (done using checksums).
#
# The default is a sstate-cache directory under TOPDIR.
#
#SSTATE_DIR ?= "${TOPDIR}/sstate-cache"

#
# Where to place the build output
#
# This option specifies where the bulk of the building work should be done and
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
#
# The default is a tmp directory under TOPDIR.
#
#TMPDIR = "${TOPDIR}/tmp"

#
# Default policy config
#
# The distribution setting controls which policy settings are used as defaults.
# The default value is fine for general Yocto project use, at least initially.
# Ultimately when creating custom policy, people will likely end up subclassing 
# these defaults.
#
DISTRO ?= "poky"
# As an example of a subclass there is a "bleeding" edge policy configuration
# where many versions are set to the absolute latest code from the upstream 
# source control systems. This is just mentioned here as an example, its not
# useful to most new users.
# DISTRO ?= "poky-bleeding"

#
# Package Management configuration
#
# This variable lists which packaging formats to enable. Multiple package backends
# can be enabled at once and the first item listed in the variable will be used
# to generate the root filesystems.
# Options are:
#  - 'package_deb' for debian style deb files
#  - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
#  - 'package_rpm' for rpm style packages
# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
# We default to rpm:
PACKAGE_CLASSES ?= "package_rpm"

#
# SDK target architecture
#
# This variable specifies the architecture to build SDK items for and means
# you can build the SDK packages for architectures other than the machine you are
# running the build on (i.e. building i686 packages on an x86_64 host).
# Supported values are i686, x86_64, aarch64
#SDKMACHINE ?= "i686"

#
# Extra image configuration defaults
#
# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
# images. Some of these options are added to certain image types automatically. The
# variable can contain the following options:
#  "dbg-pkgs"       - add -dbg packages for all installed packages
#                     (adds symbol information for debugging/profiling)
#  "src-pkgs"       - add -src packages for all installed packages
#                     (adds source code for debugging)
#  "dev-pkgs"       - add -dev packages for all installed packages
#                     (useful if you want to develop against libs in the image)
#  "ptest-pkgs"     - add -ptest packages for all ptest-enabled packages
#                     (useful if you want to run the package test suites)
#  "tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)
#  "tools-debug"    - add debugging tools (gdb, strace)
#  "eclipse-debug"  - add Eclipse remote debugging support
#  "tools-profile"  - add profiling tools (oprofile, lttng, valgrind)
#  "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
#  "debug-tweaks"   - make an image suitable for development
#                     e.g. ssh root access has a blank password
# There are other application targets that can be used here too, see
# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
# We default to enabling the debugging tweaks.
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"

#
# Additional image features
#
# The following is a list of additional classes to use when building images which
# enable extra features. Some available options which can be included in this variable
# are:
#   - 'buildstats' collect build statistics
#   - 'image-mklibs' to reduce shared library files size for an image
#   - 'image-prelink' in order to prelink the filesystem image
# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
USER_CLASSES ?= "buildstats image-mklibs image-prelink"

#
# Runtime testing of images
#
# The build system can test booting virtual machine images under qemu (an emulator)
# after any root filesystems are created and run tests against those images. It can also
# run tests against any SDK that are built. To enable this uncomment these lines.
# See classes/test{image,sdk}.bbclass for further details.
#IMAGE_CLASSES += "testimage testsdk"
#TESTIMAGE_AUTO_qemuall = "1"

#
# Interactive shell configuration
#
# Under certain circumstances the system may need input from you and to do this it
# can launch an interactive shell. It needs to do this since the build is
# multithreaded and needs to be able to handle the case where more than one parallel
# process may require the user's attention. The default is iterate over the available
# terminal types to find one that works.
#
# Examples of the occasions this may happen are when resolving patches which cannot
# be applied, to use the devshell or the kernel menuconfig
#
# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
# Note: currently, Konsole support only works for KDE 3.x due to the way
# newer Konsole versions behave
#OE_TERMINAL = "auto"
# By default disable interactive patch resolution (tasks will just fail instead):
PATCHRESOLVE = "noop"

#
# Disk Space Monitoring during the build
#
# Monitor the disk space during the build. If there is less that 1GB of space or less
# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
# of the build. The reason for this is that running completely out of space can corrupt
# files and damages the build in ways which may not be easily recoverable.
# It's necessary to monitor /tmp, if there is no space left the build will fail
# with very exotic errors.
BB_DISKMON_DIRS ??= "\
    STOPTASKS,${TMPDIR},1G,100K \
    STOPTASKS,${DL_DIR},1G,100K \
    STOPTASKS,${SSTATE_DIR},1G,100K \
    STOPTASKS,/tmp,100M,100K \
    ABORT,${TMPDIR},100M,1K \
    ABORT,${DL_DIR},100M,1K \
    ABORT,${SSTATE_DIR},100M,1K \
    ABORT,/tmp,10M,1K"

#
# Shared-state files from other locations
#
# As mentioned above, shared state files are prebuilt cache data objects which can be
# used to accelerate build time. This variable can be used to configure the system
# to search other mirror locations for these objects before it builds the data itself.
#
# This can be a filesystem directory, or a remote url such as http or ftp. These
# would contain the sstate-cache results from previous builds (possibly from other
# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
# cache locations to check for the shared objects.
# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
# at the end as shown in the examples below. This will be substituted with the
# correct path within the directory structure.
#SSTATE_MIRRORS ?= "\
#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
#file://.* file:///some/local/dir/sstate/PATH"

#
# Yocto Project SState Mirror
#
# The Yocto Project has prebuilt artefacts available for its releases, you can enable
# use of these by uncommenting the following line. This will mean the build uses
# the network to check for artefacts at the start of builds, which does slow it down
# equally, it will also speed up the builds by not having to build things if they are
# present in the cache. It assumes you can download something faster than you can build it
# which will depend on your network.
#
#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH"

#
# Qemu configuration
#
# By default native qemu will build with a builtin VNC server where graphical output can be
# seen. The line below enables the SDL UI frontend too.
PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
# By default libsdl2-native will be built, if you want to use your host's libSDL instead of 
# the minimal libsdl built by libsdl2-native then uncomment the ASSUME_PROVIDED line below.
#ASSUME_PROVIDED += "libsdl2-native"

# You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds
# a handy set of menus for controlling the emulator.
#PACKAGECONFIG_append_pn-qemu-system-native = " gtk+"

#
# Hash Equivalence
#
# Enable support for automatically running a local hash equivalence server and
# instruct bitbake to use a hash equivalence aware signature generator. Hash
# equivalence improves reuse of sstate by detecting when a given sstate
# artifact can be reused as equivalent, even if the current task hash doesn't
# match the one that generated the artifact.
#
# A shared hash equivalent server can be set with "<HOSTNAME>:<PORT>" format
#
#BB_HASHSERVE = "auto"
#BB_SIGNATURE_HANDLER = "OEEquivHash"

#
# Memory Resident Bitbake
#
# Bitbake's server component can stay in memory after the UI for the current command
# has completed. This means subsequent commands can run faster since there is no need
# for bitbake to reload cache files and so on. Number is in seconds, after which the
# server will shut down.
#
#BB_SERVER_TIMEOUT = "60"

# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
# track the version of this file when it was generated. This can safely be ignored if
# this doesn't mean anything to you.
CONF_VERSION = "1"

I am still getting the error.

Many thanks

Moritz

lemmi25 commented 2 years ago

Hi,

many thanks again Stefan for pointing me in the right direction. I used the 64 version and no it is working ;).

Cheers Moritz