![]() |
2009-11-27
, 09:50
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#2
|
The Following 3 Users Say Thank You to lardman For This Useful Post: | ||
![]() |
2009-11-27
, 10:17
|
Posts: 252 |
Thanked: 252 times |
Joined on Nov 2009
|
#3
|
![]() |
2009-11-27
, 10:53
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#4
|
![]() |
2009-11-27
, 11:39
|
Posts: 252 |
Thanked: 252 times |
Joined on Nov 2009
|
#5
|
I'm not going to do libmagick++ though I'm afraid. What is the app you are trying to build?
If it's just a barcode scanner, try mbarcode (in extras-devel).
![]() |
2009-11-27
, 12:11
|
Posts: 1,208 |
Thanked: 1,028 times |
Joined on Oct 2007
|
#6
|
Thanks for the quick reply
I'm afraid I don't know much about packaging libraries. As you probably figure I'm pretty new to developing for Maemo (and Debian in general). How would I go ahead to port the packages and push them to the repositories?
If you have a look in the sources for zbar-0.10, there is a folder named "qt". I'm not sure what compile options one needs to compile it with the Qt bindings, but they are included in the Debian repos as the package libzbarqt-dev.
![]() |
2009-11-27
, 14:51
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#7
|
![]() |
2009-11-27
, 16:27
|
Posts: 252 |
Thanked: 252 times |
Joined on Nov 2009
|
#8
|
The problem you may well have using the Qt zbar plugin (which I assume includes a link to the camera) is that of focusing the camera. That's why I'm just using the raw zbar decoder, and not the GTK+ plugin.
I'm actually pursuing the same goal as you apparently, though I'm not using Qt (yet). Where are you thinking of obtaining your review information? AWS?
Please let me know if you would like to collaborate.
![]() |
2009-11-27
, 21:08
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#9
|
![]() |
2009-11-28
, 01:46
|
Posts: 252 |
Thanked: 252 times |
Joined on Nov 2009
|
#10
|
QT += network \ xml TARGET = informi TEMPLATE = app CONFIG += link_pkgconfig PKGCONFIG = zbar-qt SOURCES += main.cpp \ mainwindow.cpp HEADERS += mainwindow.h FORMS += mainwindow.ui
#ifndef MAINWINDOW_H #define MAINWINDOW_H #include <QtGui/QMainWindow> namespace Ui { class MainWindow; } class MainWindow : public QMainWindow { Q_OBJECT public: MainWindow(QWidget *parent = 0); ~MainWindow(); private: Ui::MainWindow *ui; private slots: void slotTest(); void slotDecode(int type, const QString &text); }; #endif // MAINWINDOW_H
#include "mainwindow.h" #include "ui_mainwindow.h" #include <zbar/QZBar.h> using namespace std; using namespace zbar; MainWindow::MainWindow(QWidget *parent) : QMainWindow(parent), ui(new Ui::MainWindow) { ui->setupUi(this); connect(ui->btn_test,SIGNAL(clicked()),SLOT(slotTest())); } MainWindow::~MainWindow() { delete ui; } void MainWindow::slotTest() { QZBar *zbar = new QZBar(this); zbar->setVideoDevice("/dev/video0"); zbar->setVideoEnabled(true); connect(zbar,SIGNAL(decoded(int,QString)),SLOT(slotDecode(int,QString))); } void MainWindow::slotDecode(int type, const QString &text) { ui->lbl_test->setText(text); }
The Following User Says Thank You to dragly For This Useful Post: | ||
I am devoloping an application for Maemo 5 and use two libraries not included in the Maemo repositories. These are libzbarqt and libmagick++.
I was wondering what the best approach is to include these with my application? They are available in the Debian repositories, but asking a user to download these and install them manually seems like too much of a hassle for most users. The same goes for asking them to do a manual .configure && make && make install.
Is it possible to include Debians repositories for these packages, or would that crash the device? Or are there any preferred methods to include such libraries with a Maemo application?
Last edited by dragly; 2009-11-27 at 09:34.