(Cross-posted to lazarus & fpc mailing lists)
I'm happy to announce a new binary version of Ludo Brands' and my fpcup FPC+Lazarus+packages SVN downloader/installer.
New binaries for Windows, Windows x64, Linux x86, Linux x64 can be downloaded from
https://bitbucket.org/reiniero/fpcup/downloads
Source is available too as well as older builds for OSX and Linux armel.
Compared to previous versions:
*** User visible: ***
- users can specify names instead of URLs for FPC SVN urls: 2.7.1,trunk,2.6.1,fixes,2.6.0
- same for Lazarus:
trunk,1.1,1.0
- --installdir option to specify "mother" directory where fpc+lazarus+settings reside. This makes the setup self-contained (apart from desktop shortcuts)
- default install location has been changed due to the previous point
- support for adding desktop icons on Linux (needs testing from users)
- user can specify log file location
- added rx, zeos testing, kzdesktop, ocrivist to list of "external modules" that fpcup can download and install for you if wanted
*** Internal/bug fixes: ***
- logging using TEventLog instead of writeln to file
- improved detection of SVN checkout/update problems (e.g. due to interrupted connection)
- started support for creating the Lazarus Inno Setup installer using the Lazarus-supplied build scripts
- updated list of Windows binutils downloads from FPC site
- fix for TProcess.Execute not detecting missing executables
- more resiliency in make distclean for(uses Jonas Maebe's tip of running make distclean 2x as well as removing fpmake.exe instances on Windows)
- ready for Win64=>Win32 cross compiling once FPC supports that
Directions for the future:
- finish Inno Setup creator, which will incidentally allow me to more easily test modifications e.g. for bug 22533 [Patch] Set up windows installer to allow multiple debuggers using $(TargetCPU)-$(TargetOS)
- more SVN checkout/update error detection (one user had an intermittent 3G connection and ran into svn problems that the current detection logic didn't seem to catch)
- add support for an ini file with options/profiles instead of having to add a lot of command line arguments (command line arguments support will likely remain to support batch scripting etc)
- GUI - preferably by others as my GUI-fu is not that strong...
Incidentally, I've used fpcup to set up a Jenkins build environment including database unit tests, which seems to work fine: http://wiki.lazarus.freepascal.org/Jenkins
Thanks to:
Ludo Brands
Arny the Turborascal, Miquel and IPGUy from the forum Jonas Maebe
and Marco van de Voort for his excellent Build FAQ.
Bug reports/improvements request welcome via the bitbucket site bugtracker or the fpcup thread in the forum (third party announcements)
Thanks,
Reinier