The setup program is created by a shell script from the zip files of the
distribution, which are themselves created by another shell script. So, the
creation of the package files is automated. I have considered NSIS, but
since it does not seem to offer more possibilties than Inno, I have not made
the step to NSIS. WIX seems indeed an interesting alternative.
Kees Zeelenberg
----- Original Message -----
From: "Volker Grabsch" <[EMAIL PROTECTED]>
To: <gnuwin32-users@lists.sourceforge.net>
Sent: Sunday, March 12, 2006 3:38 PM
Subject: [GnuWin32-Users] Use NSIS instead of InnoSetup?
Dear GnuWin32 Developers,
I saw that all your packages are packed using InnoSetup. That's
interesting for me, because it seems to be a good alternative
to NSIS. However, is InnoSetup fully scriptable? I.e., do you
produce an instaler-Exe without any manual intervention?
Maybe I'm wrong, but InnoSetup looks to me like a lot of manual
work, and developer generally don't have much time to waste.
NSIS is free software, it's fully scriptable (so you can automate
away any packaging work), it has very good compression algorithms
(LZMA, BZIP2, deflate), unpacks fast and inplace (without any additional
temorary directory) and it adds a very small overhead of about
34kb.
http://nsis.sourceforge.net/
The best of all: NSIS is small and portable. I can run this
in my Debian/Linux, and produce a complete working installer-EXE
without having to boot any Windows system.
It's a simple task for me to write a shell script for you
which creates an NSIS Windows installer from a project's
*-bin.zip and *-dep.zip files.
I just needed to know your special requirements, i.e.
* Where do what files have to be installed to?
(bin/* -> ?? , lib/* -> ??, ...)
* What registry entries have to be set, if any?
* Do libraries (zlib) need another treatment than usual
programs (a2ps)?
* Do any packages need any additional manual work to
function properly?
If you already considered using NSIS and it didn't fit
your requirement, or your packaging process is already
well-orgnized and automated, please apologise my obtrusion.
But if you are interested in my offer, just let me know.
BTW, NSIS and InnoSetup have a common drawback: They don't
support *.msi and probably never will. So I keep an eye
on "WIX", maybe trying to port it to Linux in the future. :-)
This is probably also interesting for the GnuWin32 project
since it allows you to support Win-XP platforms with a
native package/installer format.
Greets,
Volker
--
Volker Grabsch
---<<(())>>---
Administrator
NotJustHosting GbR
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
GnuWin32-Users mailing list
GnuWin32-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
GnuWin32-Users mailing list
GnuWin32-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
