Reply
Thread Tools
Posts: 299 | Thanked: 241 times | Joined on Oct 2009 @ Singapore
#1
Hi,

So, I've got my app to compile nicely on my PC in the MADDE environment. No issues. I've tried most of the suggestions in this thread, at least to the extent that I understood what I needed to do. Now I upload it to Garage and I get the following (qmake: Command not found):

Code:
# Add here commands to clean up after the build process.
/scratchbox/tools/bin/make clean
make[1]: Entering directory `/home/builder1/maemo-fremantle-armel-extras-devel/work/qteachme-0.1'
Makefile:106: *** multiple target patterns.  Stop.
make[1]: Leaving directory `/home/builder1/maemo-fremantle-armel-extras-devel/work/qteachme-0.1'
make: [clean] Error 2 (ignored)
dh_clean 
 dpkg-source -b qteachme-0.1
dpkg-source: warning: unknown information field `Homepage' in input data in general section of control info file
dpkg-source: building qteachme in qteachme_0.1.tar.gz
dpkg-source: building qteachme in qteachme_0.1.dsc
 debian/rules build
dh_testdir
# Add here commands to configure the package.
qmake
make: qmake: Command not found
make: *** [configure-stamp] Error 127
Is the problem that I am using MADDE, but Garage is using Scratchbox so I have to provide a different .pro or rules file when I upload? How would I do that? Now, mad dpkg-buildpackage creates all the files that I need to upload.
At the moment my key files look as follows:

Code:
TARGET      = qteachme
HEADERS += mainwindow.h \
    settings.h \
	importflashcard.h
SOURCES += main.cpp \
    mainwindow.cpp \
    settings.cpp \
	importflashcard.cpp
FORMS += mainwindow.ui \
    settings.ui \
	importflashcard.ui
LEXSOURCES  += #LEXS#
YACCSOURCES += #YACCS#

INCLUDEPATH +=
LIBS        +=
DEFINES     +=

# All generated files goes same directory
OBJECTS_DIR = build
MOC_DIR     = build
UI_DIR      = build

DESTDIR     = build
TEMPLATE    = app
DEPENDPATH  +=
VPATH       += src uis
CONFIG      -= 
CONFIG      += debug
#QT=core gui sql xml phonon
QT=core gui sql xml

INSTALLS    += target
target.path  = /usr/bin/

INSTALLS    += desktop
desktop.path  = /usr/share/applications/hildon
desktop.files  = data/qteachme.desktop

INSTALLS    += service
service.path  = /usr/share/dbus-1/services
service.files  = data/qteachme.service

# INSTALLS    += db
# db.path  = /home/user
# db.files  = data/qteachme.db

INSTALLS    += sample
sample.path  = /home/user
sample.files  = data/Chinese.txt

INSTALLS    += icon64
icon64.path  = /usr/share/icons/hicolor/64x64/apps
icon64.files  = data/64x64/qteachme.png

INSTALLS    += icon48
icon48.path  = /usr/share/icons/hicolor/48x48/apps
icon48.files  = data/48x48/qteachme.png

# INSTALLS    += audio
# audio.path  = /home/user/audio
# audio.files  = data/test.aac

#
# Targets for debian source and binary package creation
#
debian-src.commands = dpkg-buildpackage -S -r -us -uc -d
debian-bin.commands = dpkg-buildpackage -b -r -uc -d
debian-all.depends = debian-src debian-bin

#
# Clean all but Makefile
#
compiler_clean.commands = -$(DEL_FILE) $(TARGET)

QMAKE_EXTRA_TARGETS += debian-all debian-src debian-bin compiler_clean

And

Code:
#!/usr/bin/make -f
# -*- makefile -*-
# Sample debian/rules that uses debhelper.
# This file was originally written by Joey Hess and Craig Small.
# As a special exception, when this file is copied by dh-make into a
# dh-make output file, you may use that output file without restriction.
# This special exception was added by Craig Small in version 0.37 of dh-make.

# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1

# CFLAGS = -Wall
#
# ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
#	CFLAGS += -O0
# else
#	CFLAGS += -O2
# endif




configure: configure-stamp
configure-stamp:
	dh_testdir
	# Add here commands to configure the package.

	qmake
#	qmake-qt4
#	/opt/qt4-maemo5/bin/qmake-qt4
	touch configure-stamp


build: build-stamp

build-stamp: configure-stamp  
	dh_testdir

	# Add here commands to compile the package.
	$(MAKE)
#	$(MAKE) CFLAGS="$(CFLAGS)"

	#docbook-to-man debian/qteachme.sgml > qteachme.1

	touch $@

clean: 
	dh_testdir
	dh_testroot
	rm -f build-stamp configure-stamp

	# Add here commands to clean up after the build process.
	-$(MAKE) clean

	dh_clean 

install: build
	dh_testdir
	dh_testroot
	dh_clean -k 
	dh_installdirs

	# Add here commands to install the package into debian/qteachme.
	$(MAKE) INSTALL_ROOT="$(CURDIR)"/debian/qteachme install


# Build architecture-independent files here.
binary-indep: build install
# We have nothing to do by default.

# Build architecture-dependent files here.
binary-arch: build install
#	dh_maemo_package_icons
	dh_testdir
	dh_testroot
	dh_installchangelogs 
	dh_installdocs
	dh_installexamples
#	dh_install
#	dh_installmenu
#	dh_installdebconf	
#	dh_installlogrotate
#	dh_installemacsen
#	dh_installpam
#	dh_installmime
#	dh_python
#	dh_installinit
#	dh_installcron
#	dh_installinfo
	dh_installman
	dh_link
	dh_strip
	dh_compress
	dh_fixperms
#	dh_perl
#	dh_makeshlibs
	dh_installdeb
	dh_shlibdeps
	dh_gencontrol
	dh_md5sums
	dh_builddeb
#	dh_maemo_package_icons -r

binary: binary-indep binary-arch
.PHONY: build clean binary-indep binary-arch binary install configure
 
Posts: 432 | Thanked: 645 times | Joined on Mar 2009
#2
Hi,

do you have "libqt4-dev" in your build-dependencies in your debian/control file? The line should look like:

Code:
Build-Depends: debhelper (>= 5), libqt4-dev
Daniel
 

The Following User Says Thank You to danielwilms For This Useful Post:
krk969's Avatar
Posts: 754 | Thanked: 630 times | Joined on Sep 2009 @ London
#3
also its a good practice to put

QT+= core gui sql xml
instead of
QT=core gui sql xml

so you dont override, unless you are sure of what you are doing
Maybe MADDE is generating this file, in that case it should be fine.
__________________
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 User Says Thank You to krk969 For This Useful Post:
shep's Avatar
Posts: 85 | Thanked: 65 times | Joined on Jan 2010 @ Ireland
#4
Originally Posted by magnuslu View Post
Hi,

So, I've got my app to compile nicely on my PC in the MADDE environment. No issues. I've tried most of the suggestions in this thread, at least to the extent that I understood what I needed to do. Now I upload it to Garage and I get the following (qmake: Command not found):
I don't understand this stuff very well...but I always follow this post and it get's me through

Good Luck!

Shep
__________________
- Hey! I also do other stuff Touchscreen apps for Windows and Android
- Currently developing a Diet Assistant/Weight Tracker for the N900
 

The Following User Says Thank You to shep For This Useful Post:
Posts: 299 | Thanked: 241 times | Joined on Oct 2009 @ Singapore
#5
Thanks everyone!

libqt4-dev clinched it! After adding that I hit a few other issues, bug I got reasonable error messages, so I could fix them.

At last!!!

Now I only have to fix a couple of usability issues before I announce it.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 11:43.