Portable Development Test 8.1 update 11/9/16
Application: Lazarus
Category: Development
Description: Lazarus is a Delphi compatible cross-platform IDE for Rapid Application Development. It has variety of components ready for use and a graphical form designer to easily create complex graphical user interfaces.
Download:LazarusPortable_1.4.5_Development_Test_8.1.paf
MD5Sum: 65752cd92583031d40004100cb4d8cec
Size: [~142 MB Download / ~1009 MB Installed]
Release Notes:
(ReleaseLog: 11/9/16)
- replaced LazarusPortable.exe in App\lazarus folder (it opens a new window with the same project 
) (MD5 2fc490be3eed15116e238b477b8a75d5 LazarusPortable.exe)
(ReleaseLog: 11/8/16)
- DefaultData will not be changed, it contain files to setup LazarusPortable newly and I have renamed lazarus.exe to lazarus_initial.exe which will be copied by First Start
- config is stored in DataDir
(ReleaseLog: 11/5/16)
- it can easily be adjusted to work with Lazarus 1.0 to 1.7
- LazarusPortableUnregFileAssociation.reg (Other\Source) to delete FileAssociations from HKEY_LOCAL_MACHINE (Windows 10) with admin rights
- LazarusConfigChanger (profile could not be changed, if lazarus is running!) it changes the profiles 
- multiple profiles (for example: LazarusPortable detects fpc 2.6.5 (2.6.0 / 2.7.1 / 3.0.0) on FirstStart, if you have more versions of fpc installed; later you must edit Data\FPCSettings.ini and add a new profile by yourself
- BackupTool stores DataDir in Folder Backups as zip file (except Data\temp)
- registers file extention lpr, lpi, pas, lfm, lpk (experimental)
- multiple instances (Shortcut STRG+M opens a new window, during lazarus is running, that's why a special file LazarusPortable.exe is in App\lazarus folder)
- updates now AppDir, DataDir, Temp and fpc.cfg is updated by LazarusPortable.exe (custum.nsh)
- config is stored in DataDir (important files are copied to DefaultData before LazarusPortable is closed)
(ReleaseLog: 6/9/15)
fixed problem with settings
(ReleaseLog: 6/8/15)
path updates correct now
(ReleaseLog: 6/4/15)
Initial release.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
would this be the largest PA or is there another even bigger?
No comment on the app itself, if it needs to be that big so be it.
Wm
Lazarus Portable 1.1 about 930 MB and 1.5 ~ 1.8 GB. I will make it once more.
Hello,
where is the download of Lazarus 1.4.0 Potable?
Greetings
OLLI
Hello,
the download link is not working.
It points to http://workupload.com/file/
Here the file name is missing.
OLLI
When two apps rise from a grave it is best to sit back and watch for a bit
Wm
Hello hemmen,
you did a fantastic work, Lazarus 1.4.0 is working!
Thank you very very much!
If I compile my project I get in the unit LCLProc (a unit provided by Lazarus, none of my units) the following error:
lclproc.pas(30,3) Fatal: Kann Unit win9xwsmanager nicht finden verwendet von LCLProc von Package LCLBase.
The error is in German Language, here it is translated into English Language:
lclproc.pas(30,3) Fatal: Can not find Unit win9xwsmanager used by LCLProc in Package LCLBase.
Is this a problem in my Project settins or a problem with packaging Lazarus (like an invalid Path)?
Thank you for your fantastic work again!
Greetings
OLLI
I think this is always a problem with the path in fpc.cfg. X:\PortableApps\LazarusPortable is expected, but LazarusPortable takes any path it has found.
If LazarusPortable has been started, fpc.cfg must be there:
App\lazarus\fpc\2.6.4\bin\i386-win32\
If LazarusPortable has ended, fpc.cfg must be there:
Data\Settings
Look in LazarusPortable\Data\Settings there is the fpc.cfg. In the orginal place at lazarus\fpc\2.6.4\bin\i386-win32\ there is no fpc.cfg (when lazarus hasn't been started! otherwise there is and it will be automatically deleted when lazarus was finished)
Solution (when lazarus has been ended): I have written a little batch program therefore. makefpc_cfg.bat - updated -
Copy makefpc_cfg.bat to LazarusPortable\App\lazarus\fpc\2.6.4 and rename the existing one (=when lazarus has been started). DoubleClick LazarusPortable\App\lazarus\fpc\2.6.4\makefpc_cfg.bat and the problem is gone (that's the cause for the error which you reported).
Is the path in LazarusPortable (menue: tools->option) correct?
Usually it updates to the correct path if the LazarusDir has been changed. In this case the message "Incorrect configuration directory found" is displayed and the button "Update info" is the correct one.
Now I must rewrite "makefpc_cfg.bat" to take care of both cases. It should work ..
best regards
Diane
@OLLI Thanks for your Thanks for your positive feedback. Much appreciated!
Hello hemmen,
you wrote in your Release log:
(ReleaseLog: 6/8/15)path updates correct now
I had no time to test you batch file yet, so I deleted the Lazarus Portable folder (Development Test 1), downloaded the Development Test 2 and installed it.
When I open my project and compile it, I still get the same error message like before:
German: clproc.pas(30,3) Fatal: Kann Unit win9xwsmanager nicht finden verwendet von LCLProc von Package LCLBase.English: clproc.pas(30,3) Fatal: Can not find Unit win9xwsmanager used by LCLProc in Package LCLBase.
When I start a new project and compiled it I get the following error message:
German: Kann Verzeichnis "C:\Users\diane\" nicht erzeugenEnglisch: Can not create directory "C:\Users\diane\"
This is your user folder (so your name is Diane).
This version of Lazarus is not really portable, because it contains fixed user folders.
But I think that portable apps should contain relative paths to the portable app directory.
Please fix your portable version so that it can be downloaded and used like all other portable apps.
I really love Lazarus and would love to see it as a portable app.
Greetings
OLLI
There were two files which were copied in the App folder after Lazarus have started:
:lol:
App\lazarus\fpc\2.6.4\bin\i386-win32\fpc.cfg and
App\lazarus\EnvironmentOptions.xml
They must be deleleted. I'm uploading a correct version. It's funny they were there in Development Test 1, too.
@OLLI Thank you
Yes, the new files contain the relative path which will be replaced to have the absolute path which is required by lazarus. The files are a part of installation and they should not be there, because they could not be overwritten. But my files were overwritten by them. Now PortableLazarus deletes these files first and helps to keep the new ones.
best regards,
Diane
hemmen,
Thanks for uploading this, however you'll notice that I have already been working on Lazarus Portable for a few months now. As such, there was no need to upload a new build, particularly without checking if there was already one available. If you had, you'd have een I was dealing with failing equipment, but was working on getting the package up ASAP. I've now taken care of my dead HDD, and have uploaded the package above.
@Gord Caswell
I've made this, too. Okay, it's the base for developing a LazarusPortable2ndConfig to use an other fpc version with LazarusPortable. I would have asked you if I want to release LazarusPortable. I want to improve my work and it isn't ready, yet. I'll try to make a more flexible approach to start all versions of lazarus in this way. Lazarus as PortableApp offers more advantages than startlazarus --pcp can do. A backup feature would be nice, too. The release version is a better starting point than svn versions are.
That sounds like an interesting plan. I'd be happy to look at how to adjust the launcher to allow for that. I've got the project up on bitbucket, if you'd like to fork and propose merges, so as to keep it a single project.
I can build what I want from Lazarus 1.1 to 1.7 with it's related fpc version.
please test..
Enjoy.
You mention above that important files are copied back to DefaultData - don't do that. Default Data is to be used for just that - Default Data, required when a user resets the application to a newly installed setup. It should not be copied in/out of in regular use.
a user resets the application to a newly installed setup okay that is difficult because lazarus.exe was certainly build with some extra components. If there are so "many" components installed, I don't want to loose them. - lazarus.exe have to be stored (>200MB) or newly compiled (4 minutes on harddrive, on usb stick longer) okay to install it new on usb stick this will take longer). That's an argument. I will change that. Thank you Gord Caswell.
Any chance to update it to the latest version?
There is already exist Lazarus version 1.8.4 with builtin FPC 3.0.4
https://www.lazarus-ide.org/index.php?page=downloads
It would be great if you update this development, I really appreciate your hard work!
edit
oh and also don't forget to include the cross-x86_64-win64-win32.exe add-on, so that we can build 64-bit apps from the 32-bit ide
https://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2032%20...