Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 14 hrs, 18 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days, 2 hrs ago - more...
lardman |
2010-08-10
, 19:57
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#421
|
You should see some output regarding the plugin (whether it was detected, if it was loaded and if not what the error was) if you run mbarcode from a terminal.
| The Following User Says Thank You to lardman For This Useful Post: | ||
|
|
2010-08-10
, 23:26
|
|
Posts: 1,994 |
Thanked: 3,342 times |
Joined on Jun 2010
@ N900: Battery low. N950: torx 4 re-used once and fine; SIM port torn apart
|
#422
|
Originally Posted by lardman
It was noticed, but couldn't be loaded.
You should see some output regarding the plugin (whether it was detected, if it was loaded and if not what the error was) if you run mbarcode from a terminal.
Loading ///
Could not load ///
Any help is deeply appreciated.
|
|
2010-08-11
, 00:02
|
|
Posts: 111 |
Thanked: 80 times |
Joined on Oct 2009
|
#423
|
Originally Posted by Wikiwide
I don't know what specifically is the problem, but I strongly suspect that it's something with using g++ directly instead of running stuff through qmake.
It was noticed, but couldn't be loaded.
Loading ///
Could not load ///
Any help is deeply appreciated.
| The Following User Says Thank You to joshn53 For This Useful Post: | ||
|
|
2010-08-11
, 00:08
|
|
Posts: 1,994 |
Thanked: 3,342 times |
Joined on Jun 2010
@ N900: Battery low. N950: torx 4 re-used once and fine; SIM port torn apart
|
#424
|
Originally Posted by joshn53
Surely.
I don't know what specifically is the problem, but I strongly suspect that it's something with using g++ directly instead of running stuff through qmake.
I have added
#ifndef QT_STATICPLUGIN
#define QT_STATICPLUGIN
#endif
to the header, but nothing changed. Still could not load.
Of course, qmake knows some magic options for g++ command. The question is, what commands?
Right now, I removed ^M from mb.cpp and use these two commands to create mb.so.
g++ -Wall -fPIC -c mb.cpp
g++ -Wall -fPIC -shared mb.o -o mb.so
But nothing changed:
Could not load ///.
What else can be suggested?
"...The compilation of loadable modules are very much system-dependent..."
http://www.inf.usi.ch/carzaniga/sdl/doc/index.html
Can anybody help with it?
I hope I don't need to add -I///directory flags to g++, because if they were required, compilation wouldn't occur (header files wouldn't be found). So, what do optimisation -O3, -pipe, -fno-omit-frame-pointer and -fno-optimize-sibling-calls flags mean? Could they fix the problem?
Last edited by Wikiwide; 2010-08-11 at 04:39.
|
|
2010-08-11
, 06:03
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#425
|
Can you not use QMake?
I'm also rather concerned that you're not linking against the QtPlugin library (though you apparently have no errors, which is also a bit strange).
Can you post some code so we can take a look ourselves?
I'm also rather concerned that you're not linking against the QtPlugin library (though you apparently have no errors, which is also a bit strange).
Can you post some code so we can take a look ourselves?
| The Following User Says Thank You to lardman For This Useful Post: | ||
|
|
2010-08-11
, 06:14
|
|
Posts: 1,994 |
Thanked: 3,342 times |
Joined on Jun 2010
@ N900: Battery low. N950: torx 4 re-used once and fine; SIM port torn apart
|
#426
|
Originally Posted by lardman
Well... I prefer not to use QMake and Make. They generate too much of difficult-to-understand text inside qmake.pro and Makefile, and working without QMake would let me understand C++ and g++, while working with QMake leads me to Qt, do-this, don't-know-why-it-is-needed.
Can you not use QMake?
Originally Posted by lardman
I have heard (in Google) that QtPlugin is linked through QtGui. It's not the straightest way, but GUI is needed, anyway, I suppose.
I'm also rather concerned that you're not linking against the QtPlugin library (though you apparently have no errors, which is also a bit strange).
Originally Posted by lardman
Here it is, renamed to mb.cpp.txt.
Can you post some code so we can take a look ourselves?
Quite short, not more that 80 lines of code altogether.
|
|
2010-08-11
, 08:58
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#428
|
Right, I Debian-ised it and did a compile, I've attached the whole tarball here. It also contains output.txt which should show you the commands that were executed to get it to build.
Have a look and see if that's of use.
Have a look and see if that's of use.
| The Following User Says Thank You to lardman For This Useful Post: | ||
|
|
2010-08-11
, 09:25
|
|
Posts: 1,994 |
Thanked: 3,342 times |
Joined on Jun 2010
@ N900: Battery low. N950: torx 4 re-used once and fine; SIM port torn apart
|
#429
|
Originally Posted by lardman
Hmm... It's strange, but the .so which was built and packed into this .tar.gz, still gives this message "Could not load" when I run mbarcode from terminal. Even though I have given full r+w+x permissions to the .so.
Right, I Debian-ised it and did a compile, I've attached the whole tarball here. It also contains output.txt which should show you the commands that were executed to get it to build.
Have a look and see if that's of use.
It seems that this stubborn cpp is ready to ruin even qmake magic in order to prove that its impossible to build a module from it...
I'll continue to look at the qr-code plugin: maybe, there is a hint because the qr-code plugin works fine.
|
|
2010-08-11
, 21:23
|
|
Posts: 29 |
Thanked: 12 times |
Joined on Apr 2010
@ ~
|
#430
|
Originally Posted by Habmala
Hmm, using mbarcode again today I noticed the fps was much lower. It seems that when opening mbarcode with the lenscover closed the fps is really high (it was above 100 at one time) but when opening the cover it drops and stais down. The fps bug dosn't seem to happen if mbarcode is started with the lenscover open.
And also (not so minor perhaps) the fps are really racing here, im geting values between 50 and 70, IIRC it used to be at about half that in the last update..
cheers //Habmala
EDIT: Silly me posting at two AM, I would like to clarify that those last numbers are for when the lenscover is closed, upon opening the cover the fps drops rapidly to about 20 or 30.
