#4996 closed update (fixed)
UPDATE: aqua/Growl 0.7.6
Reported by: | jberry@… | Owned by: | mww@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Growl build failure osacompile | Cc: | mww@…, boeyms@…, pipping@…, jberry@…, rhwood@…, markd@… |
Port: |
Description
Patch to update growl to 0.7.2 attached.
Note that I can't get it to build on my system, which I don't have time to work through. Build output is attached. Somewhere deep down in the build process osacompile is complaining that it can't interact with the user...I don't know why.
Attachments (3)
Change History (19)
Changed 19 years ago by jberry@…
Attachment: | growl.diff added |
---|
Changed 19 years ago by jberry@…
Attachment: | growl-build-output.txt added |
---|
Output from failed growl build
comment:1 Changed 19 years ago by jberry@…
There's an open issue at Growl about this, by a guy named "robertshaw":
comment:2 Changed 19 years ago by joe@…
I know this port is sort of in limbo, and I hope I'm not disrupting the usual process by contributing some comments here, but I'd love to see variants for building each of the Extras (e.g. +GrowlSafari, etc.). I think it would be cool to dictate which extras to build and install.
comment:3 Changed 19 years ago by jberry@…
I think I can speak for Markus by saying that I'm sure you're not stepping on anybody's toes if you just dive in and work on this port.
comment:4 Changed 19 years ago by yeled@…
Status: | new → assigned |
---|
i'm almost finished a 0.7.2 port here. if you'd like to share what you have Joe, it would be appreciated.
comment:5 Changed 19 years ago by joe@…
I haven't worked on this any further since I heard of the compile error. My "work" was only in planning and dreaming anyway... It looks like there is another bug open for Growl 0.7.2. Should we consolidate?
comment:6 Changed 18 years ago by markd@…
Type: | defect → enhancement |
---|
comment:7 Changed 18 years ago by kballard (Lily Ballard)
Milestone: | → Available Ports |
---|
Changed 18 years ago by pipping@…
Attachment: | growl.2.diff added |
---|
new patch (for version 0.7.6) - problem persists, though
comment:8 Changed 18 years ago by pipping@…
Milestone: | Available Ports → Port Updates |
---|
comment:9 Changed 18 years ago by pipping@…
Summary: | UPDATE: aqua/Growl 0.7.2 → UPDATE: aqua/Growl 0.7.6 |
---|
comment:10 Changed 17 years ago by boeyms@…
Cc: | mww@… boeyms@… pipping@… jberry@… added |
---|---|
Keywords: | Growl build failure osacompile added |
(Much of this comment is taken from an email that I sent to the Growl mailing list, but I can't find an online archive of it to link to.)
I think that I've found the problem (which, as discoveries so often are, was by accident): it fails to build when attempting to compile the AppleScript in GrowlAction when GrowlHelperApp
is not running. Using a binary installation of Growl, I can make the problem go away if Growl is launched at login, or if "Start Growl" appears in the Growl menu extra and I click on that option before attempting to build from a clean checkout. The problem returns if I click on "Stop Growl" in the Growl menu extra and then attempt to build from a clean checkout.
Line 10 of main.applescript
is "tell application GrowlHelperApp". According to the AppleScript Language Guide for AppleScript Version 1.3.7:
"You can also specify an application on the local computer with only the application's name ( "ApplicationName" ). In this case, AppleScript attempts to find an application of that name among currently running applications. If the application isn't running, AppleScript attempts to locate it in the current directory. If the application isn't in the current directory, AppleScript displays a
directory dialog box asking where the application is located. If the name of the application you select is different from the name specified in the script, the name in the script changes to match the name of the application you select."
I imagine that osacompile
behaves the same way, in which case it seems that it's failing to locate a built GrowlHelperApp
and then failing in its attempt to display a dialog box to find one. A symlink in Extras/GrowlAction
to the build location of GrowlHelperApp
(i.e. build/$(CONFIGURATION)/GrowlHelperApp.app/Contents/MacOS/GrowlHelperApp
) ought to be sufficient to fix the problem, but unfortunately the GrowlHelperApp
target of the XCode project depends on the "Show Notification Action.action
" product of GrowlAction, so either this circularity of dependencies would need to be fixed as well, or GrowlAction would need to be removed from the default build.
The lead developer on Growl, however, informed me that they don't plan on making any further releases in the 0.7.x series, so unless someone gains enough courage to try to learn to patch the XCode files by hand, we will have to wait until the next release to fix this (or take an svn build from trunk, which does not suffer from this problem).
Sorry about the length of this comment.
comment:11 Changed 17 years ago by rhwood@…
Cc: | rhwood@… added |
---|
comment:12 Changed 17 years ago by markd@…
Cc: | markd@… added |
---|
I see Growl has been updated. Can this be closed?
comment:13 Changed 17 years ago by boeyms@…
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:14 Changed 17 years ago by nox@…
Cc: | mww@macports.org, boeyms@macports.org, pipping@macports.org, jberry@macports.org, rhwood@macports.org,markd@macports.org → mww@macports.org, boeyms@macports.org, pipping@macports.org, jberry@macports.org, rhwood@macports.org, markd@macports.org |
---|---|
Priority: | Expected → Normal |
Version: | 1.0 |
comment:15 Changed 16 years ago by jmroot (Joshua Root)
Type: | enhancement → update |
---|
Patch to Portfile