• Home
  • History
  • Annotate
  • only in this directory
NameDateSize

..27-May-2015211

bin/H06-Aug-201410

client.crtH A D04-Feb-2013641

client.pemH A D04-Feb-20131.8 KiB

NMakefileH A D10-Jul-2014372

openssl-0.9.8za.tar.gzH A D10-Jul-20143.6 MiB

openssl.xcodeproj/H06-Aug-20143

OpenSSL098.plistH A D10-Jul-2014992

patches/H06-Aug-201419

pkgconfigs/H06-Aug-20145

README.rtfH A D10-Jul-20143.3 KiB

server.pemH A D04-Feb-20131.7 KiB

signed.pemH A D04-Feb-20131.5 KiB

src/H06-Aug-201452

Unit Tests-Info.plistH A D10-Jul-2014682

unit_tests.hH A D04-Feb-2013367

unit_tests.mH A D04-Feb-20135.6 KiB

win32/H06-Aug-20143

README.rtf

1{\rtf1\ansi\ansicpg1252\cocoartf1265\cocoasubrtf210
2{\fonttbl\f0\fswiss\fcharset0 Helvetica;\f1\fnil\fcharset0 Monaco;}
3{\colortbl;\red255\green255\blue255;\red255\green0\blue0;}
4\margl1440\margr1440\vieww19820\viewh22160\viewkind0
5\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\li1441\fi-1442\ri-5038\pardirnatural
6
7\f0\fs24 \cf0 All local changes 
8\b \cf2 MUST
9\b0 \cf0  be present as patch files in ./patches. If you make local changes, you can generate a patch file by running:\
10\
11\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\li1441\fi-1442\ri-5038\pardirnatural
12
13\f1\fs20 \cf0 \CocoaLigature0    ./bin/generate-patch.sh ./patches/RADARNUM-SOME_DESCRIPTIVE_NAME.patch\
14\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\li1441\fi-1442\ri-5038\pardirnatural
15
16\f0\fs24 \cf0 \CocoaLigature1 \
17If you would like to update to a newer version of OpenSSL:\
18\
19	1)	Delete the existing source tarball and the existing "src" directory`\
20	2)	Download the new source tarball and save it into the current directory\
21	3)	Extract source and re-apply all local patches:\
22                            
23\f1\fs20 \CocoaLigature0 ./bin/extract-source.sh .\
24
25\f0\fs24 \CocoaLigature1 	4)	Add any new source files and remove any obsolete source files from the Xcode project. Determine whether there are new headers that should be installed. Determine whether there are any new test targets that should be added.\
26	5)	Some patches may not apply cleanly. In that case, you will have to determine whether the patch is still relevant, and if so, you will have to manually re-create the patch. You can do this by deleting the patch file from the patches directory, manually modifying the relevant source files, then running generate-patch.sh as mentioned above.\
27	6)	
28\b \cf2 IMPORTANT
29\b0 \cf0 : After making sure the project compiles, carefully look at any changes to the installed headers. OpenSSL occasionally makes binary-incompatible changes in minor releases, which can cause existing code to fail in unexpected ways.\
30	7)	
31\b \cf2 IMPORTANT
32\b0 \cf0 : Make sure that the project builds on both OSX and Windows. On OSX, test with buildit. On Windows, if you have the right version of Visual Studio (whichever version B&I is currently using) and ActiveState Perl (you need this for the OpenSSL build system), you should be able to start a Visual Studio command prompt, cd to the root of the source directory, and run "
33\f1\fs20 \CocoaLigature0 nmake -f NMakefile install
34\f0\fs24 \CocoaLigature1 ". You can also test with builditwin:\
35                            
36\f1\fs20 \CocoaLigature0 perl \\\\xs-smb.apple.com\\release\\wbs\\bin\\builditwin .
37\f0\fs24 \CocoaLigature1 \
38	8)	
39\b \cf2 IMPORTANT
40\b0 \cf0 : Run all unit tests. On OSX, you can run:\
41                            
42\f1\fs20 \CocoaLigature0 xcodebuild -target test ARCHS="i386 x86_64"
43\f0\fs24 \CocoaLigature1 \
44		and on Windows you can run:\
45                            
46\f1\fs20 \CocoaLigature0 nmake -f NMakefile install TEST=test
47\f0\fs24 \CocoaLigature1 \
48	9)	Make sure to update OpenSSL098.plist to indicate the new source version. Update OpenSourceModifications to describe any newly created patches, or to remove mention of patches that are no longer relevant.\
49}