[maemo-developers] Help needed: packaging/distributing very small C app

From: Thomas Waelti twaelti at gmail.com
Date: Thu Apr 22 22:58:35 EEST 2010
Thanks everybody for your extensive support in documenting this process. While I encountered a few smaller stumbling blocks, it worked quite good (especially once the docs got updated by David)
I can report "halfway" success for now :-)

It was impossible to achieve the original target, having a smaller effort in building than in developing. Adapting C code and just building it took me an hour. Reading through the package docs plus two separate efforts to get it running took about 3 hours :-)

However, I was now able to build a 386 and an armel package the way it's described in the docs. Manually installing the armel deb on my N900 through dpkg -i gave me a working binary. Hooray!
(Now I'm where I've been before, a working binary on MY device :-)

Unfortunately, my effort to share this in the proper way (uploading the sources package) did now fail in the autobuilder:

The reason is simple:
- No package 'mafw' found
- No package 'mafw-shared' found

How to proceed? Is this indeed a problem of the autobuilder (no mawf libs) or of my source package?

Best regards


> On 2010-04-19 16:50, Dave Neary <dneary at maemo.org> wrote:
>>Dave Neary wrote:
>>> I documented the packaging of a C app (using autotools for building) a
>>> while back in the wiki:
>>> http://wiki.maemo.org/Packaging#A_concrete_example_-_rot13
>>> This starts with a tiny C program & the minimum autotools stuff to build
>>> it (I don't include these - would that be useful?) and guides you
>>> through making a .deb.
>>So I included an A to Z for this project, with the 3 files you need to
>>create a .tar.gz using standard autotools. Let me know if it's useful.
> I updated this with some newer syntax and a link to some (very detailed)
> documentation in the wiki. I second autotools as a way to make packaging
> easier (once you understand them).
More information about the maemo-developers mailing list