mirror of
https://github.com/pocoproject/poco.git
synced 2024-12-15 19:33:07 +01:00
40 lines
2.0 KiB
Markdown
40 lines
2.0 KiB
Markdown
POCO C++ Libraries
|
||
==================
|
||
|
||
Build Status
|
||
------------
|
||
|
||
- Travis: [![Travis Build Status](https://travis-ci.org/pocoproject/poco.png?branch=develop)](https://travis-ci.org/pocoproject/poco)
|
||
- AppVeyor: [![AppVeyor Build Status](https://ci.appveyor.com/api/projects/status/7iyrx3f233s3akae)](https://ci.appveyor.com/project/obiltschnig/poco)
|
||
- [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/370/badge)](https://bestpractices.coreinfrastructure.org/projects/370)
|
||
|
||
|
||
![alt text][logo]
|
||
|
||
POrtable COmponents C++ Libraries are:
|
||
--------------------------------------
|
||
- A collection of C++ class libraries, conceptually similar to the Java Class Library, the .NET Framework or Apple’s Cocoa.
|
||
- 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](https://spdx.org/licenses/BSL-1.0).
|
||
|
||
----
|
||
To start using POCO, see the [Guided Tour](https://pocoproject.org/docs/00100-GuidedTour.html)
|
||
and [Getting Started](https://pocoproject.org/docs/00200-GettingStarted.html) documents.
|
||
|
||
----
|
||
POCO has an active user and contributing community, please visit our [web site](https://pocoproject.org) and [blog](https://pocoproject.org/blog).
|
||
Answers to POCO-related questions can also be found on [Stack Overflow](https://stackoverflow.com/questions/tagged/poco-libraries).
|
||
|
||
Please see [CONTRIBUTING](CONTRIBUTING.md) for submitting contributions, bugs reports, feature requests or security issues.
|
||
|
||
----
|
||
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.
|
||
|
||
[logo]: https://raw.githubusercontent.com/pocoproject/poco/develop/doc/poco.png "Poco Layout"
|