Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 19 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 2 days, 14 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 23 hrs ago - more...
|
2010-03-24
, 11:49
|
|
Posts: 432 |
Thanked: 645 times |
Joined on Mar 2009
|
#22
|
Originally Posted by davidmaxwaterman
MADDE is not really meant to work with external libraries. But have you got the code compiled, right? Do you have the library installed on your device? If this is a compiler issue, try to set the full path to your library in the pro file. This might work.
[1] Actually, I noticed I added 'LIBS += lib/libQtLocation.so' rather than something like 'LIBS += -Llib', but it still seems to pick up the other libraries in their so I guess it's clever like that.
Daniel
|
|
2010-03-24
, 11:56
|
|
Posts: 432 |
Thanked: 645 times |
Joined on Mar 2009
|
#23
|
Hi all,
instructions on how to combine QtCreator with MADDE using Linux are now available:
http://wiki.maemo.org/MADDE/QtCreato...tion_for_linux
Please let me know if something does not work as expected.
Daniel
instructions on how to combine QtCreator with MADDE using Linux are now available:
http://wiki.maemo.org/MADDE/QtCreato...tion_for_linux
Please let me know if something does not work as expected.
Daniel
|
|
2010-03-24
, 12:14
|
|
Posts: 267 |
Thanked: 183 times |
Joined on Jan 2010
@ Campinas, SP, Brazil
|
#24
|
Originally Posted by pbouda
I tried to follow the Mac instruction and I also used google translate to follow the german tutorial in english, but I always have this error when I try to 'rebuild' the debugging helper: "The QT version has no toolchain". But I installed QT Creator 1.3.82 revision 81c1f6e712 and MADDE 0.6.14 with all options and I was able to create a qthello using MADDE.
And followed the Mac instructions. I have a german tutorial here:
http://www.mobileqt.de/wiki/wie_man_...tor_integriert
Is there some path I need to set, some variable, something? Couldn't find in the guide. That's why I think there should be a specific integration page for GNU/Linux.
This is the screenshot of my problem:
|
|
2010-03-24
, 13:56
|
|
Posts: 123 |
Thanked: 21 times |
Joined on Sep 2009
|
#25
|
Originally Posted by danielwilms
What external libraries? The only libraries I'm using are Qt ones - they're just newer than the ones in Madde (and there are additional ones).
MADDE is not really meant to work with external libraries.
But have you got the code compiled, right?
Do you have the library installed on your device?
If this is a compiler issue, try to set the full path to your library in the pro file. This might work.l
Anyway, I'll see when I get home. Thanks.
Max.
|
|
2010-03-24
, 14:38
|
|
Posts: 432 |
Thanked: 645 times |
Joined on Mar 2009
|
#26
|
Originally Posted by davidmaxwaterman
With external libraries, I meant libraries, which are not part of the official rootstrap, no matter which ones.
What external libraries? The only libraries I'm using are Qt ones - they're just newer than the ones in Madde (and there are additional ones).
Originally Posted by davidmaxwaterman
Have you seen this post? There is as well MADDE mentioned, whith instructions on how to integrate 4.6 there.
Right, but I'm not convinced my method is valid. IINM, I'm compiling the source using Qt 4.5.2 qmake, moc and includes (as well as the QtMobility includes), and linking with the Qt 4.6.2 libs and QtMobility libraries.
Only the Qt 4.6.2 and Mobility libs.
Well, I will check more deeply when I get home, but I think this is basically the same as if I change a library in a way that breaks the ABI, and so binaries linking with it will run, but crash when they call a methods that's been changed.
Anyway, I'll see when I get home. Thanks.
Max.
Daniel
Last edited by danielwilms; 2010-03-24 at 14:41.
|
|
2010-03-24
, 18:50
|
|
Posts: 123 |
Thanked: 21 times |
Joined on Sep 2009
|
#27
|
Originally Posted by danielwilms
OK, though that's quite a big restriction. I wonder when QtMobility will be part of the SDK at all...
With external libraries, I meant libraries, which are not part of the official rootstrap, no matter which ones.
Have you seen this post? There is as well MADDE mentioned, whith instructions on how to integrate 4.6 there.
I'm not sure how I can get around this issue, so I'm moving back to scratchbox, perhaps only using mad for packaging. At least my directory structure is mad-ready
Thanks!
Max.
|
|
2010-03-25
, 07:29
|
|
Posts: 123 |
Thanked: 21 times |
Joined on Sep 2009
|
#28
|
I did have a quick play with downloading the maemo5 version of Qt 4.6.2 and seeing if that would compile inside Madde....but it borks really quickly.
Shouldn't that work? I'd guess it shouldn't need anything apart from the compiler toolchain in order to build.
Shouldn't that work? I'd guess it shouldn't need anything apart from the compiler toolchain in order to build.
|
|
2010-06-01
, 04:35
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#29
|
Originally Posted by danielwilms
Do you mean this as in "it's not officially supported", "it's not our primary/initial concern" or "it won't work"?
MADDE is not really meant to work with external libraries.
I understand the purpose of Qt Mobility and Qt in general, in terms of portability, but Qt+extensions can't cover everything. Specifically, the work I'm doing at my university involves a couple of libraries developed independently by members of our team (this, for one), and I'd be a bit concerned if the new SDK is designed in such a way that using those will be painful.
|
|
2010-06-01
, 07:30
|
|
Posts: 432 |
Thanked: 645 times |
Joined on Mar 2009
|
#30
|
Originally Posted by jaem
Do you mean this as in "it's not officially supported", "it's not our primary/initial concern" or "it won't work"?
I understand the purpose of Qt Mobility and Qt in general, in terms of portability, but Qt+extensions can't cover everything. Specifically, the work I'm doing at my university involves a couple of libraries developed independently by members of our team (this, for one), and I'd be a bit concerned if the new SDK is designed in such a way that using those will be painful.
It means it is possible but not officially supported. What you could do is cross-compile those libraries and then point in the *.pro file with the whole path to that libraries. This should work. Other possibilities are under discussion, mostly in public, and I hope we can give updates on this soon.
Daniel
| The Following User Says Thank You to danielwilms For This Useful Post: | ||
These are the hacks I made :
If someone has some indication of what might be wrong with this that would cause a run-time crash (my app just stops, without any 'crash dialog', so I'm not convinced it's dumping core), I'd love to hear suggestions.
Thanks!
Max.
PS. Why doesn't this 'list' icon on this forum work? It's supposed to put numbers on them, but I have to put them in manually...annoying
[1] Actually, I noticed I added 'LIBS += lib/libQtLocation.so' rather than something like 'LIBS += -Llib', but it still seems to pick up the other libraries in their so I guess it's clever like that.