maemo.org - Talk
Page 5 of 5 « First 34 5
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   MeeGo / Harmattan (https://talk.maemo.org/forumdisplay.php?f=45)
-   -   Maemo 6 loosing source compatibility with plain Qt, and Symbian^4 (https://talk.maemo.org/showthread.php?t=34686)

attila77 2010-10-24 21:14
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
They cannot have *identical* widget sets as the functionality is different on various platforms, but you will certainly get a lot less #ifdefs than you would by making separate MTF, Orbit and QWidget UIs.

Venemo 2010-10-24 22:15
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Here's how I see the situation:
So basically we have 3 main separate and largely incompatible GUI tools:

- QWidgets: Native look&feel for each platform, cross-platform but deprecated.
- QML: also cross-platform, but mostly recommended for creating totally unique GUIs.
- MeeGo Touch: MeeGo only; hardware-accellerated

So the cheapest solution is to use one of these depending on your target platforms, and if you can afford it, you can use the others too for making different UIs for different platforms.

Do I see the situation correctly?

w00t 2010-10-24 23:33
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by Venemo (Post 849900)
Here's how I see the situation:
So basically we have 3 main separate and largely incompatible GUI tools:

- QWidgets: Native look&feel for each platform, cross-platform but deprecated.
- QML: also cross-platform, but mostly recommended for creating totally unique GUIs.
- MeeGo Touch: MeeGo only; hardware-accellerated

So the cheapest solution is to use one of these depending on your target platforms, and if you can afford it, you can use the others too for making different UIs for different platforms.

Do I see the situation correctly?
well, you make one mistake in leaving 'hardware acceleration' under MTF, as QML can also be hardware accelerated (as can QWidget), and likewise, MeeGo Touch can use software rendering, so there's no functional difference between the three there.

personally, the summary, as i'd put it, is below.

summary being (as it ended out being a bit longer than I expected), with no surprises:
- QWidget is portable, but aging badly
- QML is shiny, new, and looking promising, but really needs more work in the portability department with e.g. components (no, mobiles really aren't the only target in the world, no matter what you say, Nokia) - which is something I myself have started playing with in the past day
- MeeGo Touch is an 'ok' choice if you want a good product on MeeGo now and don't care about maintaining it into the future or making the best technology choice for deployment on multiple platforms.

The comparison:
QWidget
(note, that it isn't deprecated from the Qt point of view as there is no capable replacement yet, but it clearly isn't where UIs of the future are coming from)
Pros:
- Cross platform
- Native look and feel
Cons:
- Not really flexible enough to do some of the shinier UI tricks
- Painting stuff yourself is really a pain in the ***, especially when you get on to things like delegates

QML
Pros:
- Cross platform
- Flexible
Cons:
- No native look and feel
- Immature
- QML (with Qt Components)
Same as QML, with the addition:
Pros:
- Some native look and feel, but only on limited platforms at this point.


MeeGo Touch
Pros:
- Designed for Omg! Shiny!
- Fairly mature, thanks to having had a number of applications built on it
Cons:
- A very, very moving target - I don't think the API was all that well thought out in places (seriously. MContentItem, MBasicListItem, MAdvancedListItem, MDetailedListItem?! how many different ways do we *really* need to show data in a list..), nor the requirements, and it shows in the sheer amount of stuff that is deprecated from MeeGo Touch, even in more recent times.
- No look and feel for platforms other than MeeGo whatsoever
- Increasingly less portable (things like MGConfItem, in addition to being kind of crappy design, are kind of hinting where the target platform is)

egoshin 2010-10-24 23:46
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Where I can find Qt 4.6 binaries for ARM platform (Maemo5)?

Maemo repository doesn't have it (see bug https://bugs.maemo.org/show_bug.cgi?id=11437)

w00t 2010-10-24 23:49
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by egoshin (Post 849935)
Where I can find Qt 4.6 binaries for ARM platform (Maemo5)?

Maemo repository doesn't have it (see bug https://bugs.maemo.org/show_bug.cgi?id=11437)
For dev stuff, you can't. It's just not available, thanks to the way they do packages. You'll need to build it yourself via scratchbox and/or chicken sacrifice.

[I don't think this is strictly on-topic for this thread, btw]

egoshin 2010-10-24 23:56
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by w00t (Post 849937)
For dev stuff, you can't. It's just not available, thanks to the way they do packages. You'll need to build it yourself via scratchbox and/or chicken sacrifice.

[I don't think this is strictly on-topic for this thread, btw]
In my mind the absence of capability to build Qt application from source on N900 is an exactly "Maemo 5 loosing source compatibility with plain Qt". Sorry for misunderstanding.

EDIT: Yes, I understand that Maemo 5 is not Maemo 6, but...

daperl 2010-10-25 01:06
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by egoshin (Post 849935)
Where I can find Qt 4.6 binaries for ARM platform (Maemo5)?
As an example:

apt-get -d --reinstall install libqt4-core

This will just download and not actually reinstall.

Then look in

/var/cache/apt/archives

and you should find

libqt4-core_4.6.2~git20100401-0maemo1+0m5_armel.deb

egoshin 2010-10-25 01:28
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by daperl (Post 849963)
As an example:

apt-get -d --reinstall install libqt4-core

This will just download and not actually reinstall.

Then look in

/var/cache/apt/archives

and you should find

libqt4-core_4.6.2~git20100401-0maemo1+0m5_armel.deb
I could not ask without reason, you can try yourself. Or just follow the reference to bug - I put some interesting output in it.

daperl 2010-10-25 02:00
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by egoshin (Post 849970)
I could not ask without reason, you can try yourself. Or just follow the reference to bug - I put some interesting output in it.
LOL, that's funny. Well, in a coincidental sort of way. I ran into the same problem when trying to build fcamera on the device, so then I had to rebuild some of those. Also, I think some Qt binary package(s) messed up my FREMANTLE_ARMEL target in one of my scratchbox installs. It caused the qemu transparency stuff to stop working.

Thanks for reporting it.

daperl 2010-10-25 05:06
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Here's the bug fix for FREMANTLE_ARMEL:

Code:
--- qt4-x11-4.6.2~git20100401.orig/configure    2010-04-08 02:48:34.000000000 -0700
+++ qt4-x11-4.6.2~git20100401/configure    2010-10-24 21:52:36.000000000 -0700
@@ -2297,7 +2297,8 @@
    # if we're within scratchbox, build qmake and friends with the host compiler
    if [ -z "$PLATFORM" ] && [ -z "$XPLATFORM" ] && [ "$SBOX_UNAME_MACHINE" = "arm" ] ; then
        XPLATFORM="linux-g++-maemo5"
-        PLATFORM="linux-host-g++"
+        #PLATFORM="linux-host-g++"
+        PLATFORM="linux-g++-maemo5"
        QT_FORCE_PKGCONFIG=yes
    fi
    if [ -z "$CFG_ARCH" ] && [ "$SBOX_UNAME_MACHINE" = "arm" ] ; then
I've successfully built armel binaries of

qmake
moc
rc
uic

with the above patch on an x86 machine in the FREMANTLE_ARMEL target with the following command:

Code:
dpkg-buildpackage -b -d -nc -rfakeroot
The build hasn't reached the other binaries yet, but their Makefiles have been created.

egoshin 2010-10-25 05:55
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
For a moment I build it on N900, following your instruction in other thread.

EDIT: It again failed in opengl check -

"The EGL functionality test failed!
EGL is required for OpenGL ES to manage contexts & surfaces.
You might need to modify the include and library search paths by editing
QMAKE_INCDIR_EGL, QMAKE_LIBDIR_EGL and QMAKE_LIBS_EGL in
/root/qt4-x11-4.6.2~git20100401/mkspecs/linux-g++-maemo5."

Both packages - opengles-sgx-img-common-dev and libgles2-sgx-img-dev are installed as so as non "-dev" versions.

daperl 2010-10-25 06:55
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by egoshin (Post 850091)
For a moment I build it on N900, following your instruction in other thread.

EDIT: It again failed in opengl check -

"The EGL functionality test failed!
EGL is required for OpenGL ES to manage contexts & surfaces.
You might need to modify the include and library search paths by editing
QMAKE_INCDIR_EGL, QMAKE_LIBDIR_EGL and QMAKE_LIBS_EGL in
/root/qt4-x11-4.6.2~git20100401/mkspecs/linux-g++-maemo5."

Both packages - opengles-sgx-img-common-dev and libgles2-sgx-img-dev are installed as so as non "-dev" versions.
Yes, the build failed. I'll take a closer look at the errors tomorrow, but from a quick glance I think it was gl related.

cristids 2010-10-25 08:28
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by attila77 (Post 849863)
They cannot have *identical* widget sets as the functionality is different on various platforms, but you will certainly get a lot less #ifdefs than you would by making separate MTF, Orbit and QWidget UIs.
I fail to see why they must be incompatible. Actually I kind of know, it is lack of communication between divisions in the same company and this is what makes it even more unacceptable.
From a developer point of view I do want my application to look exactly the same on all targeted mobile platforms. I don't want my application to look different in symbian than meego or maemo. I mean we are talking about mobile devices having almost same screen size/resolution. There are four mobile os-es supported right now, why should one think an application needs to look different in any of them?
Well I now that the look and feel of a button is not same on meego vs symbian but that doesn't mean I need a button class for each. This should be Qt hidding it from me.
If they cannot achieve that then this means Qt fails to deliver on its promise big time.

From a user point of view it means that some platforms may not get some applications because it means redesigning all UI. So platforms having lower market adoption (think Maemo) may not get applications after all, even though they are available for other platforms supporting Qt.

attila77 2010-10-25 09:26
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by cristids (Post 850194)
I don't want my application to look different in symbian than meego or maemo. I mean we are talking about mobile devices having almost same screen size/resolution. There are four mobile os-es supported right now, why should one think an application needs to look different in any of them?
Well I now that the look and feel of a button is not same on meego vs symbian but that doesn't mean I need a button class for each.
Because the UI paradigm *is* different on these OSes, either due to historical reasons or because of HW form factors (they definitely do NOT have nearly the same size/resolution and screen/kbd). This is not about just a QPushbutton, that we could get over easily, but rather how much part of the OS the app feels. I agree that the #ifdeffing should be done away with or at least minimized, but you cannot so easily forego platform specifics (Components is no silver bullet but at least it makes the mess more manageable). As said, QPushbutton is easy, but what do you do with Symbian softkeys, Maemo's stacked windows, funky pickers, application menus, file management, etc. I know, I know 'not my problem', but am just saying that after doing a project or two you *will* realize that you don't *really* want your apps to look literally the same on all platforms, the best Qt can do is to help you minimize the pain.

Khertan 2010-10-25 09:32
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Exactly it s not cross plateform but Qt minimize the pain.

cristids 2010-10-25 09:43
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by attila77 (Post 850255)
Because the UI paradigm *is* different on these OSes, either due to historical reasons or because of HW form factors (they definitely do NOT have nearly the same size/resolution and screen/kbd). This is not about just a QPushbutton, that we could get over easily, but rather how much part of the OS the app feels. I agree that the #ifdeffing should be done away with or at least minimized, but you cannot so easily forego platform specifics (Components is no silver bullet but at least it makes the mess more manageable). As said, QPushbutton is easy, but what do you do with Symbian softkeys, Maemo's stacked windows, funky pickers, application menus, file management, etc. I know, I know 'not my problem', but am just saying that after doing a project or two you *will* realize that you don't *really* want your apps to look literally the same on all platforms, the best Qt can do is to help you minimize the pain.
Please explain to me how N900 is different in HW form factor than N8 or newer symbian devices bearing Qt. They all have touch screens that are about same size. I assume N9 or whatever name will have will be somwhere between 3 and 4.5 inches.
None of the elements you mention must be os specific. I mean I would've have them all put under Qt umbrella. If I want soft keys implemented that is fine, I put the code in Qt, making a note that it is only symbian supported. Meego finds out that it needs soft keys, here they are,we enable them in qt. But each with its own set of controls it is simply bad design and bad interaction between architects. I understand that they choose the shortest path but eventually this will strike back as Qt doesn't deliver on its promise. Instead they should've plan better and when a UI component is needed implement it in all platforms, make it look the same and everybody would've been happy.

egoshin 2010-10-25 16:21
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by daperl (Post 850130)
Yes, the build failed. I'll take a closer look at the errors tomorrow, but from a quick glance I think it was gl related.
Today's PR1.3 - package libqt4-dev_4.7.0~git20100909-0maemo1+0m5_armel.deb - the same sh*t, it has Intel386 binaries instead of ARM-based.

attila77 2010-10-25 16:43
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by cristids (Post 850282)
Please explain to me how N900 is different in HW form factor than N8 or newer symbian devices bearing Qt. They all have touch screens that are about same size. I assume N9 or whatever name will have will be somwhere between 3 and 4.5 inches.
That's the point, Qt is not just a 'widget set for ~4" touchscreen devices'. It really needs to (and already does) cover a lot more ground than that, and esp with MeeGo I expect to see a lot wider device spectrum than just N8/N900 lookalikes.

Quote:
None of the elements you mention must be os specific. I mean I would've have them all put under Qt umbrella. If I want soft keys implemented that is fine, I put the code in Qt, making a note that it is only symbian supported. Meego finds out that it needs soft keys, here they are,we enable them in qt. But each with its own set of controls it is simply bad design and bad interaction between architects. I understand that they choose the shortest path but eventually this will strike back as Qt doesn't deliver on its promise. Instead they should've plan better and when a UI component is needed implement it in all platforms, make it look the same and everybody would've been happy.
I have the feeling you are talking about the now bygone Orbit vs MTF discussion. Please check up on Qt Components, it is almost exactly what you seem to be missing.

egoshin 2010-10-27 20:31
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by daperl (Post 850130)
Yes, the build failed. I'll take a closer look at the errors tomorrow, but from a quick glance I think it was gl related.
I used QT 4.7.0 from PR.1.3 and build in accordance with your instructions passed up to creating bin/qmake. Good! It failed just after that on absence of X11 libs.

I am going to recreate the rest of binaries (moc etc).

But just one question - zrules.txt misses some parameters in comparison with debian/rules, like "-graphicssytem raster" or "-phonon" or "no-rpath". Do I need to add that to zrules.txt?

Venemo 2010-10-28 10:28
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by w00t (Post 849930)
well, you make one mistake in leaving 'hardware acceleration' under MTF, as QML can also be hardware accelerated (as can QWidget), and likewise, MeeGo Touch can use software rendering, so there's no functional difference between the three there
If this is the case, what is the point in having just another widget framework for MeeGo instead of using the already existing QWidget-based stuff?

daperl 2010-10-28 14:02
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by egoshin (Post 854177)
I used QT 4.7.0 from PR.1.3 and build in accordance with your instructions passed up to creating bin/qmake. Good! It failed just after that on absence of X11 libs.

I am going to recreate the rest of binaries (moc etc).

But just one question - zrules.txt misses some parameters in comparison with debian/rules, like "-graphicssytem raster" or "-phonon" or "no-rpath". Do I need to add that to zrules.txt?
zrules.txt was a hack. I think my one line fix to configure is the better solution. At least for building the armel tools. So, maybe ignore zrules.txt.

I haven't tried building Qt in PR1.3 yet, but I was able to fix some other compile errors for 1.2. However, that just opened a can of worms that maybe revealed a deeper issue. Anyway, I'll try building 4.7 when I get a moment, and if the build fails as it did in 1.2, I'll post some details here.

egoshin 2010-10-28 16:23
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by daperl (Post 855289)
zrules.txt was a hack. I think my one line fix to configure is the better solution. At least for building the armel tools. So, maybe ignore zrules.txt.
Where is "one line fix"? Changing linux-g++-maemo? In any case it requires running "configure" and it's parameters issue is still here.

BTW, in 4.7.0 it seems fixed and now I bump into "absense" of XLib. It doesn't elaborate which kind of xlib it needs - run time or developer build time. Or it may just absence of /usr/X11R6/lib...

daperl 2010-10-28 17:02
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by egoshin (Post 855498)
Where is "one line fix"? Changing linux-g++-maemo? In any case it requires running "configure" and it's parameters issue is still here.
Make the one line configure fix and then let the debian tools do all the work.

From scratchbox in the FREMANTLE_ARMEL target:

Code:
mkdir qt
chdir qt
apt-get source libqt4-dev
chdir qt4-x11-4.7.0~git20100909
sed -i 's/linux-host-g++/linux-g++-maemo5/' configure
dpkg-buildpackage -b -d -nc -rfakeroot
No other changes are needed in order to create qmake moc rcc and uic.

daperl 2010-10-28 17:12
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
And don't forget to do the following:

Code:
fakeroot apt-get build-dep libqt4-dev

egoshin 2010-10-28 18:55
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by daperl (Post 855552)
Make the one line configure fix and then let the debian tools do all the work.

From scratchbox in the FREMANTLE_ARMEL target:

Code:
mkdir qt
chdir qt
apt-get source libqt4-dev
chdir qt4-x11-4.7.0~git20100909
sed -i 's/linux-host-g++/linux-g++-maemo5/' configure
dpkg-buildpackage -b -d -nc -rfakeroot
No other changes are needed in order to create qmake moc rcc and uic.
dpkg-buildpackage doesn't work because there is reference to /usr/share/cdbs/ files in debian/rule. Which package does it use - cdbs or cdbs-dh7? Or maemo-cflags-cdbs-rules?

egoshin 2010-10-28 19:11
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by daperl (Post 855568)
And don't forget to do the following:

Code:
fakeroot apt-get build-dep libqt4-dev
This program was written somebody worked with Microsoft - it says:

E: Build-dependencies for libqt4-dev could not be satisfied.

without elaboration and sign of more extensive diagnostic.

daperl 2010-10-29 01:02
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by egoshin (Post 855718)
This program was written somebody worked with Microsoft - it says:

E: Build-dependencies for libqt4-dev could not be satisfied.

without elaboration and sign of more extensive diagnostic.
How did you upgrade your scratchbox? After commenting out all the extras repositories, here's what I did:

Code:
apt-get update
fakeroot apt-get upgrade
I then installed all the held back packages and I ran

Code:
fakeroot apt-get upgrade
until it said there were no more held back packages.

daperl 2010-10-29 01:33
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Awesome, the other build errors are gone in 1.3. Here's the debian/rules diff needed to complete the build:

Code:
--- debian/rules.orig        2010-10-27 01:04:40.140719086 +0100
+++ debian/rules        2010-10-27 01:03:16.552666520 +0100
@@ -52,7 +52,7 @@
        HOST_EXCLUDES=-X/moc -X/rcc -X/uic -X/qmake -X/lrelease
        EXTRA_STRIP_ARGS=$(HOST_EXCLUDES)
        EXTRA_HOST_STRIP_ARGS=--strip-all bin/moc bin/rcc bin/uic bin/qmake bin/lrelease
-        HOST_MKSPEC=-spec $(CURDIR)/mkspecs/linux-host-g++
+        HOST_MKSPEC=-spec $(CURDIR)/mkspecs/linux-g++-maemo5
 else
        HOST_EXCLUDES=
        GL_BACKEND=desktop
@@ -118,7 +118,7 @@
 common-build-arch:: build-dbus-tools build-linguist-tools build-maemo5-examples strip-host-tools build-uitools build-qml-tool
 
 strip-host-tools:
-        if [ -n "$(EXTRA_HOST_STRIP_ARGS)" ] ; then host-strip $(EXTRA_HOST_STRIP_ARGS) ; fi
+        if [ -n "$(EXTRA_HOST_STRIP_ARGS)" ] ; then strip $(EXTRA_HOST_STRIP_ARGS) ; fi
 
 build-dbus-tools:
        bin/qmake -o tools/qdbus/qdbusxml2cpp/Makefile tools/qdbus/qdbusxml2cpp/qdbusxml2cpp.pro
And here's the result:

Code:
-rw-r--r-- 1 maemo maemo  9898818 Oct 27 01:13 libqt4-core-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  1541266 Oct 27 01:13 libqt4-core_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  1995710 Oct 27 01:15 libqt4-dbus-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  230152 Oct 27 01:15 libqt4-dbus_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo 14842646 Oct 27 01:16 libqt4-declarative-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  1425932 Oct 27 01:16 libqt4-declarative_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  5897106 Oct 27 01:16 libqt4-dev_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo 42749090 Oct 27 01:14 libqt4-gui-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  5035830 Oct 27 01:13 libqt4-gui_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  554966 Oct 27 01:16 libqt4-maemo5-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  206572 Oct 27 01:16 libqt4-maemo5-examples_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo    29798 Oct 27 01:16 libqt4-maemo5_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  840278 Oct 27 01:16 libqt4-multimedia-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo    64888 Oct 27 01:16 libqt4-multimedia_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  6236302 Oct 27 01:14 libqt4-network-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  618632 Oct 27 01:14 libqt4-network_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  2745624 Oct 27 01:16 libqt4-opengl-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo    1454 Oct 27 01:16 libqt4-opengl-dev_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  221480 Oct 27 01:16 libqt4-opengl_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  3338876 Oct 27 01:16 libqt4-phonon-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  242438 Oct 27 01:16 libqt4-phonon_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo 19667124 Oct 27 01:14 libqt4-script-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  1363486 Oct 27 01:14 libqt4-script_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  1020768 Oct 27 01:14 libqt4-sql-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  165326 Oct 27 01:14 libqt4-sql-sqlite-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo    21482 Oct 27 01:14 libqt4-sql-sqlite_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  100724 Oct 27 01:14 libqt4-sql_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  1708854 Oct 27 01:14 libqt4-svg-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  175042 Oct 27 01:14 libqt4-svg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  503944 Oct 27 01:15 libqt4-test-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo    59552 Oct 27 01:15 libqt4-test_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  746740 Oct 27 01:13 libqt4-translations_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  1293596 Oct 27 01:15 libqt4-webkit-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  6047210 Oct 27 01:15 libqt4-webkit_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  438090 Oct 27 01:15 libqt4-xml-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  115474 Oct 27 01:15 libqt4-xml_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo 23883406 Oct 27 01:15 libqt4-xmlpatterns-dbg_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  1622994 Oct 27 01:15 libqt4-xmlpatterns_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-r--r-- 1 maemo maemo  180516 Oct 27 01:16 qt4-declarative-qmlviewer_4.7.0~git20100909-0maemo1+0m5_armel.deb
-rw-rw-r-- 1 maemo maemo    7302 Oct 27 01:16 qt4-x11_4.7.0~git20100909-0maemo1+0m5_armel.changes
Don't mind my time stamps; my settings inside my Ubuntu VM are off.

egoshin 2010-10-29 03:50
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by daperl (Post 856039)
How did you upgrade your scratchbox?
I run on N900. It is a reason why I need ARMEL binaries of qmake/moc/etc

daperl 2010-10-29 04:30
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by egoshin (Post 856125)
I run on N900. It is a reason why I need ARMEL binaries of qmake/moc/etc
Me too, I upgraded my on-device sdk the same way I described above. Here's the answer to your earlier question:

Code:
(chroot)root@Nokia-N900:/
# dpkg -l|grep -i cdbs
ii  cdbs                                  0.4.48-0osso2                  common build system for Debian packages

egoshin 2010-10-29 06:32
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
I gave up - for qt4 build I turned to scratchbox.

On "apt-get upgrade" it find hildon-initscripts version from SDK which is clearly for scratchbox (it tryes to remove mp-fremantle-002-pr) and "apt-get build-dep libqt4-dev" repeats the same unreasonable error message (see above).

Later I will compare the installed packages on both - scratchbox and N900 with qt4 debian/control but for now I think I am spending too much time just to fix a simple bug in small qt-based program.

egoshin 2010-10-29 16:36
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
OK, I successfully build all qt4 packages in scratchbox and I have now ARMEL binaries for libqt4-dev - qmake/moc/uic/etc. It took a couple of hours, so in N900 it would take a couple of days I guess.

Let's see can it work for simple qt4-based application build in N900 (I target googlelatitude) now. If it work I can share that binaries.

EDIT: googlelatitude build on N900 works... some issue does exist but it may be bugs...

In any case - big thank to daperl for providing clues and build bugs fixes.

qgil 2010-10-30 05:11
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Sorry for interrupting but aren't you taking this old thread too far from its original topic?

egoshin 2010-10-31 02:43
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Quote:
Originally Posted by qgil (Post 857298)
Sorry for interrupting but aren't you taking this old thread too far from its original topic?
Don't sure but my point is about incompatibility of Maemo's N900 with libqt4-dev. I speak not about general incompatibility but practical one - I can't did QT development on N900 from software source.

Sorry, if it bothers you.

attila77 2010-10-31 11:03
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
I would say Quim is asking that not because what you say is not interesting but because this topic is in the Harmattan forum and about Maemo 6...

egoshin 2010-11-03 19:22
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Sorry for bothering you the last time in this thread -

I upload a package libqt4-dev-armel into https://garage.maemo.org/projects/libqt4-dev-arm/

You can install it on N900 Maemo for small QT development instead of libqt4-dev. It is built from the same source but with ARMEL binaries.

svdwal 2011-02-12 23:09
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
Ok, people, do you now understand, after the windows Phone 7 announcements, why I started this thread? And do you see now why it was such a bad idea?

geneven 2011-02-12 23:26
Re: Maemo 6 loosing source compatibility with plain Qt, and Symbian^4
 
It sounds like the OP doesn't think this is too far off topic, and it might even be relevant to what's happening nowl


All times are GMT. The time now is 04:57.
Page 5 of 5 « First 34 5
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8