maemo.org - Talk - Post-development steps

Page 1 of 2

Next >

Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)

- Development (https://talk.maemo.org/forumdisplay.php?f=13)

- - Post-development steps (https://talk.maemo.org/showthread.php?t=60957)

Berserk

2010-08-23 19:59

Post-development steps

EDIT:
Hmm.. 56 views and no replies, I think I'm asking too much :D
I've just sent the upload request with the package name 'imagesetmaker', I took a look at other apps and figured that out, sorry for asking..

Maybe I'm just worrying too much, It'll probably be easier than I think.

For reference, the original post is here:

Quote:

Hi,

I just finished developing a well-featured stable version of my first Qt/C++ app "Image Set Maker" and I'd like to upload it to Extras-Devel, but I have too much questions before I can do that.. :(
Thanks to anyone who can brighten up my knowledge about the following:

- Upload requesting
I have a Maemo.org account :D
I need to fill in a package name.. is that the full app name ("Image Set Maker"), or something like "imagesetmaker_0.1_armel.deb"?

- Version numbers
When testing with Nokia Qt SDK, it always transfers "imagesetmaker_0.1_armel.deb" to my N900, can I set version numbers with maemo.org?

- Autobuilder instructions
I have close to zero knowledge about Linux commands.. I really appreciate the help given on the instruction page, but unfortunately, I can't make much sense of it :(

- Which files should I upload?
.pro, .cpp and .h files? And/or .o files, or anythins else?

Maybe a lot of this is made clear and easy with the Extras Assistant mentioned on this page... ?

I suppose that... when I am allowed to upload and and being given a package page, I can setup a bugtacker, track downloads, see test/vote when it's gotten to Extras-Testing etc.?

- Licencing
Basically I'm looking for a licence that says "Use it at no cost, spread it, read (and learn from?) the freely available source code.. but I'm the author and copyright holder. Please give credit, don't say you made the app, because I did."

I'm starting to think I missed something, since there are so many apps in Extras(-Devel, -Testing), and I haven't found a topic that covers these questions..
Please go easy on the "RTFM" remarks :D
Thanks!

kif	2010-08-24 10:54

Re: Post-development steps

Hi Berserk

> - Version numbers

I too have this problem, and have asked in the qt development forum.

I have gotten some answers that may solve the problem, but it requires some testing before I know if it is a solution.

I'll let you know the result.

Kim

DeargDoom

2010-08-24 11:05

Re: Post-development steps

Quote:

Originally Posted by kif (Post 796719)

> - Version numbers

I too have this problem, and have asked in the qt development forum.

I have gotten some answers that may solve the problem, but it requires some testing before I know if it is a solution.

I am very far from being an expert but following the wiki instructions works for me.

Berserk

2010-08-25 16:24

Re: Post-development steps

Well.. I finally got it to upload, thanks to the wiki's :D

But now the autobuild fails.. I copied the rules contents from the Packaging a Qt application page, but I'm not sure how to edit the rules file.
I think I have to replace "(APPNAME)", "(CURDIR)" and "(MAKE)"? I did anyway, except the "(MAKE)", I don't know what that needs to be. Don't know if replacing is good or not either..

At the top of the rules file, it says

Code:

#!/usr/bin/make -f

APPNAME := my_app_name

When I put "APPNAME := imagesetmaker" there, will every APPNAME be replaced? I don't get it..
I really feel stupid for not understanding the rules file :D

I just noticed/read that "libqt4-dev" needs to be added, so this line is now in my control file:
(Didn't have "libqt4-dev" before this post)

Code:

Build-Depends: debhelper (>= 5), autotools-dev, libhildon1 (>= 2.2), libqt4-dev

Berserk

2010-08-25 16:40

Re: Post-development steps

It seems to me that things like $(CURDIR) are some sort of system variables that don't need to be specified by the developer.. I'm just not sure :D

DeargDoom

2010-08-26 00:27

Re: Post-development steps

Quote:

Originally Posted by Berserk (Post 798050)

If I were you I would try and package it yourself and test installing it on your own device before uploading it to extras-devel. From your post I dont think you have done this yet.

Speaking for myself I found it quite helpful to use the qt-maemo-example package. Once you have that correctly building a package you can use it as a reference to see where you might be going wrong with your own packaging.

Berserk

2010-08-26 23:23

Re: Post-development steps

Thanks for pointing me in the right direction!
I've tried numerous times now.. and I think it's almost working now.
So far I've had *empty* .deb's showing up, only the bin and doc dir had files in it, no icons, .desktop or .service files..

After I've prepared the folders/sources and ran "mad dh_make", I edited the files inside the debian folder, then I ran "mad qmake", and right after that I ran the "mad dpkg-buildpackage -sa" command.

The problem is.. the files that should go into debian/<appname> show up somewhere else.
(I use WinXP with Nokia Qt SDK, both installed on E: )

My source files are in
E:\QtPrograms\... etc.

While building, the necessary files go into
E:\e\QtPrograms\... etc.

I know Linux doesn't work with drive letters, but how can I fix this? :P
EDIT: I could probably (?) put those folders in the .deb with an archiver, but that's not the way it should go, I think.

fcrochik

2010-08-26 23:36

Re: Post-development steps

Quote:

Originally Posted by Berserk (Post 799535)

I develop on the Nokia SDK but create my packages on scratchbox.

I have never tried to create a package using Mad but a common problem for me on scratchbox is that qmake adds the "absolute paths" to the Makefile. I always have to edit by hand the Makefile before creating the package in order for the autobuilder to work.

Just an idea ... if you think this maybe the case post your Makefile.

Felipe

Berserk

2010-08-26 23:41

Re: Post-development steps

Thanks! I'll try it, and post the Makefile in case it screws up..

In the meantime I've gotten the idea of replacing
INSTALL_ROOT=$(CURDIR)/debian/$(APPNAME) install
with
INSTALL_ROOT=debian/$(APPNAME) install
in debian/rules

Since CURDIR probably starts with /e/

EDIT: hmm.. I'd better not, I don't know where it will end up then :D

EDIT2:
INSTALL_ROOT=E:\QtPrograms\ImageSetMaker\0.1.2\imagesetmaker-0.1.2/debian/$(APPNAME) install
Gave a build error: "e:e:" not found

INSTALL_ROOT=QtPrograms\ImageSetMaker\0.1.2\imagesetmaker-0.1.2/debian/$(APPNAME) install
Partially worked, it put that whole path in the .deb package :D but with the needed folders/files! (DEBIAN, qtprograms and usr folders)
Also, "dh_shlibdebs" took quite long in the process.

INSTALL_ROOT=debian/$(APPNAME) install
Made E:\debian (wrong again)

EDIT3:
INSTALL_ROOT=$(APPNAME) install
Made E:\imagesetmaker

I'll post my Makefile then :D

Berserk

2010-08-27 00:12

Re: Post-development steps

Here's my Makefile (first half of it)
It does seem to recognise E:\
Could you help me with this one?

Code:

#############################################################################

# Makefile for building: imagesetmaker

# Generated by qmake (2.01a) (Qt 4.6.2) on: vr 27. aug 02:08:55 2010

# Project:  imagesetmaker.pro

# Template: subdirs

# Command: e:/NokiaQtSDK/Maemo/4.6.2/targets/fremantle-1030/bin/qmake.exe -unix -o Makefile imagesetmaker.pro

#############################################################################



first: make_default

MAKEFILE      = Makefile

QMAKE         = e:/NokiaQtSDK/Maemo/4.6.2/targets/fremantle-1030/bin/qmake.exe

DEL_FILE      = rm -f

CHK_DIR_EXISTS= test -d

MKDIR         = mkdir -p

COPY          = cp -f

COPY_FILE     = $(COPY)

COPY_DIR      = $(COPY) -r

INSTALL_FILE  = install -m 644 -p

INSTALL_PROGRAM = install -m 755 -p

INSTALL_DIR   = $(COPY_DIR)

DEL_FILE      = rm -f

SYMLINK       = ln -f -s

DEL_DIR       = rmdir

MOVE          = mv -f

CHK_DIR_EXISTS= test -d

MKDIR         = mkdir -p

SUBTARGETS    =  \

        sub-src



src/$(MAKEFILE): 

    @$(CHK_DIR_EXISTS) src/ || $(MKDIR) src/ 

    cd src/ && $(QMAKE) e:/qtprograms/imagesetmaker/0.1.2/imagesetmaker-0.1.2/src/src.pro -unix -o $(MAKEFILE)

sub-src-qmake_all:  FORCE

    @$(CHK_DIR_EXISTS) src/ || $(MKDIR) src/ 

    cd src/ && $(QMAKE) e:/qtprograms/imagesetmaker/0.1.2/imagesetmaker-0.1.2/src/src.pro -unix -o $(MAKEFILE)

sub-src: src/$(MAKEFILE) FORCE

    cd src/ && $(MAKE) -f $(MAKEFILE)

sub-src-make_default: src/$(MAKEFILE) FORCE

    cd src/ && $(MAKE) -f $(MAKEFILE) 

sub-src-make_first: src/$(MAKEFILE) FORCE

    cd src/ && $(MAKE) -f $(MAKEFILE) first

sub-src-all: src/$(MAKEFILE) FORCE

    cd src/ && $(MAKE) -f $(MAKEFILE) all

sub-src-clean: src/$(MAKEFILE) FORCE

    cd src/ && $(MAKE) -f $(MAKEFILE) clean

sub-src-distclean: src/$(MAKEFILE) FORCE

    cd src/ && $(MAKE) -f $(MAKEFILE) distclean

sub-src-install_subtargets: src/$(MAKEFILE) FORCE

    cd src/ && $(MAKE) -f $(MAKEFILE) install

sub-src-uninstall_subtargets: src/$(MAKEFILE) FORCE

    cd src/ && $(MAKE) -f $(MAKEFILE) uninstall



(There's some more here.. .prf files and stuff

If needed, I'll paste the remaining contents too

All times are GMT. The time now is 00:52.

Page 1 of 2

Next >

Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8