From: Ian S. <di...@us...> - 2014-11-15 20:38:01
|
Update of /cvsroot/ijbswa/OSXPackageBuilder In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv372 Modified Files: OS X Package Builder HOWTO.txt Log Message: Clarified pre-requisites with respect to where the privoxy software should be checked out Index: OS X Package Builder HOWTO.txt =================================================================== RCS file: /cvsroot/ijbswa/OSXPackageBuilder/OS X Package Builder HOWTO.txt,v retrieving revision 1.10 retrieving revision 1.11 diff -C2 -d -r1.10 -r1.11 *** OS X Package Builder HOWTO.txt 8 Mar 2013 15:47:14 -0000 1.10 --- OS X Package Builder HOWTO.txt 15 Nov 2014 20:37:59 -0000 1.11 *************** *** 6,10 **** ASSUMPTIONS ! 1. That the Privoxy CVS project is available in a folder parallel to the one containing this file. If building for release it should have been exported from Sourceforge to a folder named 'dist', pinned at whichever release you intend to build (as per the instructions in the developer manual), you might have simply checked out the head of the CVS project to a folder named 'current'. If you are using a folder name other than these two you will be prompted to enter it. 2. That you have Xcode installed, including the SDKs for each OS X version you intend your package(s) to support. 3. That your build machine runs Snow Leopard (OS X 10.6). It will likely work equally well on Leopard or Lion (or later), but PackageMaker is substantially different in Tiger and earlier versions of OS X (even the project file format is different). --- 6,13 ---- ASSUMPTIONS ! 1. That the Privoxy CVS project is available in a folder parallel to the one containing this file. ! - If building for release it MUST have been exported from Sourceforge to a folder named 'dist', pinned at whichever release you intend to build (as per the instructions in the Privoxy developer manual) ! - If doing a general test build, you might have simply checked out the head of the CVS project to a folder named 'current'. ! - If you are using a folder name other than these two (or else both exist) you will be prompted to enter the source folder you wish to use when running the scripts detailed below. 2. That you have Xcode installed, including the SDKs for each OS X version you intend your package(s) to support. 3. That your build machine runs Snow Leopard (OS X 10.6). It will likely work equally well on Leopard or Lion (or later), but PackageMaker is substantially different in Tiger and earlier versions of OS X (even the project file format is different). |