September 2008 - Installer-dev

Migration from VISE to PackageMaker
by Gu, Kevin 25 Sep '08

25 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Acke7VJLoKqbuY08QDOmUyMRGQ4IsA== Thread-topic: Migration from VISE to PackageMaker _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

RE: dylib inter-dependencies, install_name_tool and @loader_path
by Lisa Weimer 24 Sep '08

24 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AckeTXHo+YFNw9DHQNmMLTd1jYWWVgAJqSHQ Thread-topic: dylib inter-dependencies, install_name_tool and @loader_path Hi Nicolas, I've just finished remapping a bunch of frameworks and dylibs for my company's applications, so I will take a crack at answering this. It sounds like your dylib was not relocated properly if it loaded the global one first. If you properly relocate things, then the system will always use your copy of whatever was relocated. I don't know what happens if the copy you want to use doesn't exist--that is, I can't confirm that it searches the global system path after trying your path, but based on my linux experience, it wouldn't surprise me if that was the default behaviour. (I think if you want it to search a specific series of paths, you need to set this behaviour in xcode at linking time using -rpath. I don't know much about doing things in xcode at linking time so I can't help you there.) id in install name tool allows you to change the install_name. You can read more about install_name in the ld man page. You can set the install_name in the Xcode linker options, or you can use install_name_tool to change this setting. Install_name (id) is means this: things linked against that library will record that path as the way dyld should locate that library. @loader_path, as far as I understand it means this: at run time dyld replaces @loader_path with the path to the Mach-O binary that loaded it (an executable or another shared library of some sort). Unlike @executable_path which only refers to the main executable. When you changed the ids and references did you use this procedure? Use install name tool 1. change the id of a.framework (no longer is the system copy) 2. change the id of b.framework (no longer is the system copy) 3. in a.framework, change the reference to look for your copy of b.framework (Install_name_tool -change) 4. in your exececutable change the references to look for your copies of a.framework and b.framework. (Install_name_tool -change) You can check all of your work with otool -L, see where and how things are referring to each other. So for your app and libs, the first thing I would do is run otool against them all, and verify that things are referring to the right things, and also verify the places they are looking actually exist. I've read before that install_name_tool only works if the new install_name (id) is no longer than the old one. But I've never run into this limitation yet, lucky me. I don't know if this will help at all, but hopefully it doesn't cause more confusion for you. Other mail lists that might help are xcode development mail lists. Best, Lisa Weimer -----Original Message----- From: installer-dev-bounces+lisaweimer=smarttech.com(a)lists.apple.com [mailto:installer-dev-bounces+lisaweimer=smarttech.com@lists.apple.com] On Behalf Of Nicolas.Castagne(a)imag.fr Sent: Wednesday, September 24, 2008 7:44 AM To: installer-dev(a)lists.apple.com Subject: Re: dylib inter-dependencies, install_name_tool and @loader_path Hi again, Indeed, one of the problems was caused by a dynamically dylib loaded at run time (a plugin). The plugin was searched in a global system scope, instead of being searched inside my distribution. Hence, as far as checked, using @loader_path/**relative_path_to_B** inside a .dylib A to refer to a dependent library B behave as following: 1- if path_of_A/**relative_path_to_B** is existing dylib B is, this version of B is loaded 2- if path_of_A/**relative_path_to_B** is NOT can existing dylib B, then B is searched in the global system path. Is this correct? Anyhow, my first question is still valid: > install_name_tool allows changing the "id" of a dynamic library, with -id. > But What Does "id" Mean ? > And what is the impact of the lib's "id" on loading? > I've browsed the doc and the Net for long, but did not find any clear > info... Thanks, Nicolas > Hi folks, > > I am trying to make my applications distribution for mac OSX.4 and X.5, > but > have a couple of problem with the dynamic loading of libraries. > > > My first question is: > install_name_tool allows changing the "id" of a dynamic library, with -id. > But What Does "id" Mean ? > And what is the impact of the lib's "id" on loading? > I've browsed the doc and the Net for long, but did not find any clear > info... > > > My second question is: > What does @loader_path means exactly ? > I did not find any clear info on this, and basically, the observed > behavior does not match what the doc (apparently) says. > > > > Let's now get into a bit more details. > > > My distribution contains various executables, both bundled apps and > command-line, that rely on various interdependent libraries. The distrib > looks like: > distrib > |_ bin > |_ cmdlineexecutable > |_ application.app > |_ lib > |_ A.framework > |_ B.framework > where both executable depend on A AND B, and where A depends on B. > > > Since the executables are NOT on the same level in the distribution tree, > using @executable_path inside a library to refer to another library is NOT > possible. > > > I guess I have to use @loader_path: the executable would refer to a > libraries using @executable_path, and the libraries would refer to each > others using @loader_path > > > According to the doc: >> Library-relative location. To specify a file path relative to >> the location of the library itself, >> place the @loader_path macro at the beginning of the pathname. > > However, when using @loader_path, and when the framework is installed BOTH > inside my distribution AND in a system-searchable location (eg: > /Library/Framework) then BOTH versions of a library are loaded when > launching the app. > > > I guess that: > - the executable, that depends on frameworks A and B refered by using > @executable_path, loads the executable-relative versions of the frameworks > A and B > - framework A, that depends on framework B referred by using @loader_path, > loads the version of B which is located in /Library/Frameworks > > > Hence, @loader_path would NOT refer to the currently-loaded library > path... And the doc would lie :/ > > > I would appreciate any help on this situation. > > Thanks much for your attention, > best- > Nicolas > > PS: First message on this list. I hope it I picked the correct list. Sorry > if I was wrong :/ > _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/lisaweimer%40smartt ech.com This email sent to lisaweimer(a)smarttech.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

PackageMaker exits with 0, but no installer package is created...help! :)
by OSullivan, Steve 24 Sep '08

24 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AckedAZyr2PifkbAok23q1YE5112FA== Thread-topic: PackageMaker exits with 0, but no installer package is created...help! :) User-agent: Microsoft-Entourage/12.12.0.080729 Howdy All, I am running this on Leopard 10.5.5, using Xcode 3.1. I have made a couple of small changes (I removed the 'exit 0' from the first block in the 'if...fi' block, and I removed an extraneous 'if' that was mentioned earlier I am running this script in the hopes of building my installer package, and placing the output in a specific folder. At this point, when I run the script, my target directory is created yet there is no package file output there. PackageMaker seems to exit with 0, and I see nothing indicating the problem in the verbose output. Can anyone offer some ideas on how I might proceed? Has anyone ever run into a problem like this? Regards, Steve O'Sullivan # --- begin script #!/bin/sh # set -vx VERSION=$1 BUILDVERSION=$2 GETDATE=$(date +%m%d%y) CONSOLETARGET="/Volumes/TestingMac/target/Installers/target_${VERSION}_${GET DATE}/Console.pkg" packagemaker -r /pkg_base_console -o ${CONSOLETARGET} -i com.emc.company -n ${BUILDVERSION} -t company -l /Applications/company/ -g 10.5 -h system -b -v > pm_console_text.txt echo "packagemaker output: "$? if [ $? == 0 ] then echo "pm_console.sh ran." >> /daily_build.txt else echo "pm_console.sh failed." >> /daily_build.txt exit 1 Fi exit 0 # --- end script _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Installer-dev Digest, Vol 49, Issue 16
by OSullivan, Steve 24 Sep '08

24 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AckeZsxPtNhoBwRyakywUKKfzG+Whg== Thread-topic: Installer-dev Digest, Vol 49, Issue 16 User-agent: Microsoft-Entourage/12.12.0.080729 Thanks Ulf, But no, removing the erroneous 'if' did not change the outcome of the running of this script. But seriously, thanks for the input (I hadn't seen that for a couple of (ahem) days....) SteveO On 9/24/08 8:58 AM, "installer-dev-request(a)lists.apple.com" <installer-dev-request(a)lists.apple.com> wrote: > Send Installer-dev mailing list submissions to > installer-dev(a)lists.apple.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.apple.com/mailman/listinfo/installer-dev > or, via email, send a message with subject or body 'help' to > installer-dev-request(a)lists.apple.com > > You can reach the person managing the list at > installer-dev-owner(a)lists.apple.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Installer-dev digest..." > > > Today's Topics: > > 1. Re: Permissions on 10.5.4 & packagemaker 2.1.1 (Bill Royds) > 2. Re: Version control in Installer Packages (Ulf Dunkel) > 3. Re: Version control in Installer Packages (Ulf Dunkel) > 4. dylib inter-dependencies, install_name_tool and @loader_path > (Nicolas.Castagne(a)imag.fr) > 5. Re: dylib inter-dependencies, install_name_tool and > @loader_path (Nicolas.Castagne(a)imag.fr) > 6. PackageMaker exits with 0, but no installer package is > created...help! :) (OSullivan, Steve) > 7. Re: PackageMaker exits with 0, but no installer package is > created...help! :) (Ulf Dunkel) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 23 Sep 2008 15:02:35 -0400 > From: Bill Royds <apple(a)royds.net> > Subject: Re: Permissions on 10.5.4 & packagemaker 2.1.1 > To: Annette Brooks <annette.brooks(a)myob.com> > Cc: "installer-dev(a)lists.apple.com" <installer-dev(a)lists.apple.com> > Message-ID: <3E0B969D-81F7-47E6-AA46-8ACE7C39FBC0(a)royds.net> > Content-Type: text/plain; charset="windows-1252" > > > On 23-Sep-08, at 13:36 , Annette Brooks wrote: > >> I am running on OS 10.5.4. Haven‚t upgraded my Packagemaker to v3 >> because of all of the comments on this forum, so I am still running >> 2.1.1. >> >> When I try to set permissions for files through Edit File >> Permissions on the Contents tab, I used to see all of the owners and >> groups that were available to be set on the file ˆ root, wheel, >> admin, etc. Now I see cryptic information ˆ such as „S-1-5-32-550‰ >> or „ABCDEFAB-CDEF-ABCD-EFAB-CDEF0000005C‰ >> >> Anyone know where these things are coming from and what to do about >> it??? _______________________________________________ > d > If it can't look up account numbers to convert them to names, that is > what it woul look like. > The S-1-5-32-550 format is used for Windows accounts, so if you are > authenticating against Active Directory, that would be the source. > Similarly the second format looks like UID account numbers. > > Have you go a directory server that was unavailable? > > > Bill Royds > > > >

1 0

Re: PackageMaker exits with 0, but no installer package is created...help! :)
by Ulf Dunkel 24 Sep '08

24 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Organization: invers Software & DSD.net User-agent: Thunderbird 2.0.0.17pre (Windows/20080924) Hi Steve. if if [ $? == 0 ] then echo "pm_console.sh ran." >> /daily_build.txt exit 0 else echo "pm_console.sh failed." >> /daily_build.txt exit 1 fi I wonder if the doubled 'if' is right here? HTH, UlfDunkel _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Can anyone offer some ideas on how I might proceed? This email sent to site_archiver(a)lists.apple.com

1 0

PackageMaker exits with 0, but no installer package is created...help! :)
by OSullivan, Steve 24 Sep '08

24 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AckeWm4cF1r5tZ0J6UeaUAS/J3ZgEg== Thread-topic: PackageMaker exits with 0, but no installer package is created...help! :) User-agent: Microsoft-Entourage/12.12.0.080729 Howdy All, I am running this on Leopard 10.5.5, using Xcode 3.1. I am running this script in the hopes of building my installer, and placing the output in a specific folder. At this point, when I run the script, my target directory is created yet there is no package file output there. PackageMaker seems to exit with 0, and I see nothing indicating the problem in the verbose output. Can anyone offer some ideas on how I might proceed? Regards, Steve O'Sullivan # --- begin script #!/bin/sh # set -vx VERSION=$1 BUILDVERSION=$2 GETDATE=$(date +%m%d%y) CONSOLETARGET="/Volumes/TestingMac/target/Installers/target_${VERSION}_${GET DATE}/Console.pkg" packagemaker -r /pkg_base_console -o ${CONSOLETARGET} -i com.emc.company -n ${BUILDVERSION} -t company -l /Applications/company/ -g 10.5 -h system -b -v > pm_console_text.txt echo "packagemaker output: "$? if if [ $? == 0 ] then echo "pm_console.sh ran." >> /daily_build.txt exit 0 else echo "pm_console.sh failed." >> /daily_build.txt exit 1 fi # --- end script _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: dylib inter-dependencies, install_name_tool and @loader_path
by Nicolas.Castagne＠imag.fr 24 Sep '08

24 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Importance: Normal User-agent: SquirrelMail/1.4.9a Hi again, Indeed, one of the problems was caused by a dynamically dylib loaded at run time (a plugin). The plugin was searched in a global system scope, instead of being searched inside my distribution. Hence, as far as checked, using @loader_path/**relative_path_to_B** inside a .dylib A to refer to a dependent library B behave as following: 1- if path_of_A/**relative_path_to_B** is existing dylib B is, this version of B is loaded 2- if path_of_A/**relative_path_to_B** is NOT can existing dylib B, then B is searched in the global system path. Is this correct? Anyhow, my first question is still valid: > install_name_tool allows changing the "id" of a dynamic library, with -id. > But What Does "id" Mean ? > And what is the impact of the lib's "id" on loading? > I've browsed the doc and the Net for long, but did not find any clear > info... Thanks, Nicolas > Hi folks, > > I am trying to make my applications distribution for mac OSX.4 and X.5, > but > have a couple of problem with the dynamic loading of libraries. > > > My first question is: > install_name_tool allows changing the "id" of a dynamic library, with -id. > But What Does "id" Mean ? > And what is the impact of the lib's "id" on loading? > I've browsed the doc and the Net for long, but did not find any clear > info... > > > My second question is: > What does @loader_path means exactly ? > I did not find any clear info on this, and basically, the observed > behavior does not match what the doc (apparently) says. > > > > Let's now get into a bit more details. > > > My distribution contains various executables, both bundled apps and > command-line, that rely on various interdependent libraries. The distrib > looks like: > distrib > |_ bin > |_ cmdlineexecutable > |_ application.app > |_ lib > |_ A.framework > |_ B.framework > where both executable depend on A AND B, and where A depends on B. > > > Since the executables are NOT on the same level in the distribution tree, > using @executable_path inside a library to refer to another library is NOT > possible. > > > I guess I have to use @loader_path: the executable would refer to a > libraries using @executable_path, and the libraries would refer to each > others using @loader_path > > > According to the doc: >> Library-relative location. To specify a file path relative to >> the location of the library itself, >> place the @loader_path macro at the beginning of the pathname. > > However, when using @loader_path, and when the framework is installed BOTH > inside my distribution AND in a system-searchable location (eg: > /Library/Framework) then BOTH versions of a library are loaded when > launching the app. > > > I guess that: > - the executable, that depends on frameworks A and B refered by using > @executable_path, loads the executable-relative versions of the frameworks > A and B > - framework A, that depends on framework B referred by using @loader_path, > loads the version of B which is located in /Library/Frameworks > > > Hence, @loader_path would NOT refer to the currently-loaded library > path... And the doc would lie :/ > > > I would appreciate any help on this situation. > > Thanks much for your attention, > best- > Nicolas > > PS: First message on this list. I hope it I picked the correct list. Sorry > if I was wrong :/ > _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

dylib inter-dependencies, install_name_tool and @loader_path
by Nicolas.Castagne＠imag.fr 24 Sep '08

24 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Importance: Normal User-agent: SquirrelMail/1.4.9a Hi folks, I am trying to make my applications distribution for mac OSX.4 and X.5, but have a couple of problem with the dynamic loading of libraries. My first question is: install_name_tool allows changing the "id" of a dynamic library, with -id. But What Does "id" Mean ? And what is the impact of the lib's "id" on loading? I've browsed the doc and the Net for long, but did not find any clear info... My second question is: What does @loader_path means exactly ? I did not find any clear info on this, and basically, the observed behavior does not match what the doc (apparently) says. Let's now get into a bit more details. My distribution contains various executables, both bundled apps and command-line, that rely on various interdependent libraries. The distrib looks like: distrib |_ bin |_ cmdlineexecutable |_ application.app |_ lib |_ A.framework |_ B.framework where both executable depend on A AND B, and where A depends on B. Since the executables are NOT on the same level in the distribution tree, using @executable_path inside a library to refer to another library is NOT possible. I guess I have to use @loader_path: the executable would refer to a libraries using @executable_path, and the libraries would refer to each others using @loader_path According to the doc: > Library-relative location. To specify a file path relative to > the location of the library itself, > place the @loader_path macro at the beginning of the pathname. However, when using @loader_path, and when the framework is installed BOTH inside my distribution AND in a system-searchable location (eg: /Library/Framework) then BOTH versions of a library are loaded when launching the app. I guess that: - the executable, that depends on frameworks A and B refered by using @executable_path, loads the executable-relative versions of the frameworks A and B - framework A, that depends on framework B referred by using @loader_path, loads the version of B which is located in /Library/Frameworks Hence, @loader_path would NOT refer to the currently-loaded library path... And the doc would lie :/ I would appreciate any help on this situation. Thanks much for your attention, best- Nicolas PS: First message on this list. I hope it I picked the correct list. Sorry if I was wrong :/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Version control in Installer Packages
by Ulf Dunkel 24 Sep '08

24 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Organization: invers Software & DSD.net User-agent: Thunderbird 2.0.0.17pre (Windows/20080922) Talking about "manually change the distribution": Do you refer on the file <myPackage>.mpkg/Contents/distribution.dist? I opened in TextWrangler and found a similar line there in <script>function pm_volume_check() Right? PS: Bug #6242214 filed. Best regards, UlfDunkel _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… In your situation I would suggest you manually change the distribution after creating it through PM. And please file a bug for this. I'll do both of what you suggested. Thank you. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Version control in Installer Packages
by Ulf Dunkel 24 Sep '08

24 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Organization: invers Software & DSD.net User-agent: Thunderbird 2.0.0.17pre (Windows/20080922) Hi Scott. Thank you - I love straight answers. :-) I'll do both of what you suggested. Thank you. Best regards, UlfDunkel _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… I'm sorry to say that I think that this is a bug in PackageMaker. In your situation I would suggest you manually change the distribution after creating it through PM. And please file a bug for this. This email sent to site_archiver(a)lists.apple.com

1 0