The POCO C++ Libraries Blog

Welcome to the POCO Community!

Filed under: News by guenter at 12:58

The POCO project was started in 2004 by Günter Obiltschnig. In the following years he was joined by developers from Applied Informatics and the open source community. Günter has been a fan of the open source model for many years. This led to the decision to make POCO available for free, under the Boost license.

So go ahead, download POCO, have fun with it and give us a couple of minutes and let us know how you are doing. That’s your contribution to the ongoing development of POCO. Thank you for being part of it.

Don’t hesitate to get in touch with us if you have any questions or you like to contribute to the project.

  1. Did you move DBLite out of the bundle? What is the reason and what do you want to use instead?


    Comment by tranquil on July 11, 2006, 18:37

  2. Thank you for the liberal licensing. Now that a boost license is used, I will DEFINITELY be using this wonderful kit, and will advertise it to my friends and clients. Good luck, I hope POCO really takes off!

    Comment by Jeremy Jurksztowicz on July 12, 2006, 01:09

  3. We currently provide DBLite and NetSSL, as well as a few other packages (Remoting, FastInfoSet, …) only as part of a support contract/SLA.
    However, regarding database support, we will soon start a project to bring a SQL database access library supporting multple database engines to POCO.

    Comment by guenter on July 12, 2006, 08:28

  4. What will the governance process be for submitting changes?

    (And are you going to remove the references to NetSSL in the pdf documentation? I can understand why there’s a desire to protect some of the system to generate revenue, but these components are referenced as part of POCO but there’s no indication that they are witheld, or what the price is for the support contract.)

    Comment by James Mansion on July 12, 2006, 14:19

  5. We generally welcome changes from the community. For now, the best way to get changes into POCO is to discuss them on or send them to the poco-develop mailing list.

    (Yes, we will put up updated documentation referring only the Boost licensed libraries in the next few days).

    Comment by guenter on July 12, 2006, 15:35

  6. Er, is this the place where the POCO community discuss things? IMO it is not clear from the main web page, nor the annoucemenrt I saw in comp.lang.c++.moderated. I initially tried the WIKI but that did not work for me. It seems to be empty. Oh well, I will post here for now. I am impressed with POCO so far but I have only just started to look at it. Will post more as I find out more….

    BTW, it is traditional to be able to preview a post before committing it. Perhaps this is an improvement that could be made to this blog facility?

    Comment by Andrew Marlow on July 16, 2006, 21:36

  7. One odd thing I have run into almost right away is that the Makefiles do not seem to work unless invoked by the top level Makefile from the top-level directory. I went into a test directory and tried to rebuild one of the tests and I got errors like:

    Makefile:9: /build/rules/global: No such file or directory.

    If there is a Makefile in a directory I expect to be able to go that directory, type ‘make’ and it will make whatever is in that directory. What is going on please?

    -Andrew Marlow

    Comment by Andrew Marlow on July 16, 2006, 21:57

  8. Andrew, we are still in the process of setting up the community. At this time, there is no content yet in the Wiki, but this will change in the coming days. A good place for discussion is also the poco-develop mailing list.

    Regarding the make issue, before invoking a Makefile you have to set the environment variable POCO_BASE to the directory where POCO is located (e.g. export POCO_BASE=/users/guenter/poco-1.1.2). You can then invoke gmake separately for each of the testsuites or samples. You might also want to take a look at the README file 😉

    Comment by guenter on July 17, 2006, 11:46

RSS RSS feed for comments on this post. TrackBack URI

Leave a comment