fte/quakespasm
2
0
Fork 0
mirror of https://github.com/Shpoike/Quakespasm.git synced 2024-11-10 15:31:39 +00:00
Code Issues Projects Releases Packages Wiki Activity

removed remaining pieces of sparkle references from documents

Browse source 
git-svn-id: http://svn.code.sf.net/p/quakespasm/code/trunk/quakespasm@597 af15c1b1-3010-417e-b628-4374ebc0bcbd
This commit is contained in:
sezero 2012-01-05 10:27:09 +00:00
parent 9594aebb43
commit d5ab11d47e
1 changed files with 1 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
MacOSX/Build Instructions.md
View file

@ -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 <version>.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
Kristian Duske, kristian.duske@gmail.com