Hello Luis,
thank you very much for your quick reply. I'm having trouble bitbaking the layer "fsl-image-qt5", bitbake says "Nothing PROVIDES 'fsl-image-qt5'". How can I obtain a local copy of this layer? Do I even need to do that?
Sorry for all these noobish questions.
Regards,
Christoph
EDIT: With the help of this tutorial: Communication between asymmetric cores on i.MX6SoloX I've been able to setup my Ubuntu correctly and am now compiling fsl-image-qt5. Let's see where this leads.
EDIT2: For all the people facing the same problem as I was: Install and setup your SDK like in the linked tutorial. After that go to /usr/bin/ and use "sudo gedit qtcreator.sh" There you need to paste after "export LD_LIBRARY_PATH":
export SDKTARGETSYSROOT=/opt/poky/1.6.2/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi
export PATH=/opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux/usr/bin:/opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi:$PATH
export PKG_CONFIG_SYSROOT_DIR=$SDKTARGETSYSROOT
export PKG_CONFIG_PATH=$SDKTARGETSYSROOT/usr/lib/pkgconfig
export CONFIG_SITE=/opt/poky/1.6.2/site-config-cortexa9hf-vfp-neon-poky-linux-gnueabi
export OECORE_NATIVE_SYSROOT="/opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux"
export OECORE_TARGET_SYSROOT="$SDKTARGETSYSROOT"
export OECORE_ACLOCAL_OPTS="-I /opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux/usr/share/aclocal"
export PYTHONHOME=/opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux/usr
export CC="arm-poky-linux-gnueabi-gcc"
export CXX="arm-poky-linux-gnueabi-g++"
export CPP="arm-poky-linux-gnueabi-gcc"
export AS="arm-poky-linux-gnueabi-as "
export LD="arm-poky-linux-gnueabi-ld --sysroot=$SDKTARGETSYSROOT"
export GDB=arm-poky-linux-gnueabi-gdb
export STRIP=arm-poky-linux-gnueabi-strip
export RANLIB=arm-poky-linux-gnueabi-ranlib
export OBJCOPY=arm-poky-linux-gnueabi-objcopy
export OBJDUMP=arm-poky-linux-gnueabi-objdump
export AR=arm-poky-linux-gnueabi-ar
export NM=arm-poky-linux-gnueabi-nm
export M4=m4
export TARGET_PREFIX=arm-poky-linux-gnueabi-
export CONFIGURE_FLAGS="--target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi --build=x86_64-linux --with-libtool-sysroot=$SDKTARGETSYSROOT"
export CFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types"
export CXXFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types"
export LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"
export CPPFLAGS=""
export OECORE_DISTRO_VERSION="1.6.2"
export OECORE_SDK_VERSION="1.6.2"
export ARCH=arm
export CROSS_COMPILE=arm-poky-linux-gnueabi-
export PATH=/opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux/usr/bin/qt5:$PATH
export OE_QMAKE_CFLAGS="$CFLAGS"
export OE_QMAKE_CXXFLAGS="$CXXFLAGS"
export OE_QMAKE_LDFLAGS="$LDFLAGS"
export OE_QMAKE_CC=$CC
export OE_QMAKE_CXX=$CXX
export OE_QMAKE_LINK=$CXX
export OE_QMAKE_AR=$AR
export OE_QMAKE_LIBDIR_QT=/opt/poky/1.6.2/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi/usr/lib
export OE_QMAKE_INCDIR_QT=/opt/poky/1.6.2/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi/usr/include/qt5
export OE_QMAKE_MOC=/opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/moc
export OE_QMAKE_UIC=/opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/uic
export OE_QMAKE_RCC=/opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/rcc
export OE_QMAKE_QDBUSCPP2XML=/opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/qdbuscpp2xml
export OE_QMAKE_QDBUSXML2CPP=/opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/qdbusxml2cpp
export OE_QMAKE_QT_CONFIG=/opt/poky/1.6.2/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi/usr/lib/qt5/mkspecs/qconfig.pri
export QMAKESPEC=/opt/poky/1.6.2/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi/usr/lib/qt5/mkspecs/linux-oe-g++
export QT_CONF_PATH=/opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/qt.conf
To run QTCreator, you then have to type: "sudo sh qtcreator.sh". The Super User rights are needed for correct compiling, why is beyond me. Otherwise QTCreator would always throw the error in the likes that "c is an unknown command" because he tries to use a parameter as a command.
I used up a good 6 hours to find this out, I hope, somebody reads this and can solve their problem a little bit quicker.
The SDK was installed in the standard directory, don't know if this is actually needed or not, but I tried this in the process of trying to get it all to work aswell and haven't tried using another SDK location but with QT sudo-mode.
Anyway, have fun with this solution.
Regards,
Christoph