scottk/wlan-cloud-lib-poco
1
0
Fork 0
mirror of https://github.com/Telecominfraproject/wlan-cloud-lib-poco.git synced 2025-11-03 03:57:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

updated README

Browse Source
This commit is contained in:
Guenter Obiltschnig
2012-11-18 16:51:07 +01:00
parent bd5d3bca07
commit b9acb9f263
1 changed files with 16 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files

65
README
View File

@@ -16,11 +16,10 @@ All libraries come with a test suite and a number of sample programs.
The basic directory layout is as follows: The basic directory layout is as follows:
build/ the build system for Unix/OpenVMS and additional utility scripts build/ the build system for Unix and additional utility scripts
config/ build configurations for various Unix platforms config/ build configurations for various Unix platforms
rules/ common build rules for all platforms rules/ common build rules for all platforms
scripts/ build and utility scripts scripts/ build and utility scripts
vms/ OpenVMS build system scripts
vxconfig/ VxWorks build configurations vxconfig/ VxWorks build configurations
bin/ all executables (dynamic link libraries on Windows) bin/ all executables (dynamic link libraries on Windows)
@@ -93,14 +92,14 @@ libraries) being installed to build properly:
- Data/MySQL requires the MySQL client. - Data/MySQL requires the MySQL client.
Most Unix/Linux systems already have OpenSSL preinstalled. If your system Most Unix/Linux systems already have OpenSSL preinstalled. If your system
does not have OpenSSL, please get it from http://www.openssl.org or does not have OpenSSL, please get it from <http://www.openssl.org> or
another source. You do not have to build OpenSSL yourself - a binary another source. You do not have to build OpenSSL yourself - a binary
distribution is fine (e.g., apt-get install openssl libssl-dev). distribution is fine (e.g., apt-get install openssl libssl-dev).
The easiest way to install OpenSSL on Windows is to use a binary The easiest way to install OpenSSL on Windows is to use a binary
(prebuild) release, for example the one from Shining Light (prebuild) release, for example the one from Shining Light
Productions that comes with a Windows installer Productions that comes with a Windows installer
(http://www.slproweb.com/products/Win32OpenSSL.html). <http://www.slproweb.com/products/Win32OpenSSL.html>.
Depending on where you have installed the OpenSSL libraries, Depending on where you have installed the OpenSSL libraries,
you might have to edit the build script (buildwin.cmd), or add the you might have to edit the build script (buildwin.cmd), or add the
necessary paths to the INCLUDE and LIB environment variables. necessary paths to the INCLUDE and LIB environment variables.
@@ -122,17 +121,17 @@ accordingly.
BUILDING ON WINDOWS BUILDING ON WINDOWS
=================== ===================
Microsoft Visual Studio 7.1 (2003), 8.0 (2005), 9.0 (2008) or 10.0 (2010) is required to Microsoft Visual Studio 7.1 (2003), 8.0 (2005), 9.0 (2008), 10.0 (2010) or 11.0 (2012)
build the POCO C++ Libraries on Windows platforms. Solution and project files for all is required to build the POCO C++ Libraries on Windows platforms. Solution and project
versions are included. For Visual Studio 2008 and 2010, 64-bit (x64) builds are files for all versions are included. For Visual Studio 2008 and later, 64-bit (x64) builds
supported as well. are supported as well.
You can either build from within Visual Studio (Build->Batch Build->Select All;Rebuild) You can either build from within Visual Studio (Build->Batch Build->Select All;Rebuild)
or from the command line. To build from the command line, start the or from the command line. To build from the command line, start the
Visual Studio .NET 2003 (or 2005/2008/2010) Command Prompt and cd to the directory where you Visual Studio .NET 2003 (or 2005/2008/2010/2012) Command Prompt and cd to the directory
have extracted the POCO C++ Libraries sources. Then, simply start the buildwin.cmd script where you have extracted the POCO C++ Libraries sources. Then, simply start the buildwin.cmd
and pass as argument the version of visual studio (71, 80, 90 or 100). You can customize script and pass as argument the version of visual studio (71, 80, 90, 100 or 110). You can
what is being built by buildwin.cmd by passing appropriate command line arguments to customize what is being built by buildwin.cmd by passing appropriate command line arguments
it. Call buildwin.cmd without arguments to see what is available. to it. Call buildwin.cmd without arguments to see what is available.
To disable certain components (e.g., NetSSL_OpenSSL or Data/MySQL) from the build, To disable certain components (e.g., NetSSL_OpenSSL or Data/MySQL) from the build,
edit the file named "components" and remove the respective lines. edit the file named "components" and remove the respective lines.
@@ -157,7 +156,7 @@ BUILDING FOR WINDOWS CE
Building for Windows CE is supported with Microsoft Visual Studio 2008. Building for Windows CE is supported with Microsoft Visual Studio 2008.
Unless you have the Digi JumpStart Windows CE 6.0 SDK installed, you'll Unless you have the Digi JumpStart Windows CE 6.0 SDK installed, you'll
have to modify the included Visual Studio project and solution files. have to modify the included Visual Studio project and solution files.
Please see the SDK Reference Documentation (http://pocoproject.org/documentation) Please see the SDK Reference Documentation <http://pocoproject.org/documentation>
for instructions. for instructions.
@@ -167,8 +166,7 @@ BUILDING ON UNIX/LINUX/MAC OS X
For building on Unix platforms, the POCO C++ Libraries come with their own For building on Unix platforms, the POCO C++ Libraries come with their own
build system. The build system is based on GNU Make 3.80 (or newer), with the help build system. The build system is based on GNU Make 3.80 (or newer), with the help
from a few shell scripts. If you do not have GNU Make 3.80 (or later) installed on from a few shell scripts. If you do not have GNU Make 3.80 (or later) installed on
your machine, you will need to download it from your machine, you will need to download it from <http://directory.fsf.org/wiki/Make>,
http://directory.fsf.org/devel/build/make.html>,
build and install it prior to building the POCO C++ Libraries. build and install it prior to building the POCO C++ Libraries.
You can check the version of GNU Make installed on your system with You can check the version of GNU Make installed on your system with
@@ -208,7 +206,7 @@ on your system. To do this, use the --omit argument to configure:
To build on Mac OS X 10.3 with GCC 3, do the following: To build on Mac OS X 10.3 with GCC 3, do the following:
(NOTE: This only affects 10.3; for 10.4/10.5 see above) (NOTE: This only affects 10.3; for 10.4 or newer see above)
> ./configure --config=Darwin7 > ./configure --config=Darwin7
> make -s > make -s
@@ -252,37 +250,6 @@ more information. The Reference Documentation can be found online
at <http://pocoproject.org/docs/>. at <http://pocoproject.org/docs/>.
BUILDING ON OPENVMS
===================
OpenVMS is no longer supported in recent versions of POCO, due to both a
lack of interest and a lack of contributors. The following
instructions are here for historical reasons.
The POCO C++ Libraries come with their own build system for OpenVMS, implemented
by a bunch of DCL scripts. The scripts can be found in the build/vms directory.
To build the POCO C++ Libraries on OpenVMS, follow the following steps.
1) Download the .zip distribution of the POCO C++ Libraries
2) Unzip the archive
$ unzip -aa poco-0_91_4.zip
3) Change the directory
$ set def [.poco-0_01_4]
4) Create a lib directory
$ create/dir [.lib]
5) Run the buildvms.com script
$ @buildvms
This will build the debug versions of the libraries. To build the release
versions, use
$ @buildvms -release
MORE INFORMATION MORE INFORMATION
================ ================
@@ -291,4 +258,4 @@ at <http://pocoproject.org>.
-- --
$Id: //poco/1.4/dist/README#4 $ $Id: //poco/1.4/dist/README#5 $