Re: [Development] bitbake meta-toolchain error

2014-08-01 Thread thomas . senyk
EGL "thinks" (as in defines) it's a framebuffer build, Qt tries to build the XCB plugin .. shouldn't happen when removing x11 from distro_features. Have you 'bitbake'ed before adding DISTRO_FREATURES_remove ... ? If so consider to start over with a fresh build because it might be a bit hard to

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

2014-08-01 Thread Jake Petroules
On 2014-08-01, at 04:00 PM, Henry Skoglund wrote: > On 2014-08-01 21:01, Adam Strzelecki wrote: >> ... >> Well, to be frank there is a simple workaround for that :) Why not > symlink Qt frameworks at build time, then replace symlinks with real > copies on deployment step? >> >> So the easiest

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

2014-08-01 Thread Jake Petroules
On 2014-08-01, at 03:01 PM, Adam Strzelecki wrote: >>> All we need to do is build all Qt dylibs with install_name = >>> @rpath/pathrelative_to_lib_folder/some.dylib and make sure qmake adds >>> following linker flags to all apps linking to Qt: >> >> Just @rpath/QtModuleName.framework/Versions/

[Development] [docs/c++] How do we deal with the special member functions (copy/move ctor/assignment operator, dtor, default ctor)

2014-08-01 Thread Marc Mutz
Hi, As part of the move to C++11, we have dropped some user-defined special member functions from the API if they weren't doing anything else than the ones the compiler implicitly creates for us. This has the advantage that a C++11 compiler will create move ctors without the need for #ifdef'ing

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

2014-08-01 Thread Henry Skoglund
On 2014-08-01 21:01, Adam Strzelecki wrote: >... > Well, to be frank there is a simple workaround for that :) Why not symlink Qt frameworks at build time, then replace symlinks with real copies on deployment step? > > So the easiest solution would be to symlink Qt frameworks when your create

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

2014-08-01 Thread Jake Petroules
On 2014-08-01, at 11:13 AM, Adam Strzelecki wrote: > Hello, > > Since 5.4 feature freeze is going to happen soon, I want to escalate long > standing problem described in QTBUG-31814. > > Long story short, Qt is using some nasty install prefix padding and dylib > rewrite (via install_name_tool

[Development] Relative paths in EXAMPLE_FILES in .pro files

2014-08-01 Thread Sumedha Widyadharma
Hi, This seems to be forbidden in a .pro file: EXAMPLE_FILES += ../some/file what is the rationale behind not allowing this? It is silently dropped, you have to enable CONFIG+=check_examples to get a notice about this. Why is that? Shouldn't it always warn the user? Regards, Sumedha Widyadha

[Development] bitbake meta-toolchain error

2014-08-01 Thread Nilesh Kokane
Hello, I followed http://wiki.wandboard.org/index.php/Building_Qt5_using_yocto_on_Wandboard (newly added) The DISTRO_FEATURES_remove = "x11 wayland" is removed from the local.conf And after giving the bitbake core-image-minimal I'm logged with the errors as posted on pastebin http://pastebin

[Development] Running QtQuick 1.1 "Hello World" application on ARM Linux (LinuxFB platform)

2014-08-01 Thread Zoran PlesivĨak
I would appreciate any help I could get regarding this. 1. I've compiled Qt 5.1.1 for HOST and tested "Hello World" QtQuick 1.1 application and it works without any problems, 2. I've cross-compiled Qt 5.1.1 without problems for ARM with LinuxFB platform support, 3. I've cross-compiled "Hello World