Overview
Features
Download
Documentation
Community
Add-Ons & Services
The POCO C++ Libraries Blog

POCO 1.3.5 Available

Filed under: News by guenter at 20:23

Version 1.3.5 of the POCO C++ Libraries has been released today. This is mostly a bugfix release, fixing some bugs in the NetSSL, Crypto and Zip libraries, plus a few minor enchancements. Upgrading from 1.3.4 is optional.

Here is the CHANGELOG.

7 Comments »
  1. Great! I’m updated. Thanks for the release. Have you marked your calendar when the version 1.4.0 will be released?

    Comment by Viet on May 16, 2009, 09:14

  2. Thanks for your hard work, Guenter.

    Comment by coolzdp on May 16, 2009, 16:55

  3. I tried to build with VS2005 in WinXP by command: “buildwin.cmd 80 build static both yes” and I am received error:
    “LINK : fatal error LNK1181: cannot open input file ‘PocoFoundation.lib’”

    - I don’t use the p drive mapping.
    - I received this problem during Building Foundation project.
    - There are two files for Foundation project in lib folder:
    PocoFoundationmt.lib and PocoFoundationmtd.lib.

    How can I solve this problem for version 1.3.5?

    Comment by Mega on May 22, 2009, 13:16

  4. If it’s the TestLibrary project complaining, you can ignore it – it’s looking for the DLL .lib stub which is not there. If you want to eliminate the linking error, build shared first, then static.

    Comment by alex on May 23, 2009, 19:25

  5. I have downloaded the 1.3.5 version of ibrary at 22 May 09. How can I check if I it’s the TestLibrary project complaining?

    I was able to build static version of library after build dynamic version at first. But, I am not able to use the library as static version – compilator always looks for *.dll files during running my programs even added static lib.

    Comment by Mega on May 24, 2009, 23:27

  6. The project files for the sample projects delivered with POCO only support linking with the shared libraries. If you want to link statically to POCO, you have to change your project’s properties accordingly. The most important thing to do is to define the POCO_STATIC macro for your project. The POCO header files contain some pragmas that will cause automatic linking of the respective library. Normally, the DLL version of the library will be linked (e.g. PocoFoundation.lib). If you define the POCO_STATIC macro, the static library (PocoFoundationmt.lib) will be used instead.

    Comment by guenter on May 25, 2009, 09:53

  7. I have the same probleme,
    with Visual studio 2012, when I build the project thas containt Poco lybrary I have this message:
    LNK1104: impossible d’ouvrir le fichier ‘PocoFoundationd.lib’

    pleas help me!!!!

    Comment by steve on April 3, 2013, 19:05

RSS RSS feed for comments on this post. TrackBack URI

Leave a comment