-This branch represents an unofficial patched version of the Growl
-1.2.x sources taken from the last available public source tree.
+bitbucket.org/pmetzger/growl is an unofficial patched version of the
+Growl 1.2.x sources taken from the last available public source tree.
-(The tip of this tree is the "fork-1.2" branch, which was branched
-from the "maintenance-1.2" branch. The "default" branch seems to be
-This branch builds cleanly under XCode 4.1. As provided, it constructs
+The branch builds cleanly under XCode 4.1. As provided, it constructs
binaries that run only under Mac OS X 10.7 "Lion", though people
running Snow Leopard are probably better off using the official 1.2.x
None of this work is official, it is not endorsed by the growl.info
folks, it is not guaranteed to work at all.
+(The tip of this tree is the "fork-1.2" branch, which was branched
+from the "maintenance-1.2" branch. The "default" branch seems to be
+Binaries, version numbered "1.2.2f" to distinguish them from 1.2.2,
+are available in "Downloads" on my bitbucket.org page. They were built
+using the "HOW TO BUILD" directions below. The only one of real
+interest is probably the patched HardwareGrowler which doesn't crash
+On my own machines, I am running the growl prefpane itself,
+HardwareGrowler and GrowlTunes, but I wouldn't call that "extensive
+testing", and I haven't properly tested the other Extras -- you have
-0) You need
to have XCode 4.1 installed
+0) You need have XCode 4.1 installed
-2) type "./build.sh" in the top directory. Better yet, do
- "./build.sh >/tmp/log 2>&1" and make sure when it is done that
+2) Run "make" in the "Release" directory. This will build the entire
+ system and generate .dmg files for the release that can be found as
+ It is probably a good idea to do something like
+ "make >/tmp/log 2>&1" and make sure when it is done that
/tmp/log contains no "BUILD FAILED" lines.
-3) A zip file of the growl preferences will be left in
+0) Build output is located in "building" directories that are
+ scattered in the various XCode projects in the tree. The main
+ project builds the Growl prefpane and framework. "Extras" contains
+ the sources and projects for the various plugins like GrowlTunes.
+1) The "./build.sh" script in the top directory may be of some small
+ use, if only for reading.
+ After it runs, a zip file of the growl preferences will be left in
- To install it by hand (yes, this is cheesy)....
- a) Make sure you have no other version of growl (like 1.3 or 1.2.2)
+ To install it by hand for experiments
+ a) Make sure you have no other version of growl installed or running.
b) cd to ~/Library/PreferencePanes and unzip the thing there.
-4) .app files for HardwareGrowler, GrowlTunes, etc, are in
- Extras/HardwareGrowler/build/Release (and the like named
- directories for the other "Extras".) I haven't tested these well AT
- ALL -- HardwareGrowler seems to work, GrowlTunes seems to work, I
- haven't tested the others AT ALL.
-Patches to automate creating a real release welcome -- there is some
-existing release automation there but it doesn't seem to be "press one
-button" automatic, which it could be. (If I end up doing this too
-often I'll do that, or more likely, I'll just wait until someone else
-gets frustrated and does it.)
+2) .app files for HardwareGrowler, GrowlTunes, etc, are in
+ Extras/<extraname>/build/Release for each of the extras.
+[UPDATE: As of Tuesday, October 11th, I have been banned by
+Christopher Forsythe from the growl mailing lists, apparently for
+telling people that I'd forked the code and where to find it. Sadly,
+this does not seem like a promising development.]
I forked the Growl sources largely because Growl 1.3, available only
on the Mac App Store, seemed to fail very badly for most of the people
who installed it (including me), and the growl developers seemed
will eventually become open source again and get straightened out so
that it works for most users, but if it doesn't, a fork of the project
will be able to provide a working Growl to Mac users.
-UPDATE: As of Tuesday, October 11th, I appear to have been banned from
-the growl mailing lists, apparently for telling people that I'd forked
-the code and where to find it.