Closed GoogleCodeExporter closed 9 years ago
There are two solutions:
- Set up a folder with a ReadMe.txt file in it that instructs the person
building GrowlMail to put a release framework and its dSYM in that folder, and
have the GrowlMail Xcode project and Release Makefile targets use the items in
that folder.
- Include the built framework's dSYM with GrowlMail's dSYM.
Original comment by p...@growl.info
on 15 May 2011 at 12:08
Changing GrowlMail over to require a dropped-in framework looks like it'd be a
lot of work. I've just made changes that include copying the built framework's
dSYM alongside GrowlMail's dSYM, and will be committing these changes over the
next few minutes.
Original comment by p...@growl.info
on 16 May 2011 at 2:42
Fixed in [b5d642471d8c].
Original comment by p...@growl.info
on 16 May 2011 at 2:48
Original comment by p...@growl.info
on 16 May 2011 at 2:50
Original comment by chrisf.g...@gmail.com
on 16 May 2011 at 2:52
GrowlMail 1.2.4 is out, closing this issue.
Original comment by chrisf.g...@gmail.com
on 25 May 2011 at 2:22
Original comment by p...@growl.info
on 29 Jul 2011 at 4:57
Original issue reported on code.google.com by
p...@growl.info
on 15 May 2011 at 12:06