From fb02af5a08c2766929af8cbda3243839b068897a Mon Sep 17 00:00:00 2001 From: Ozkan Sezer Date: Thu, 5 Jan 2012 10:27:09 +0000 Subject: [PATCH] removed remaining pieces of sparkle references from documents git-svn-id: svn://svn.code.sf.net/p/quakespasm/code/trunk/quakespasm@597 af15c1b1-3010-417e-b628-4374ebc0bcbd --- MacOSX/Build Instructions.md | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/MacOSX/Build Instructions.md b/MacOSX/Build Instructions.md index 418d8d07..556511ab 100644 --- a/MacOSX/Build Instructions.md +++ b/MacOSX/Build Instructions.md @@ -51,18 +51,6 @@ This should be it. The guides in the link collection at the end of this document ## Building QuakeSpasm Now you can build QuakeSpasm. Simply open the project file using XCode 4.2 and make sure that "QuakeSpasm > My Mac 64-bit" is selected as the scheme in the toolbar. Select "Product > Run" from the menu to run and debug QuakeSpasm. This will not produce a universal binary however. To produce a universal binary for Intel 64bit, Intel 32bit and PowerPC 32bit, you need to select "Product > Archive" from the menu. This will create an application archive that contains the universal binary. -# Releasing QuakeSpasm -QuakeSpasm for Mac uses the Sparkle framework for automatic updates. This means you have to provide an appcast and the zipped binary at the following location: - -http://quakespasm.sourceforge.net/sparkle/appcast.xml -http://quakespasm.sourceforge.net/sparkle/QuakeSpasm .zip - -You may also want to update the release notes at - -http://quakespasm.sourceforge.net/sparkle/rnotes.html - -For security reasons, Sparkle requires updates to be signed. All this is automated using a script. - # Useful Links - XCode 3.2.6: http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/wa/getSoftware?bundleID=20792 @@ -77,4 +65,4 @@ http://stackoverflow.com/questions/5333490/how-can-we-restore-ppc-ppc64-as-well- https://github.com/thinkyhead/Legacy-XCode-Scripts # Author -Kristian Duske, kristian.duske@gmail.com \ No newline at end of file +Kristian Duske, kristian.duske@gmail.com