maemo.org - Talk
Page 26 of 29 « First 162425 26 2728 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)
-   -   Sailfish SDK version 1608 (2.0.2) Qt5 released (https://talk.maemo.org/showthread.php?t=89294)

droll 2014-02-11 19:20
Re: Sailfish SDK Alpha 1312 Qt5 released
 
@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

Quote:
//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>

droll 2014-02-11 19:24
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by mariusmssj (Post 1411632)
-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.
??

mariusmssj 2014-02-11 19:29
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by droll (Post 1412285)
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?
http://i.imgur.com/Y5lvivN.png

droll 2014-02-11 19:48
Re: Sailfish SDK Alpha 1312 Qt5 released
 
nope, don't see it.

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

i see it now. :) thanks!

droll 2014-02-11 19:58
Re: Sailfish SDK Alpha 1312 Qt5 released
 
so does anyone know why i'm getting all these unresolved symbols.... :(

evk 2014-02-11 20:28
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by droll (Post 1412296)
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.

droll 2014-02-11 23:37
Re: Sailfish SDK Alpha 1312 Qt5 released
 
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....

szopin 2014-03-21 14:52
Re: Sailfish SDK Alpha 1312 Qt5 released
 
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 2014-03-21 18:59
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by szopin (Post 1417965)
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?

szopin 2014-03-21 19:50
Re: Sailfish SDK Alpha 1312 Qt5 released
 
Quote:
Originally Posted by w00t (Post 1417999)
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


All times are GMT. The time now is 13:12.
Page 26 of 29 « First 162425 26 2728 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8