Reply
Thread Tools
Posts: 958 | Thanked: 483 times | Joined on May 2010
#251
@mariusmssj

thank you for the screenshots. i will try that in a while.

in the meantime, does anyone know how i can build a console application for Sailfish that uses Qt? i only want to use certain Qt classes with no UI.

i must be missing something in my .pro file as the compiler is complaining about unresolved symbols? i created a new project under Qt Creator as C++ application.

i also tried creating a SailfishOS project and in main.cpp I have my code added in. I commented out

//Sailfish::showView(view.data());
//return app->exec();
same thing. still complaining about unresolved symbols. i am trying to use QFeedbackHapticsEffect and QFeedbackActuator. my #include section looks like this

#include <QtFeedback/QFeedbackActuator>
#include <QtFeedback/QFeedbackHapticsEffect>
#include <QGuiApplication>
#include <QQuickView>
 
Posts: 958 | Thanked: 483 times | Joined on May 2010
#252
Originally Posted by mariusmssj View Post
-First of all you don't add Generic Linux Device but add Mer ARM Device Tools->Options->Devices->Add

-Your PC needs to be on 192.168.2.X sub domain, thus your local IP need to begin with 192.168.2.

- In project tabs you will need to add a MerSDK_SailfishOS_armv7hl kit if not already there

...
wait a sec. i don't see Mer ARM Device in the list. I only see Generic Linux Device and Mer Emulator Device.

tried updating the SDK via control panel (yes, i develop on Windows) and it only found an updated maintenance tool.

edit: i think i'll uninstall the SDK and download a copy. i had mine installed before Mer ARM Device support was added sometime around mid Dec last year.
??

Last edited by droll; 2014-02-11 at 19:29.
 
Posts: 951 | Thanked: 2,344 times | Joined on Jan 2012 @ UK
#253
Originally Posted by droll View Post
wait a sec. i don't see Mer ARM Device in the list. I only see Generic Linux Device and Mer Emulator Device.

tried updating the SDK via control panel (yes, i develop on Windows) and it only found an updated maintenance tool.

edit: i think i'll uninstall the SDK and download a copy. i had mine installed before Mer ARM Device support was added sometime around mid Dec last year.
??
So you don't see this?
 

The Following User Says Thank You to mariusmssj For This Useful Post:
Posts: 958 | Thanked: 483 times | Joined on May 2010
#254
nope, don't see it.

i just uninstalled, downloaded a new copy , and installed the new copy.

i see it now. thanks!
 
Posts: 958 | Thanked: 483 times | Joined on May 2010
#255
so does anyone know why i'm getting all these unresolved symbols....
 
Posts: 84 | Thanked: 79 times | Joined on Dec 2013
#256
Originally Posted by droll View Post
so does anyone know why i'm getting all these unresolved symbols....
Which symbols do the linker complain about? Probably something missing to the QT or QTPLUGIN variable in the .pro file.
 
Posts: 958 | Thanked: 483 times | Joined on May 2010
#257
Code:
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:17: error: undefined reference to `QFeedbackActuator::actuators()'
C:\Users\xxx\Documents\Jolla\TestVibraUI\main.cpp:24: error: undefined reference to `QFeedbackActuator::name() const'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:40: error: undefined reference to `QFeedbackHapticsEffect::QFeedbackHapticsEffect(QObject*)'
C:\Users\xxx\Documents\Jolla\TestVibraUI\main.cpp:42: error: undefined reference to `QFeedbackHapticsEffect::setIntensity(double)'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:43: error: undefined reference to `QFeedbackHapticsEffect::setDuration(int)'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:44: error: undefined reference to `QFeedbackHapticsEffect::setActuator(QFeedbackActuator*)'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:45: error: undefined reference to `QFeedbackEffect::start()'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:46: error: undefined reference to `QFeedbackEffect::stop()'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:46: error: undefined reference to `QFeedbackHapticsEffect::~QFeedbackHapticsEffect()'
\home\mersdk\Documents\Jolla\TestVibraUI\main.cpp:46: error: undefined reference to `QFeedbackHapticsEffect::~QFeedbackHapticsEffect()'
it's not even at the linker yet....
 
Posts: 2,076 | Thanked: 3,268 times | Joined on Feb 2011
#258
from twitter:
@locusf: Sailfish SDK Qt Creator sources are now online in: https://t.co/H0bqRKHQpD Might reveal a lot of interesting stuff.

Trying to build on device, qt5-qmake, qt5-qtconcurrent-devel and qt5-qtcore-devel all install fine. Qtgui and widgets sadly don't:

Code:
Fatal error: qt5-qtgui-devel-5.1.0+git31-1.12.8.armv7hl requires qt5-qtopengl-devel, but this requirement cannot be provided
qt5-qtwidgets-devel-5.1.0+git31-1.12.8.armv7hl requires pkgconfig(Qt5Gui), but this requirement cannot be provided
qtgui needs qtopengl that needs libEGL, the only similar pckg is mesa-llvmpipe-libEGL, but that conflicts with libhybris. Anyone has an idea how to get it to compile/working?
 
w00t's Avatar
Posts: 1,055 | Thanked: 4,107 times | Joined on Oct 2009 @ Norway
#259
Originally Posted by szopin View Post
qtgui needs qtopengl that needs libEGL, the only similar pckg is mesa-llvmpipe-libEGL, but that conflicts with libhybris. Anyone has an idea how to get it to compile/working?
Here be dragons.

As a whole stack, we build against Mesa's libEGL, but at runtime, we then pick a different - hardware-dependent libEGL implementation (which exactly depends on what hardware we're running on: on the Jolla, it's libhybris', on the N9 there's ti-omap3-sgx-wayland-wsegl's wrapper around the SGX drivers, etc). They're all - obviously - ABI/API compatible.

On the whole, I'd just recommend not building on device, because there is a way-too-easy chance you can wipe out your EGL libraries if you accidentally answer "yes" at the wrong prompt.

Why not use the SDK, out of interest?
__________________
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.
 

The Following 2 Users Say Thank You to w00t For This Useful Post:
Posts: 2,076 | Thanked: 3,268 times | Joined on Feb 2011
#260
Originally Posted by w00t View Post
Here be dragons.

As a whole stack, we build against Mesa's libEGL, but at runtime, we then pick a different - hardware-dependent libEGL implementation (which exactly depends on what hardware we're running on: on the Jolla, it's libhybris', on the N9 there's ti-omap3-sgx-wayland-wsegl's wrapper around the SGX drivers, etc). They're all - obviously - ABI/API compatible.

On the whole, I'd just recommend not building on device, because there is a way-too-easy chance you can wipe out your EGL libraries if you accidentally answer "yes" at the wrong prompt.

Why not use the SDK, out of interest?
Couple of reasons. First is pleasure to have a fully fledged PC in your pocket (like when flashing one N900 with another, who needs desktop, right?). Second, most of my free-to-tinker time is on bus rides to/from work and similar. If I need a quick fix/modification I can perform it on the go instead of waiting 10h (if I get the idea on the morning ride) to see if it works. Not expecting to have a full build/deploy-to-harbour env on the phone, but for a quick recompile I hope we can make it work (especially now with HWKB OH)


edit: good news, at least tohkbd can be tweaked/tinkered with on the go, qmake generates Makefile correctly, make succeeds, no need for qtcreator

Last edited by szopin; 2014-03-21 at 20:02.
 

The Following 2 Users Say Thank You to szopin For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 08:04.