From: "Peter 'Luna' Runestig" <peter@runestig.com>
Subject: Patch to create a Windows Installer MSI package
Date: Tue, 23 Sep 2003 19:13:33 +0200 [thread overview]
Message-ID: <3F707F3D.70104@runestig.com> (raw)
Hi all!
Last year, I put together a kind of (somewhat crude) toolkit to create
Windows Installer MSI installation packages from plain C code. A Windows
Installer MSI installation package is a database with installation
instructions, mostly used together with a set of files to be installed.
It's a very common software distribution format on the Windows platform.
The aim with the toolkit, is to make it possible to get a installation
ready MSI package as a result of the normal build process of the
software code. I've used the toolkit to make MSI installations for
Emacs, Mozilla, OpenSSL and Perl.
If anyone wants to try it out on Emacs, here is a link to the patch
(against CVS as of 20030920):
ftp://ftp.runestig.com/pub/emacs/emacs-20030920-msi-20030923.patch.zip
http://ftp.runestig.com/pub/emacs/emacs-20030920-msi-20030923.patch.zip
Just apply the patch, and
cd nt
configure
nmake bootstrap
nmake msi INSTALL_DIR=<some temp dir>
Only tested with MS VC++ and Platform SDK.
An already-made MSI installation is available here:
ftp://ftp.runestig.com/pub/emacs/Emacs-21.3.50-20030920.msi
http://ftp.runestig.com/pub/emacs/Emacs-21.3.50-20030920.msi
A MSI package can be made in many different ways. To change the way the
MSI is put together, you must change the nt/msi/makemsi.c file. If you
have a fairly good knowledge if the MSI internals, things should be
rather straightforward.
Cheers,
- Peter
--
Peter 'Luna' Runestig (fd. Altberg), Sweden <peter@runestig.com>
PGP Key ID: 0xD07BBE13
Fingerprint: 7B5C 1F48 2997 C061 DE4B 42EA CB99 A35C D07B BE13
AOL Instant Messenger Screen name: PRunestig
Yahoo! Messenger profile name: altberg
reply other threads:[~2003-09-23 17:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F707F3D.70104@runestig.com \
--to=peter@runestig.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).