Go to file
Aleksandar Fabijanic b90316f949 add test for #4108
2023-08-15 18:29:59 +02:00
.github/workflows Solaris.build fix #3843 and #3643 (#3939) 2023-03-18 01:28:47 -05:00
.vscode 3808 icmp statistics (#3982) 2023-03-22 09:11:13 -05:00
ActiveRecord recreated project files 2023-06-12 17:42:57 +02:00
ApacheConnector Remove trailing whitespace (#3668) 2022-07-07 04:18:20 -05:00
build switching to 64 bit arch for simulator as well (#3009) 2023-06-10 18:13:01 -05:00
ci Fix/tsan (#3617) 2022-06-01 23:47:26 -05:00
cmake Fix build for QNX 2023-02-14 14:27:31 +09:00
contrib Moved contributed CMake modules to "cmake" folder 2012-12-16 00:40:40 -02:00
CppParser base class lookup 2023-07-11 08:54:34 +02:00
CppUnit fix(CppUint) : RepeatedTest compile error (#3759) 2022-08-18 11:37:35 -05:00
Crypto fix haveLegacyProvider for OpenSSL < 3 2023-07-11 07:00:35 +02:00
Data add test for #4108 2023-08-15 18:29:59 +02:00
doc fix(devel): add missing 1.11 releases commits (#3976) 2023-03-18 01:29:14 -05:00
Encodings Remove trailing whitespace (#3668) 2022-07-07 04:18:20 -05:00
Foundation Fix typos in #4086 and #4087. 2023-07-18 07:30:29 +00:00
JSON Fix typo in example (#3894) 2023-01-24 00:41:40 -06:00
JWT chore(ProGen): MSVC does not properly recognize std version #3665 2022-07-06 11:39:47 +02:00
MongoDB Mongodb op msg database commands fix (#4004) 2023-05-05 09:27:42 -05:00
Net chore(Net) : correct spelling, remove some unused codes fix(SocketProactor) : missing adding sock to read pollset fix(DialogServer) : _lastCommands data race (#3821) 2023-07-11 08:00:17 -05:00
NetSSL_OpenSSL fix(SecureSocketImpl.cpp): Shutdown TLS1.3 connection #2776 2023-07-11 14:54:44 +02:00
NetSSL_Win Remove trailing whitespace (#3668) 2022-07-07 04:18:20 -05:00
packaging Remove trailing whitespace (#3668) 2022-07-07 04:18:20 -05:00
PageCompiler #4071: PageCompiler: add referrerPolicy to page directive 2023-07-10 21:27:24 +02:00
patches/AIX new trunk (base for 1.5) 2012-04-23 01:14:34 +00:00
PDF Remove trailing whitespace (#3668) 2022-07-07 04:18:20 -05:00
PocoDoc Remove trailing whitespace (#3668) 2022-07-07 04:18:20 -05:00
ProGen Remove trailing whitespace (#3668) 2022-07-07 04:18:20 -05:00
Prometheus chore(ProGen): MSVC does not properly recognize std version #3665 2022-07-06 11:39:47 +02:00
Redis Remove trailing whitespace (#3668) 2022-07-07 04:18:20 -05:00
release #3700: Release script must include build_vs170.cmd 2022-07-20 12:26:26 +02:00
SevenZip Remove trailing whitespace (#3668) 2022-07-07 04:18:20 -05:00
Util #3876, also for SystemConfiguration 2023-06-06 13:12:35 +02:00
XML #3849: Upgrade bundled libexpat to 2.5.0 [fixes CVE] 2022-10-31 13:26:08 +01:00
Zip Remove trailing whitespace (#3668) 2022-07-07 04:18:20 -05:00
.gitattributes more line ending fixes 2012-11-11 11:20:31 +01:00
.gitignore Always set thread names on POSIX platforms (#3384) 2022-07-07 04:08:47 -05:00
.gitmodules remove openssl submodule 2020-01-12 09:01:35 +01:00
build_cmake.cmd Cleanup cmake build system to use transitive dependency management from cmake (#2321) 2018-06-03 11:17:50 -05:00
build_cmake.sh Cleanup cmake build system to use transitive dependency management from cmake (#2321) 2018-06-03 11:17:50 -05:00
build_vs140.cmd Use defaulted 'msbuild' tool 2018-06-01 13:55:02 +02:00
build_vs150.cmd Use defaulted 'msbuild' tool 2018-06-01 13:55:02 +02:00
build_vs160.cmd add build_vs160.cmd 2020-01-12 10:03:01 +01:00
build_vs170.cmd #3405 #3482 #3485 2022-05-24 18:35:58 -05:00
buildwin.cmd fix(build): fix build with openssl 3.1.0 on vs2022 (#3969) 2023-03-17 17:45:56 -05:00
buildwin.ps1 fix(build): fix build with openssl 3.1.0 on vs2022 (#3969) 2023-03-17 17:45:56 -05:00
CHANGELOG fix(devel): add missing 1.11 releases commits (#3976) 2023-03-18 01:29:14 -05:00
CMakeLists.txt Complimentary to #3918 (std::*mutex wrapper) (#3954) 2023-05-05 09:49:06 -05:00
CODE_OF_CONDUCT.md add CODE_OF_CONDUCT.md 2018-02-09 09:19:46 +01:00
components add Prometheus library 2022-05-17 08:18:54 +02:00
configure Add --ldflags configure option (#3545) 2022-05-26 09:03:48 -05:00
CONTRIBUTING.md updated contribution guidelines 2020-01-12 10:11:47 +01:00
CONTRIBUTORS release 1.12.2 2022-08-07 12:07:03 +02:00
cppignore.lnx ignore another test 2020-02-09 09:45:25 +01:00
cppignore.win Add HTTPSClientSessionTest::.testCachedSession 2020-01-21 08:23:40 +01:00
DLLVersion.rc chore: 1.12.3 version 2022-08-10 15:32:29 +02:00
env.bat Setup POCO_BASE on Windows 2018-06-20 09:44:33 +02:00
env.sh re-added MongoDB, improved buildwin and release scripts 2013-07-23 15:04:48 +02:00
libversion chore: 1.12.3 version 2022-08-10 15:32:29 +02:00
LICENSE LICENSE: add info about SPDX-License-Identifier usage and use it 2014-05-14 08:38:09 +02:00
Makefile fix Makefile 2022-05-17 08:31:38 +02:00
NEWS Remove \$Id`$ headers 2017-09-09 11:14:06 +02:00
README Add how to install using Conan section on README (#3727) 2022-08-01 07:42:12 -05:00
README.md Add how to install using Conan section on README (#3727) 2022-08-01 07:42:12 -05:00
tsan.suppress Fix/tsan (#3617) 2022-06-01 23:47:26 -05:00
VERSION chore: 1.12.3 version 2022-08-10 15:32:29 +02:00

alt text

poco-ci CII Best Practices

POCO (Portable Components) C++ Libraries are:

  • A collection of C++ class libraries, conceptually similar to the Java Class Library or the .NET Framework.
  • Focused on solutions to frequently-encountered practical problems.
  • Focused on "internet-age" network-centric applications.
  • Written in efficient, modern, 100% ANSI/ISO Standard C++.
  • Based on and complementing the C++ Standard Library/STL.
  • Highly portable and available on many different platforms, from embedded to server.
  • Open Source, licensed under the Boost Software License.

alt text

To start using POCO, see the Guided Tour and Getting Started documents.

Quick Start (with CMake)

Prerequisites

  • CMake 3.5 or newer
  • A C++14 compiler (Visual C++ 2015, GCC 5.0, Clang 3.4, or newer)
  • OpenSSL headers and libraries (optional, but recommended)
  • MySQL, PostgreSQL and ODBC client libraries (optional)

Most Unix/Linux systems already have OpenSSL preinstalled. If your system 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 distribution is fine. For example, via Debian APT:

$ apt-get install openssl libssl-dev

On macOS, the easiest way to install OpenSSL is via Homebrew:

$ brew install openssl

The easiest way to install OpenSSL on Windows is to use a binary (prebuild) release, for example the one from Shining Light Productions that comes with a Windows installer.

On Windows, POCO can also use the native Windows TLS APIs (SChannel).

Installing All Dependencies (Linux and macOS)

All dependencies can be installed with the following commands:

Debian Linux (including Ubuntu and Raspbian)

$ sudo apt-get -y update && sudo apt-get -y install git g++ make cmake libssl-dev

RedHat Linux

$ sudo yum install -y git gcc-c++ make cmake3 openssl-devel

macOS (with Homebrew)

$ brew install cmake openssl

Building with CMake (Linux, macOS, Windows)

CMake (version 3.5 or newer) is the recommended build system for building the POCO C++ Libraries.

$ git clone -b master https://github.com/pocoproject/poco.git
$ cd poco
$ mkdir cmake-build
$ cd cmake-build
$ cmake ..
$ cmake --build . --config Release

On macOS, it's necessary to tell CMake where to find the OpenSSL headers and libraries by setting the OPENSSL_ROOT_DIR CMake variable. For example, if OpenSSL has been installed with Homebrew, the cmake invocation becomes:

$ cmake .. -DOPENSSL_ROOT_DIR=/usr/local/opt/openssl

Other common ways of building with CMake (e.g., cmake-gui) will also work.

There are also a number of project-specific CMake variables that can be changed.

Cross-Compiling

With a proper CMake toolchain file (specified via the CMAKE_TOOLCHAIN_FILE CMake variable), the POCO C++ Libraries can be cross-compiled for embedded Linux systems:

$ cmake .. -DCMAKE_TOOLCHAIN_FILE=/path/to/mytoolchain.cmake -DCMAKE_INSTALL_PREFIX=/path/to/target

Installing

The POCO C++ Libraries headers and libraries can be optionally be installed by building the install target.

$ sudo cmake --build . --target install

The default install location is /usr/local/ on Linux and macOS and C:\Program Files (x64)\ on Windows and can be overridden by setting the CMAKE_INSTALL_PREFIX CMake variable.

Building and Installing - Using vcpkg

You can download and install poco using the vcpkg dependency manager:

$ git clone https://github.com/Microsoft/vcpkg.git
$ cd vcpkg
$ ./bootstrap-vcpkg.sh
$ ./vcpkg integrate install
$ ./vcpkg install poco

The poco port in vcpkg is kept up to date by Microsoft team members and community contributors. If the version is out of date, please create an issue or pull request on the vcpkg repository.

Building and Installing - Using Conan

You can download and install poco using the Conan(https://github.com/conan-io/conan) package manager. It needed to be installed first(https://conan.io/downloads.html):

You can install Poco libraries from Conan Center(https://conan.io/center.html):

$ conan install -r conancenter poco/1.12.0@

Or, you can download Poco recipe and build locally:

$ conan install -r conancenter poco/1.12.0@ --build=poco

The Poco recipe and packages in Conan Center are kept up to date by Conan team members and community contributors. If the version is out of date, or you detect any wrong behavior, please create an issue or pull request(https://github.com/conan-io/conan-center-index) on the Conan Center Index repository.

Building Without CMake

If you do not want to or cannot use CMake, POCO can also be built with Visual Studio (project and solution files included) or GNU Make (Linux, macOS and other supported Unix platforms).

Please refer to the documentation for more information.

Getting POCO via a Package Manager

POCO can also be obtained via different package managers.

Community and Contributing

POCO has an active user and contributing community, please visit our website and blog. Answers to POCO-related questions can also be found on Stack Overflow.

Please see CONTRIBUTING for submitting contributions, bugs reports, feature requests or security issues.

POCO vs. Boost

In regards to Boost, in spite of some functional overlapping, POCO is best thought of as a Boost complement (rather than replacement). Side-by-side use of Boost and POCO is a very common occurrence.