1. reiniero
  2. fpcup


fpcup /

The default branch has multiple heads

Filename Size Date modified Message
104 B
12.7 KB
129.8 KB
4.6 KB
19.7 KB
3.8 KB
418 B
16.1 KB
55.9 KB
27.5 KB
91.0 KB
1.9 KB
1.2 KB
8.7 KB
3.5 KB
4.3 KB
1.7 KB
10.6 KB
28.1 KB
40.4 KB
54.8 KB
10.7 KB
50.9 KB
5.3 KB
12.1 KB
49.6 KB
4.0 KB
8.1 KB
7.5 KB

What is it?
fpcup is a tool that gets the current version of FreePascal Compiler (FPC) and Lazarus IDE from their subversion repositories and compiles/installs them.
It adds CHM documentation and configure the Lazarus help for you.

It also creates a shortcut on your desktop that points to the new Lazarus installation.

Meant to be used side by side with other FPC/Lazarus installations. It creates a separate primary config path directory for the new Lazarus installation, so it doesn't interfere with existing Lazarus installs.
It's open source software, please see the code for the license.
Run fpcup --help for command line options.

Why yet another tool?
I was disappointed in LazUpdater, a GUI program that has similar goals as the code seems to be too complex.
I also was tired of writing batch scripts and then having to press all kinds of buttons/fiddling with things to get it working.

On Windows: should be none.
If needed, this tool will download an svn client, the required binutils (make.exe etc) and a bootstrap FPC compiler for you.

On Linux:
- the binutils (make etc); e.g. in a package called build-essential
- bunzip2 (probably present in most distributions)
- unzip
- subversion client
E.g. on Debian or Ubuntu, do something like:
sudo aptitude install build-essential subversion unzip

On OSX: only tested with XCode installed; no requirements found

How does it work?
FPCUp is a fancy batch script written in FPC/Lazarus that simply downloads FPC and Lazarus from SVN and compiles them ;)
You run it, with options if necessary (see fpcup --help).
When done, it should have created a Lazarus_trunk shortcut on your desktop (Windows) or shell script in your home directory (Unix/Linux).
Start this to start your new Lazarus instance.
fpcup sets up a separate primary config path to store Lazarus settings separate from other installs.
You need to run the script/shortcut because it tells your Lazarus where to find that primary config path.

Technical explanation
If you want to improve or extend fpcup, here's a more detailed description of what it does.

Note that some steps will not be executed depending on the modules chosen by the user.
By default, all modules will be run; the help module is selected by default and pulls in bigide.
fpcup for Windows is 32 bit, but wincrossx64 will be run so users can compile 64 bit applications with Lazarus.

1. Setup, checking/downloading prerequisites:
- fpcup creates a shortcut on your desktop (Windows) or home directory shell script to fpcup with all the options you chose, so you don't have to type it all again
- On Windows, it checks whether make.exe and unzip.exe are present in the binutils directory (default or user-specified).
If not, it downloads them.
- It checks if make.exe is GNU make, and not e.g. Delphi/Borland make.
- It checks whether a Subversion client is available. On Windows: if there isn't, it downloads one.
- If bootstrap compilers need to be downloaded, a certain unarchiver utility is needed, depending on the way the compiler is compressed.
fpcup checks unzip.exe for Windows, gnutar for OSX, and bunzip2 for Linux.
- It checks if there is a valid FPC compiler in the bootstrap directory the user specified (or default).
If it doesn't exist, it downloads a bootstrap compiler.

2. Getting and compiling FPC
- It checks out or updates FPC using Subversion.
- It compiles FPC using the bootstrap compiler.
- It creates a valid fpc.cfg for the new compiler.
- On OSX/Linux: it creates a dummy fpc.sh designed to filter out existing system wide fpc.cfg (e.g. /etc/fpc.cfg) and places that in the FPC directory

3. Getting and compiling Lazarus
- It checks out or updates Lazarus using Subversion.
- It compiles Lazarus using the installed FPC compiler (Linux/OSX: fpc.sh) and fpc.cfg
- When done, it creates a shortcut on your desktop (Windows) or shell script in home directory to the newly installed Lazarus
- It does the same using make bigide, in order to get as many .lpk files compiled and included as possible
- It creates a minimum configuration (environmentoptions.xml) in a separate primary-config-path, or updates that config with: the compiler, the FPC source directory, make location, gdb location, help files location.
- fpcup compiles the Lazarus documentation editor (LazDE) using lazbuild in the newly compiled Lazarus directory
- fpcup compiles the Lazarus data desktop using lazbuild in the newly compiled Lazarus directory

4. Getting help
- It compiles the Lazarus lhelp CHM viewer (LazDE) using lazbuild in the newly compiled Lazarus directory
- It gets the FPC chm documentation if not already present
- It compiles the Lazarus CHM help

Cross compiler extensions
fpcup has a facitility to extend its functionality using cross compiling modules. These are classes that inherit from the fpcup TCrossInstaller class defined in m_crossinstaller.pas
An example is the Windows 32=>Windows 64 cross compile unit in m_crosswin64.pas. Note that this is a simple version, as there is no need for separate binutils and library paths.
These modules get registered automatically when compiled into the fpcup code.

LCL limitations
The Lazarus LCL can be installed in different directories depending on architecture. This is very helpful when building cross compilers, as the compiled units and binutils do not interfere with each other.
fpcup uses this approach for building cross compilers.

However, there is no provision for separating LCL units for multiple widgetsets. If you compile e.g. GTK2 and QT LCL widgetsets for the same platform, one will overwite the other. This means that fpcup cannot manage multiple widgetsets either.
If you want to use multiple widgetsets, best practice is to use separated Lazarus directories (option --lazdir in fpcup).

A big problem in designing this utility was to keep systemwide fpc.cfg on Unix/Linux from interfering with our FPC install.
It seems the only way around this is to write a fpc proxy (fpc.sh) that explicitly ignores any fpc.cfgs).

To check whether this works:
cd ~/<yourlazarusdirectory>
#Check system wide settings (look for FPC, FPC version, FPCDIR and UnitsDir:
make fpc_baseinfo | less
#Check (look for FPC, FPC version, FPCDIR and UnitsDir:
#this should pick up the proper unit path, fpcdir and version from the fpcup-installed fpc version
make fpc_baseinfo FPC=~/<yourfpcdirectory>/bin/fpc.sh
~/<yourfpcdirectory>/bin/fpc.sh -vut # or something?

Additionally, on both Windows and Unix we add our own binutils to the beginning of the path when calling make.
This ensures that e.g. existing Delphi or cygwin make.exe does not mess with our installation.
This is probably a bigger problem on Windows than on Linux/Unix

Still in development, but does work to keep my development copies of FPC fixes_2.6 and Lazarus up to date on Windows.

For reportiing bugs, suggestions, patches.
- Lazarus forum thread:
- Bitbucket issue tracker

Help output:
A recent fpcup --help shows this:

An FPC/Lazarus downloader/updater/installer
Open source freeware (modified LGPL/BSD), see:

This program will download the FPC and Lazarus sources
from the source Subversion/SVN repositories,
compile, and install.
Result: you get a fresh, up-to-date Lazarus/FPC installation.
fpcup compiled with: FPC 2.6.1 on 2012/02/21 18:03:20
for CPU: i386 on Win32
Everything below is optional...

fpcup --<options>

fpcup can work with modules - see "only", "skip" below
List of modules and standard installation action:
Std Name           Description
on  FPC            Free Pascal compiler
on  lazarus        LCL (and IDE if not crosscompiling)
off bigide         IDE with extra components. Selects lazarus.
on  help           Lazarus+FPC help. Also selects bigide.
on  wincrossx64    Lazarus Win32=>Win64 cross compiler.
                   Note: also installs lazarus 32 bit IDE.
on  doceditor      Lazarus Doceditor. Also selects lazarus.
on  lazdatadesktop Data desktop tool. Also selects lazarus.
Because help is installed by default, it pulls in bigide and
the results that all modules above get installed.
(except wincrossx64 if not on Windows, of course)

Options are not required; they include:
 help                  Show this text
 binutilsdir=<dir>     Windows only:
                       Directory where make, patch etc
                       (the binutils) are located. If make does not
                       exist, binutils will be downloaded there.
                       Default c:\development\fpcbootstrap\
                       Note: the binutils are copied to the
                       FPC directory for use by FPC. This gives
                       a more standard FPC environment.
 clean                 Don't build.
                       If no skip and only options given:
                       DELETE entire Lazarus/FPC directories
                       Else: clean up only certain modules,
                       only deleting temporary items.
 cputarget=<name>      CPU target for cross_compiling.
                       <name> has to be one of the following:
 fpcbootstrapdir=<dir> An existing FPC compiler is needed to compile the FPC
                       sources. Specify location with this option; if no
                       compiler found here, FPCUp will download one there.
                       Default: c:\development\fpcbootstrap\
                       or ~\fpcbootstrap\
 fpcdir=<dir>          Target FPC dir, default c:\development\fpc\
                       or ~\fpc\
 fpcURL=<URL>          SVN URL from which to download; default: fixes_2.6:
 fpcOPT=<options>      Options passed on to the FPC make as OPT=options.
                       E.g.: --fpcOPT="-gl -dSAX_HTML_DEBUG -dUSE_MINGW_GDB"
 fpcrevision=<number>  Revert to FPC SVN revision <number>
 fpcuplinkname=<name>  Name of the shortcut to the fpcup script.
                       On Windows: a desktop shortcut.
                       On other systems: a shell script in your home directory.
                       If empty specified, no shortcut will be produced.
                       Default: fpcup_update
                         or <lazlinkname>_update if lazlinkname specified
 lazdir=<dir>          Target Lazarus dir, default c:\development\lazarus\
                       or ~\lazarus\
 lazlinkname=<name>    Name of the shortcut to the Lazarus install.
                       On Windows: a desktop shortcut.
                       On other systems: a shell script in your home directory.
                       If empty specified, no shortcut will be produced.
                       Default: Lazarus_trunk
 lazrevision=<number>  Revert to Lazarus SVN revision <number>
 lazURL=<URL>          SVN URL from which to download; default:
                       trunk (newest version):
 lazOPT=<options>      Options passed on to the Lazarus make as OPT=options.
 lclplatform=<name>    LCL widget set. <name> has to be one of the following:
 noconfirm             No confirmation asked. For batch operation.
 only=<values>         Update/build or clean only the modules specified.
                       The module list is separated by commas.
                       See above for a list of modules.
 ostarget=<name>       OS target for cross_compiling.
                       <name> has to be one of the following:
                       Analogous to Lazarus primary-config-path parameter.
                       Determines where fpcup will create or use as primary
                       configuration path for the Lazarus it installs/updates.
                       Default: empty; then a OS dependent configuration
                       path is used; directory name lazarusdevsettings.
 skip=<values>         Do not update/build or clean modules.
                       The module list is separated by commas.
                       See above for a list of modules.
 verbose               Show output from svn and make

Share and enjoy!

FPCUp finished.