Growl nightly builds

The Growl forums have moved to Google Groups, this forum is read only.
Locked
dakidski
Harmless
Posts: 20
Joined: Thu Mar 17, 2005 11:55 am

Growl nightly builds

Post by dakidski »

Some guy i know keeps talking about these. Where can they be found?
User avatar
Diggory
Growl Team
Posts: 129
Joined: Sat Dec 04, 2004 12:17 pm
Location: London

Post by Diggory »

There aren't any - perhaps he meant building from SVN?
User avatar
The_Tick
Cocoaforge Admin
Posts: 4642
Joined: Thu Dec 02, 2004 6:06 am
Contact:

Post by The_Tick »

Ya, there aren't any nightlies. You can build from svn whenever you want though. I'd prefer that we didn't have nightlies.
User avatar
codeProle
Harmless
Posts: 13
Joined: Sat Apr 30, 2005 11:45 am
Contact:

Building from SVN

Post by codeProle »

On several occasions I have tried to build growl from SVN. Each time I get six warnings and an error.

First I checkout the latest build (2201), then following the steps on the developer page I open the Growl.xcode project and change my build style from "Development" to "Deployment" and build the "Growl" target.

The warnings I'm not too worried about, however the error (which isn't displayed or identified by the IDE) prevents the build from completing. Frustrating.

Is there a revision that does build cleaning that includes the fix that allows growlnotify to work properly from inside shells or cron tasks?

And or, how do I build Growl without getting this mystery error?

TIA
cp
Mac OS X: Because making Unix user-friendly was easier than fixing Windows.

Mac OS X (10.3.9) / Powerbook G4 (867MHz/768MB/40GB)
User avatar
boredzo
Cocoaforge Admin
Posts: 796
Joined: Mon Dec 06, 2004 7:49 am
Contact:

Re: Building from SVN

Post by boredzo »

codeProle wrote:On several occasions I have tried to build growl from SVN. Each time I get six warnings and an error. ... The warnings I'm not too worried about, however the error (which isn't displayed or identified by the IDE) prevents the build from completing. Frustrating.


what are the warnings? and what version of Xcode are you using?
User avatar
codeProle
Harmless
Posts: 13
Joined: Sat Apr 30, 2005 11:45 am
Contact:

Version and warnings

Post by codeProle »

I'm using XCode version 1.1. Mac OS X version 10.3.8.

I get two warnings in GrowlBrushedWindowsController.m on line 27

local declaration of 'identifier' hides instance variable
instance variable 'identifier' accessed in class method

In GrowlBubblesWindowsController.m I get these:
local declaration of 'identifier' hides instance variable
instance variable 'identifier' accessed in class method
#warning this is some temporary code to to stop notifications from spilling off the bottom of the visible screen area

And in GrowlWebKitWindowsController.m I get
#warning this is some temporary code to to stop notifications from spilling off the bottom of the visible screen area


cp
Mac OS X: Because making Unix user-friendly was easier than fixing Windows.

Mac OS X (10.3.9) / Powerbook G4 (867MHz/768MB/40GB)
User avatar
The_Tick
Cocoaforge Admin
Posts: 4642
Joined: Thu Dec 02, 2004 6:06 am
Contact:

Post by The_Tick »

You need to be using xcode 1.5.
User avatar
codeProle
Harmless
Posts: 13
Joined: Sat Apr 30, 2005 11:45 am
Contact:

D'oh

Post by codeProle »

D'oh!
Mac OS X: Because making Unix user-friendly was easier than fixing Windows.

Mac OS X (10.3.9) / Powerbook G4 (867MHz/768MB/40GB)
User avatar
codeProle
Harmless
Posts: 13
Joined: Sat Apr 30, 2005 11:45 am
Contact:

Growl.framework build

Post by codeProle »

Okay... I've got XCode 1.5 installed. I build the Growl taget and while it gets 8 warnings, there are no errors and the build succeeds. Looking in the build folder inside the growl folder I can see the Growl.prefPane. Cool.

Next I build Growl.framework and it succeeds with 3 warnings. However, there is no Growl.framework folder or entry in the build folder.

I'm guessing there's a step I missed on the 'build from Subversion' page, but I've repeated those steps several times with the same results.

Any ideas?
cp
Mac OS X: Because making Unix user-friendly was easier than fixing Windows.

Mac OS X (10.3.9) / Powerbook G4 (867MHz/768MB/40GB)
User avatar
The_Tick
Cocoaforge Admin
Posts: 4642
Joined: Thu Dec 02, 2004 6:06 am
Contact:

Post by The_Tick »

At this point there isn't really a reason to use the framework unless you are going to use it in an application of your own.
User avatar
codeProle
Harmless
Posts: 13
Joined: Sat Apr 30, 2005 11:45 am
Contact:

Post by codeProle »

The_Tick wrote:At this point there isn't really a reason to use the framework unless you are going to use it in an application of your own.


Is the fix for growlnotify not working from cron embedded in the framework somewhere?

I've built several nightlies now and none provide the growlnotify fix talked about in revision 1835. (http://forums.cocoaforge.com/viewtopic.php?t=797)

When I follow the directions for building growl from a SVN checkout I *do not* get the Growl.framework in the build folder after building it.

What gives?
cp
Mac OS X: Because making Unix user-friendly was easier than fixing Windows.

Mac OS X (10.3.9) / Powerbook G4 (867MHz/768MB/40GB)
User avatar
Diggory
Growl Team
Posts: 129
Joined: Sat Dec 04, 2004 12:17 pm
Location: London

Post by Diggory »

did you also re-build and install growlnotify?
User avatar
codeProle
Harmless
Posts: 13
Joined: Sat Apr 30, 2005 11:45 am
Contact:

D'oh!

Post by codeProle »

:oops:

Okay, now it works. By doing a "sudo make install" in the growl/Extras/growlnotify directory, my cron tasks now have growl notification ability.

Just to re-cap for those reading along who don't want to find the beginning of the thread:

1. Download the latest nightly build and build it following the directions on the developer download page.

2. Locate the Extras/growlnotify directory within the growl directory you just downloaded via Subversion, and perform a make install. Viola!

cp
Mac OS X: Because making Unix user-friendly was easier than fixing Windows.

Mac OS X (10.3.9) / Powerbook G4 (867MHz/768MB/40GB)
Locked