Discussion:
[Lazarus] How to deploy a Lazarus app for Windows?
Giuliano Colla via Lazarus
2017-04-27 22:46:05 UTC
Permalink
Hi all,

I have no experience at all on deploying Lazarus app for Windows,
because up to now I have always addressed to Linux platform. The few
Windows

Now I need to deploy an application for Windows, which requires not only
the executable, but also some auxiliary files. It would be nice to put
everything in a subfolder of the Programs folder, and maybe to touch
also something in the Window registry.

I have no idea of where to start from, in order to create a setup.exe
which will take advantage of the Windows installer.

Can someone point me in the right direction?

Thanks in advance,

Giuliano


--
Ondrej Pokorny via Lazarus
2017-04-27 22:52:55 UTC
Permalink
Post by Giuliano Colla via Lazarus
I have no idea of where to start from, in order to create a setup.exe
which will take advantage of the Windows installer.
Try InnoSetup. AFAIK Lazarus IDE setup is built with it as well.

Ondrej
--
Leonardo M. Ramé via Lazarus
2017-04-27 22:55:56 UTC
Permalink
Post by Giuliano Colla via Lazarus
Hi all,
I have no experience at all on deploying Lazarus app for Windows,
because up to now I have always addressed to Linux platform. The few
Windows
Now I need to deploy an application for Windows, which requires not
only the executable, but also some auxiliary files. It would be nice
to put everything in a subfolder of the Programs folder, and maybe to
touch also something in the Window registry.
I have no idea of where to start from, in order to create a setup.exe
which will take advantage of the Windows installer.
Can someone point me in the right direction?
Thanks in advance,
Giuliano
I remember using these:

http://nsis.sourceforge.net/Main_Page
http://www.jrsoftware.org/isinfo.php

Regards,
--
Leonardo M. Ramé
Medical IT - Griensu S.A.
Av. Colón 636 - Piso 8 Of. A
X5000EPT -- Córdoba
Tel.: +54(351)4246924 +54(351)4247788 +54(351)4247979 int. 19
Cel.: +54 9 (011) 40871877
--
Giuliano Colla via Lazarus
2017-04-27 23:04:32 UTC
Permalink
Post by Leonardo M. Ramé via Lazarus
http://nsis.sourceforge.net/Main_Page
http://www.jrsoftware.org/isinfo.php
Many thanks to you and to Ondrej.

Giuliano

--
LacaK via Lazarus
2017-04-28 05:11:53 UTC
Permalink
Post by Leonardo M. Ramé via Lazarus
http://nsis.sourceforge.net/Main_Page
http://www.jrsoftware.org/isinfo.php
If you need installer in Microsoft Installation Package format (*.msi)
then you can look at WiX toolset: http://wixtoolset.org and WixEdit:
http://wixedit.sourceforge.net/
-Laco.

--
Giuliano Colla via Lazarus
2017-04-28 16:22:54 UTC
Permalink
Post by LacaK via Lazarus
If you need installer in Microsoft Installation Package format (*.msi)
http://wixedit.sourceforge.net/
-Laco.
Thanks again to everybody. I'll investigate what is more suitable for my
case.

Giuliano


--
Tony Whyman via Lazarus
2017-04-29 08:00:14 UTC
Permalink
+1

IMHO, WIX is the best way to create Windows installer packages. It has
the great advantage of using XML scripts to define the installation
package. This allows you to put them under proper change control and
makes it easy to copy and edit the script for each new application
rather than start from scratch. The WIX toolset also runs under wine and
with a FPC cross-compiler, it is possible to build both a Windows
executable and the installer package under Linux. I have some
applications that I deploy under both Windows and Linux and all the
builds are performed from a single bash script under Linux. You can also
use 7-zip to create a self-installer package from the .msi.
Post by LacaK via Lazarus
Post by Leonardo M. Ramé via Lazarus
http://nsis.sourceforge.net/Main_Page
http://www.jrsoftware.org/isinfo.php
If you need installer in Microsoft Installation Package format (*.msi)
http://wixedit.sourceforge.net/
-Laco.
--
Henry Vermaak via Lazarus
2017-05-02 14:30:15 UTC
Permalink
+1
IMHO, WIX is the best way to create Windows installer packages. It has the
great advantage of using XML scripts to define the installation package.
This allows you to put them under proper change control and makes it easy to
copy and edit the script for each new application rather than start from
scratch. The WIX toolset also runs under wine and with a FPC cross-compiler,
it is possible to build both a Windows executable and the installer package
under Linux. I have some applications that I deploy under both Windows and
Linux and all the builds are performed from a single bash script under
Linux. You can also use 7-zip to create a self-installer package from the
.msi.
WiX also makes installing drivers painless. It fits nicely into the
Makefile paradigm, so plays well with the rest of our build system, too.

Henry
--

hfiandor via Lazarus
2017-04-27 23:55:30 UTC
Permalink
Dear Giuliano:

When I finisf the design phase, I copy the executable and the auxiliary files in other folder: "executable".

Then I compress in a winrar, and in a self-extracting winrar. When deploy, I instruct the user to create/open the new folder "executable", copy the self-extracting and execute.

Yours
Ing. Héctor Fiandor Rosario

--
coppolastudio via Lazarus
2017-04-28 17:51:05 UTC
Permalink
--
Gastón Dall' Oglio via Lazarus
2017-04-28 18:13:06 UTC
Permalink
Hello all.

I to use InnoSetup with Inno Script Studio
https://www.kymoto.org/products/inno-script-studio/screenshots

Best.

2017-04-28 14:51 GMT-03:00 coppolastudio via Lazarus <
innosetup has scrips in Pascal that allows some special features
Inviato tramite il client di Posta WPS
Post by LacaK via Lazarus
If you need installer in Microsoft Installation Package format (*.msi)
http://wixedit.sourceforge.net/
-Laco.
Thanks again to everybody. I'll investigate what is more suitable for my
case.
Giuliano
--
_______________________________________________
Lazarus mailing list
http://lists.lazarus-ide.org/listinfo/lazarus
--
_______________________________________________
Lazarus mailing list
http://lists.lazarus-ide.org/listinfo/lazarus
Loading...