search

brettpoole / growl

Automatically exported from code.google.com/p/growl
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Growl.app 1.3.3 won't build unmodified with XCode 4.3.1 (patch supplied) #466

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I just built Growl.app 1.3.3 from source (for the first time) using XCode 4.3.1 
(clone hg repository from here, update to "Growl.app 1.3.3" tag, open 
Growl.xcproj, build).

1. XCode refuses to compile files that don't end with a newline. I had to add 
one to three files.

2. Core/Source/GrowlMenu.h declares OpenGrowlPreferences: and StartStopGrowl: 
as returning void, but the implementation returns IBAction. The patch changes 
the .h to match the implementation.

I only built Growl.app. It's possible that other files will need similar 
changes in order to build the remaining targets in the project.

Original issue reported on code.google.com by a...@liturgiaetmusica.com on 14 Mar 2012 at 8:41

Attachments:

GoogleCodeExporter commented 8 years ago 
Besides these errors, there are also 29 warnings, which I didn't fix. Each of 
the 14 localized versions of GrowlPref.xib generates two "Deprecated: Data 
binding on OS versions 10.6 and later". The apostrophe in Nano's 
GrowlPluginDescription generates the 29th.

Original comment by a...@liturgiaetmusica.com on 14 Mar 2012 at 8:48

GoogleCodeExporter commented 8 years ago 
1.3.3 is the last 1.3.x version. 1.4.x will build fine with Xcode 4.3.1. :)

Original comment by ch...@growl.info on 14 Mar 2012 at 6:23

GoogleCodeExporter commented 8 years ago 
Is there an ETA for 1.4.x?  I'm merely curious; I'm having issues as well 
trying to build 1.3.3 with Xcode 4.3.2.  It just hangs while "Building 
Growl.app: SMS" and won't respond to efforts to stop the build cleanly.  I have 
to force quit Xcode.  I can be patient, I'm just wondering if I should check 
back next week, or in two months, or...?  Thanks.

Original comment by drukepple@gmail.com on 22 Apr 2012 at 1:01

GoogleCodeExporter commented 8 years ago 
We're looking at longer than we expected. We were in final beta, and then found 
an issue that's going to take some time to resolve. I'd suggest checking back 
when we release 1.4, we no longer have an ETA.

Original comment by ch...@growl.info on 22 Apr 2012 at 4:58