[Lazarus] fppkg and lazarus packages

Graeme Geldenhuys graemeg.lists at gmail.com
Fri Sep 3 17:15:24 CEST 2010

On 3 September 2010 11:12, Joost van der Sluis <joost at cnoc.nl> wrote:
> You'd better do the same as we did with lnet. Add a fpmake file to
> tiOPF/fpGUI's repositories. If that works ok. (Check if fpmake archive
> works, and if you can use that archive to install the package, without
> any other resources) we can build and add it to the server.

fpGUI now has a fully working fpmake.pp file with unit dependencies. I
could successfully do a 'fpmake archive' ,  unpack in temp folder,
'fpmake build' & 'fpmake install' without problems.

fpmake install did try and install to /usr/local/lib/fpc/2.4.3/units/..../fpgui

which it didn't have write access, so i use -B parameter to redirect
it to /opt/fpc-addons/ which worked fine.

I was just about to comment that it would be nice if we could see what
version of the package we have installed, then I saw the fpunit.conf
file which gives all the details, including a nice checksum. :-)

One small thing I did notice is the fpmake was not so happy with
fpGUI's version numbering. I let fpmake.pp read the version number
constant from the fpGUI src directory include file. fpGUI version
format is:  '0.7.166.g010ab';

0.7 is the major an minor number (the last release).
166 is the number of commits since 0.7 release
g010ab is the commit id (short version of SHA1 identifying specific revision)

Normally a script file automatically generates the version number for
me, when I build fpGUI.

fpmake trimmed that version number down to

What version number formats does fpmake support. eg: some projects use
a date (v0.7-2010-09-03), others use r<subversion_commit>
(v0.7.r43234) etc..

So maybe fpmake should be more flexible with the last two areas of the
version number?  Just a thought.

  - Graeme -

fpGUI - a cross-platform Free Pascal GUI toolkit

More information about the Lazarus mailing list