Changes between Version 3 and Version 4 of Packages/OpenSSL

Timestamp:

12/11/14 02:55:28 (9 years ago)

Author:

Chris Johns

Comment:

--

Packages/OpenSSL

@@ -20 +20 @@
 This version was built with the following instructions with a 4.6.1 [wiki:Developer/Multilib Multilib RTEMS] for the M68K target.
 
-I have built applications with the library on RTEMS and they work and interoperate with Linux software. The [wiki:GoAhead GoAhead] web server also builds with the OpenSSL library. Watch the initialisation of the OpenSLL library when you have the [wiki:GoAhead GoAhead] web server running. Starting a SSL web server will result in the OpenSSL library being initialised. You need to arrange initialisation in one place.
+I have built applications with the library on RTEMS and they work and interoperate with Linux software. The !GoAhead web server also builds with the OpenSSL library. Watch the initialisation of the OpenSLL library when you have the !GoAhead web server running. Starting a SSL web server will result in the OpenSSL library being initialised. You need to arrange initialisation in one place.
 
-The applications tested do not use <i>select</i>, rather threads are used with blocking sockets. This made the code simpler as <i>select</i> requires you handle the need for the SSL code wanting more data. You can find details about this in the OpenSSL API.
+The applications tested do not use ''select'', rather threads are used with blocking sockets. This made the code simpler as ''select'' requires you handle the need for the SSL code wanting more data. You can find details about this in the OpenSSL API.
 
 Change to a scratch work space on your host development machine and untar the source code:
@@ -142 +142 @@
 }}}
 
-OpenSSL installs to paths that are typically used when building for a native library rather than a cross-compiler multilib target. For the RTEMS M68K multilib target with the <tt>-m5200</tt> compiler option the include and library paths are:
+OpenSSL installs to paths that are typically used when building for a native library rather than a cross-compiler multilib target. For the RTEMS M68K multilib target with the `-m5200` compiler option the include and library paths are:
     [[BR]]
     /opt/rtems/m68k-rtems/include[[BR]]
@@ -155 +155 @@
 A possible work around is to use the ''INSTALL''PREFIX'' argument to ''make_ to install into a scratch location and then to move the header files and libraries into the expected RTEMS locations.
 
-It is recommended the header files are placed in <tt>$prefix/m68k-rtems/include</tt> so the following autoconf test can be used to detect OpenSSL has been installed:
+It is recommended the header files are placed in `$prefix/m68k-rtems/include` so the following autoconf test can be used to detect OpenSSL has been installed: