Reply
Thread Tools
Posts: 252 | Thanked: 252 times | Joined on Nov 2009
#1
I just reinstalled Scratchbox on my computer and got the newest SDK version PR1.2 with Qt4.6. While this is a good thing to begin with, it became a bad thing when I tried to compile packages and run these on my N900 device. Now I either get a segfault when trying to run the binaries directly or a dependency issue when trying to install packages built with dpkg-buildpackage.

The missing packages are
libhildon1 (>= 2.2.10)
libhildonmime0 (>= 2.15)
libqt4-core (>= 4.6.2~git20100224)
libqt4-gui (>= 4.6.2~git20100224)

which are some of the packages updated by PR1.2.

I already have libqt4-maemo5-* installed on the device, but I guess this doesn't help because the libraries are installed into /opt. And it fails to fulfill the dependencies because of the package name.

Right now it seems like I'm stuck in a situation where I can't do any development before PR1.2 is released. Is it possible to install these packages on the device before PR1.2 is released for N900? Or to revert the Scratchbox packages to Qt4.5?
 
krk969's Avatar
Posts: 754 | Thanked: 630 times | Joined on Sep 2009 @ London
#2
try linking with libqt4-maemo5 libraries and see if it works.
I was aware of this issue, so I refrained from updating my SDK , not really sure why the smart move to update the autobuilder without even having a release date from Nokia for PR1.2 !

anyways would you try and let me know, AFAIK libqt4-maemo5* libs will be maintained for futue QT4.7 development.

But be warned you wont be able to promote the app to testing.
__________________
Developer of :
Buddy - budget/expense manager ( website )
Showtime - a telly channel listing viewer/reminder ( website )
Travelapp - london underground status/planner ( website )
Batlevel - desktop widget for battery level ( website )

“I hear and I forget. I see and I remember. I do and I understand.”
 

The Following 2 Users Say Thank You to krk969 For This Useful Post:
Posts: 252 | Thanked: 252 times | Joined on Nov 2009
#3
Seems like I must have tried to run
fakeroot apt-get libqt4-maemo5*
while in X86 mode in scratchbox. Then it returned nothing, but now it is installing When I think about it I might even have tried before adding extras-devel to the sources.list. That's the bad thing about a reinstall - you never know what part you forgot to do before doing a rebuild.

Do you have a quick command to use when building against libqt4-maemo5? I'll try to look for it myself, but I've never built against another version before.

Promoting the application won't be an issue yet I guess that could wait until PR1.2 is out. Now I just want to get on with the development :-p
 
krk969's Avatar
Posts: 754 | Thanked: 630 times | Joined on Sep 2009 @ London
#4
just use the qmake from /opt/qt4-maemo5 !
__________________
Developer of :
Buddy - budget/expense manager ( website )
Showtime - a telly channel listing viewer/reminder ( website )
Travelapp - london underground status/planner ( website )
Batlevel - desktop widget for battery level ( website )

“I hear and I forget. I see and I remember. I do and I understand.”
 
Posts: 252 | Thanked: 252 times | Joined on Nov 2009
#5
I thought it would be something simple like that. I was actually trying it out now

I'll post back when I've tested it on the device.
 

The Following User Says Thank You to dragly For This Useful Post:
Posts: 252 | Thanked: 252 times | Joined on Nov 2009
#6
That fixed the issue with Qt but it still nags about the libhildon packages.

Missing packages:
libhildon1 (>= 2.2.10)
libhildonmime0 (>= 2.15)

However, that's only a problem with dpkg-buildpackage. Running the binaries directly works flawlessly now! I'll hopefully figure a way to avoid those dependencies, but until then I could just do it the hard way and copy binaries back and forth

Thanks for the help, krk969!
 
krk969's Avatar
Posts: 754 | Thanked: 630 times | Joined on Sep 2009 @ London
#7
Originally Posted by dragly View Post
That fixed the issue with Qt but it still nags about the libhildon packages.

Missing packages:
libhildon1 (>= 2.2.10)
libhildonmime0 (>= 2.15)

However, that's only a problem with dpkg-buildpackage. Running the binaries directly works flawlessly now! I'll hopefully figure a way to avoid those dependencies, but until then I could just do it the hard way and copy binaries back and forth

Thanks for the help, krk969!
you are welcome !

in case you are making a debian package, you could manually set dependencies to lower versions(PR1.1) of the hildon packages in the control file.
that might sort the issue with libhildon*
__________________
Developer of :
Buddy - budget/expense manager ( website )
Showtime - a telly channel listing viewer/reminder ( website )
Travelapp - london underground status/planner ( website )
Batlevel - desktop widget for battery level ( website )

“I hear and I forget. I see and I remember. I do and I understand.”
 
Posts: 252 | Thanked: 252 times | Joined on Nov 2009
#8
Originally Posted by krk969 View Post
in case you are making a debian package, you could manually set dependencies to lower versions(PR1.1) of the hildon packages in the control file.
that might sort the issue with libhildon*
I'm trying to figure this out, but it doesn't help to set the version in "Build-Depends". It appears that
Code:
${shlibs:Depends}
doesn't care about the value set there. I've also tried adding it to "Depends" but again,
Code:
${shlibs:Depends}
still prints out the newest libhildon* versions.

As you probably understand I'm not used to work with debian packages
 
Posts: 252 | Thanked: 252 times | Joined on Nov 2009
#9
Alright. I figured how to set the dependencies to older versions, but the autobuilder on garage.maemo.org still downloads the newest package versions, so now I end up with unmet dependencies on the dev-packages.

Code:
Unable to satisfy build-deps: libhildon1-dev (= 2.2.0-2+ultrastable1+0m5) libhildonmime-dev (= 2.1.3-1+0m5)
Is there anything else I need to do apart from setting the version in Build-Depends to make the autobuilder use the right version?
 
krk969's Avatar
Posts: 754 | Thanked: 630 times | Joined on Sep 2009 @ London
#10
Originally Posted by dragly View Post
Alright. I figured how to set the dependencies to older versions, but the autobuilder on garage.maemo.org still downloads the newest package versions, so now I end up with unmet dependencies on the dev-packages.

Code:
Unable to satisfy build-deps: libhildon1-dev (= 2.2.0-2+ultrastable1+0m5) libhildonmime-dev (= 2.1.3-1+0m5)
Is there anything else I need to do apart from setting the version in Build-Depends to make the autobuilder use the right version?
not sure why it didnt work really.
<= version should have worked for the build-Depends in the control file.
__________________
Developer of :
Buddy - budget/expense manager ( website )
Showtime - a telly channel listing viewer/reminder ( website )
Travelapp - london underground status/planner ( website )
Batlevel - desktop widget for battery level ( website )

“I hear and I forget. I see and I remember. I do and I understand.”
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 07:18.