Re: How to make Installer Plugin work?
Re: How to make Installer Plugin work?
- Subject: Re: How to make Installer Plugin work?
- From: Mike Fischer <email@hidden>
- Date: Sun, 19 Mar 2006 19:37:37 +0100
Answering my own post...
Nevermind, I figured it out. The InstallerSections.plist must be in
Contents/Plugins/ of the .pkg not in Contents/.
My Installer Plugin now loads and its UI displays just fine. The
NSLogs I put into my code indicate that the overridden methods of the
pane class are called just fine.
Sorry for the noise.
Mike
Am 19.03.2006 um 18:18 schrieb Mike Fischer:
Hi,
I've been trying to get an Installer Plugin to work, so far without
any luck.
I used Xcode 2.2.1, created a new project from the "Standard Apple
Plug-Ins" -> "Installer Plugin" template, built the project
(without any modifications), created a simple installer package
using Iceberg 1.1.6, placed the plugin .bundle into Contents/
Plugins/ of the .pkg and copied the InstallerSections.plist from
the Xcode project folder into Contents/ of the the .pkg. Then I
launched the .pkg using a double-click.
I also tried with permutations of the folder name "Plugins",
different sort order of the sections in the InstallerSections.plist
and adding some elements in the .nib of the plugin and the a few
additions to the pane class of the plugin. Same result, i.e.
nothing to see at all.
I don't see the additional installer phase in the UI of the
installer. Nothing in any log files (install.log or console.log)
either.
Did I do something wrong? Did I misunderstand something here?
I'm trying this on Mac OS X 10.4.5 Build 8H14 on a dual G5
PowerMac. The Apple Installer is version 2.1.0 (86.1).
I realize Installer Plugins are not yet documented apart from the
header files and that they require Tiger and up. But from the
comments I found on this list, I gather that others have been more
successful in getting an Installer Plugin to at least show up
during the install.
High level goal:
I would like to find out if an Installer Plugin would be a viable
way for entering a license code for a software during the install.
I'm aware of the issues this might cause for command-line installs
in lab settings and alternatives will probably be provided for
them. Unfortunatly the software requires the license code early
during the installation because depending on this code different
things are installed. (Not my idea, I'm just doing the installer.)
My alternatives are: a) calling a separate GUI tool from one of the
installer scripts or b) building my own installer. Neither is very
appealing although I probably need one of these options for Mac OS
X versions before Tiger.
Any hints?
Thanks!
Mike
--
Mike Fischer Softwareentwicklung, EDV-Beratung
Schulung, Vertrieb
Web: <http://homepage.mac.com/mike_fischer/index.html>
Note: I read this list in digest mode!
Send me a private copy for faster responses.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden