Poll: Did you try Qt5 on N900?
Poll Options
Did you try Qt5 on N900?

Reply
Thread Tools
Alecsandru's Avatar
Posts: 439 | Thanked: 282 times | Joined on Oct 2012
#71
Originally Posted by marmistrz View Post
1/ You might look at MeeGo CE rather than nemo, as Nemo can use mlite (a subset of meegotouch)
2/ And what about putting the library into /opt/xcb/ or so?
3/ What about, as a next goal, upgrading x11 as a whole? Some packages are already in -devel. (x11proto-input-meego-dev & etc. - the names are changed).
my hardware keyboard stopped working after upgrading to libx11-data 2:1.1.99.6+0m5+withxcb
how fix to this?
__________________
N900 Beast featuring :
8GB OPTFS@ext4(*performance mount options)
overclock: cpu[125 - 1,150(*VDD1)+Dsp overclock
CSSU-T latest version

Last edited by Alecsandru; 2013-07-22 at 20:58.
 

The Following User Says Thank You to Alecsandru For This Useful Post:
Posts: 114 | Thanked: 298 times | Joined on Jan 2011 @ Berlin
#72
Why do you cite marmistrz?

Did you use the libxc11* packages or libx11-with-xcb? This should not happen with the new ones(libxc11*), they are not loaded by any other program.

This is for those who installed libx11-data = 2:1.1.99.6+0m5-with-xcb :

1) If you can still use a terminal type (e.g. ssh)
apt-get install libx11-data=1.1.99.6+0m5
By the way: does anyone know how to press enter/return just with the sw keyboard?

2) Otherwise: Click on this (original sdk version) use the HAM to install it.

3) If 2) doesn't work: unpack the file above with a desktop PC, copy everything to the device and move it with Filebox (root enabled, see other point 3) below) to the correct destinations. BE CAREFUL, ASK IF YOU DON'T UNDERSTAND THE STRUCTURE OF A .DEB FILE

This is for those who installed libx11-with-xcb:

1) If you can still use a terminal type (e.g. ssh)
apt-get install --reinstall -o -o Dpkg::Options::="--force-overwrite" libx11-6

2) Otherwise: Click on this (original sdk version) use the HAM to install it.

3) If 2) fails get the file with a desktop PC unpack it and put libX11.so.6.2.0 on the device and move it with e.g. Filebox (set root mode enabled in Filebox' options before) to /usr/lib/libX11.so.6.2.0 .

Reboot.

Last edited by frafI; 2013-07-22 at 21:18.
 
Alecsandru's Avatar
Posts: 439 | Thanked: 282 times | Joined on Oct 2012
#73
tried that with ham , not working , extracting and replacing the usr/lib/x11 worked , figured that before reading your post(i f.....g love maemo) , previous post was posted from the phone that's why i've quoted wrong post , your new x11 is completly different to structure compared with nokia's one , i'm waiting for you to succede with your qt5 port , i'm studying it for my first application
__________________
N900 Beast featuring :
8GB OPTFS@ext4(*performance mount options)
overclock: cpu[125 - 1,150(*VDD1)+Dsp overclock
CSSU-T latest version
 

The Following User Says Thank You to Alecsandru For This Useful Post:
Posts: 114 | Thanked: 298 times | Joined on Jan 2011 @ Berlin
#74
Originally Posted by Alecsandru View Post
tried that with ham , not working , extracting and replacing the usr/lib/x11 worked , figured that before reading your post(i f.....g love maemo) , previous post was posted from the phone that's why i've quoted wrong post , your new x11 is completly different to structure compared with nokia's one , i'm waiting for you to succede with your qt5 port , i'm studying it for my first application
1) The only change to libX11 is the parameter --with-xcb, but that seems to change a lot even for standard xlib-based clients. Possibly Nokia configured it with --without-xcb because of a bug.

2) The only big blocker before I can at least ship a tar'ed toolchain is building a proper qmake that does not depend on my paths and other settings. The next step is building a proper qmake in scratchbox, since scratchbox transparent execution seems not to work well with Qt's separated compilation of host and guest tools.
 

The Following 3 Users Say Thank You to frafI For This Useful Post:
Alecsandru's Avatar
Posts: 439 | Thanked: 282 times | Joined on Oct 2012
#75
by the way remove those packages from the repo , you can't upgrade other things automatically without those. i appreciate your work
__________________
N900 Beast featuring :
8GB OPTFS@ext4(*performance mount options)
overclock: cpu[125 - 1,150(*VDD1)+Dsp overclock
CSSU-T latest version
 
Posts: 114 | Thanked: 298 times | Joined on Jan 2011 @ Berlin
#76
Originally Posted by Alecsandru View Post
by the way remove those packages from the repo , you can't upgrade other things automatically without those. i appreciate your work
I'd like to remove them, but ...
See some posts earlier and http://talk.maemo.org/showthread.php?p=1360937.
 
Posts: 3,328 | Thanked: 4,476 times | Joined on May 2011 @ Poland
#77
Originally Posted by frafI View Post
2) Putting them to /opt/xcb only helps if we can force the fully qualified soname or use LD_LIBRARY_PATH, I'd like to avoid both. But I've no problem putting the renamed libXc11.so.6 (and the xcb part) to another directory and change the paths for ldconfig, if you think this is better than optify.

3) I thought, libxau and other cause severe problems. However if they only cause problems on the stock kernel we might consider a power kernel only (and thumb only) build.

Note however that the way I've currently solved this is not a big burden for the future as a simple symlink from libXc11* to the new X11 libs can solve this (if and only if we can use them as a drop in replacement of the properly named old libs).

I'd like to make a first usable (for developers) version of Qt5 as soon as possible, because porting X11, porting Qt5 itself and porting and/or creating application with Qt5 are things that can be done in parallel by different groups. And the possible users of Qt5 (esp. QtQuick2) outnumber any other group. So if they can program slightly buggy but working programs with a (slightly) buggy Qt5 on an old (and buggy?) X11, we'll have actually stable, usable programs if we switch the back-ends to less buggy ones.

TL;DR: This works for now, helps bringing Qt5 to devs and we can change it later (without too much effort).
2) I was thinking about putting it somewhere else with the same name to be able to link it against the newer version. Or LD_* apps which are binaries only and require newer x11. The question is: will x11 work ok with a changed localization. libc didn't (but it was pure copying)

3) Maybe the kp devs would be able to tell us why libxau6 wouldn't work on stock omap?

Qt5 first is really a good idea.
Maybe the CSSU devs can help anything about the xcb problems?
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here

Last edited by marmistrz; 2013-07-23 at 10:17.
 

The Following 2 Users Say Thank You to marmistrz For This Useful Post:
Estel's Avatar
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#78
frafl, I appreciate your work, but never, ever, upload system package to extras-devel. You might have not notice it yet (as they had problems in determining who did that), but you have wraith of whole maemo management on your back, already

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 

The Following 2 Users Say Thank You to Estel For This Useful Post:
Posts: 114 | Thanked: 298 times | Joined on Jan 2011 @ Berlin
#79
Originally Posted by Estel View Post
frafl, I appreciate your work, but never, ever, upload system package to extras-devel. You might have not notice it yet (as they had problems in determining who did that), but you have wraith of whole maemo management on your back, already

/Estel
1) "problems in determining who did that"? The package includes my full name and mail address, and the package interface lists my account as the one who uploaded the libx11 source package. If you know someone who is "at my back", please give me a mail address or irc nickname.

2) What exactly counts as a "system package"? One with the same name as a nokia package/ (c)ssu package, one that interferes with files contained in the aforementioned kind of package ...
Do you consider the libxc11-packages (I will remove the -data package with the next source release) as system packages?
 

The Following User Says Thank You to frafI For This Useful Post:
Estel's Avatar
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#80
Re 1 - AFAIK they deleted it in such haste, than forget to check uploader, and when they reconciled, uploader data was already deleted Or something like that. IRC log in cssu-testing thread contains some funny discussions about it - at the moment of writing, they weren't able to determine uploader.

Re 2 - Ask management, as I may be talking BS, but AIUI, system package = package that exist under same package name in one of so-called Nokia's repos.(freemantle/ssu/mr0 and fremantle/ssu/apps)

Appendix: I think that this situation (and very similar case with marmistrz some time ago) is rather bug/hole of how repos work, than your fault, so fear not. The thing is, that device will install package with higher version number, as long as someone have -devel enabled, and said package is dependency of other package (so, for example, during cssu upgrade, your package was pulled automagically for some, even though they didn't apt-get upgrade).

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!

Last edited by Estel; 2013-07-24 at 20:14.
 

The Following User Says Thank You to Estel For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 14:10.