odd PackageMaker cli behavior
odd PackageMaker cli behavior
- Subject: odd PackageMaker cli behavior
- From: Karl Schramm <email@hidden>
- Date: Thu, 15 Dec 2005 15:47:09 -0800
Hi all,
I'm trying to automate the build of our installer using
PackageMaker's command line interface and have run into an odd
behavior. When building a package from the command line using
a .pmproj file, PackageMaker fails to build if the "Root" directory
is set to a relative path inside the project although the
PackageMaker command is executed from the directory containing
the .pmproj project. The following is an example of the error:
prompt$ /Developer/Applications/Utilities/PackageMaker.app/Contents/
MacOS/PackageMaker -build -proj "./myPackage.pmproj" -p "./
myPackage.pkg" -v
The package could not be created because of the following errors:
No root specified for archive.
However, if I set the "Root" directory to an absolute path using the
PackageMaker GUI I can build the project from the command line just
fine.
Does anyone have an idea for a work around? I could of course make a
script that builds the packages without a .pmproj project file,
however, our package is in a state of flux so I would really like to
preserve the ability to alter the installer with a GUI.
Thanks!
Karl Schramm
_______________________________________________
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