This is simplistic, but should do the job for an application that has only
one exe file and depends on gnustep-base.
Requires InnoSetup + Preprocessor. (Download at http://www.innosetup.com)
To compile installer as part of make add this command to Makefile:
iscc myniftysetup.iss
--- cut here : myniftysetup.iss ---
[Setup]
AppName=My Nifty App
AppVerName=My Nifty App 1.0
AppPublisher=The Nifty Company, Inc.
AppPublisherURL=http://www.example.com
AppSupportURL=http://www.example.com
AppUpdatesURL=http://www.example.com
DefaultDirName={pf}\NiftyComp\NiftyApp
DefaultGroupName=My Nifty App
AppCopyright=Copyright © 2005 The Nifty Company, Inc.
[Tasks]
Name: desktopicon; Description: Create a &desktop icon; GroupDescription:
Additional icons:
Name: quicklaunchicon; Description: Create a &Quick Launch icon;
GroupDescription: Additional icons:; Flags: unchecked
[Files]
; My Nifty Stuff
Source: shared_obj\niftyapp.exe; DestDir: {app}; Flags: ignoreversion
; GNUSTEP stuff
Source: {#=GetEnv("GNUSTEP_ROOT")}\System\Tools\gnustep-base.dll; DestDir:
{app}; Flags: ignoreversion
Source: {#=GetEnv("GNUSTEP_ROOT")}\System\Tools\libxml2-2.dll; DestDir:
{app}; Flags: ignoreversion
Source: {#=GetEnv("GNUSTEP_ROOT")}\System\Tools\objc.dll; DestDir: {app};
Flags: ignoreversion
[Icons]
Name: {group}\My Nifty App; Filename: {app}\niftyapp.exe;
Name: {commondesktop}\My Nifty App; Filename: {app}\niftyapp.exe; Tasks:
desktopicon
Name: {commonappdata}\Microsoft\Internet Explorer\Quick Launch\My Nifty App;
Filename: {app}\niftyapp.exe; Tasks: quicklaunchicon
[Run]
Filename: {app}\niftyapp.exe; Description: Launch My Nifty App; Flags:
nowait postinstall skipifsilent
----- Original Message -----
From: "Nicola Pero" <[EMAIL PROTECTED]>
To: "Jeremy Bettis" <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sent: Wednesday, October 26, 2005 10:19 AM
Subject: Re: gnustep-make roadmap
> * better support for Windows, including framework support for Windows
> (patches pending from Jeremy, my fault for not having found the time to
> study and apply them yet) ... and potentially some sort of
> auto-packaging
> of Windows applications if I ever get the time to study that matter
> [this second is unlikely]
You speak of auto-packaging for windows applications. Windows installers
are so easy to create with InnoSetup, that it might not be worth doing
that.
How about I send you a sample innosetup file that could get put into some
FAQ somewhere on the gnustep.org web site and we call it good.
Excellent - thanks! :-)
I'm totally ignorant of Windows installers, just thought it would be an
area worth exploring.
Some sort of documentation about how to set up Windows installers for
GNUstep applications using a good Windows tool would definitely be great!
We can stick that somewhere in gnustep-make's documentation.
Thanks
_______________________________________________
Gnustep-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnustep-dev
_______________________________________________
Gnustep-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnustep-dev
