Comments on: Poco 1.3.0b1 http://pocoproject.org/blog/?p=37 News and discussion for the POCO Community Thu, 09 May 2013 12:05:16 +0200 http://wordpress.org/?v=2.8.5 hourly 1 By: Ivo Roper http://pocoproject.org/blog/?p=37&cpage=1#comment-105 Ivo Roper Wed, 11 Jun 2008 02:31:53 +0000 http://appinf.com/poco/blog/?p=37#comment-105 Having been primed for poco being DLL only by some old docs, I was happily surprised to open the solution file and found debug_static and release_static configurations already there. Just tacking this onto the end of this thread so that folks stumbling across this will know that this isn't an issue any longer. (compiling 1.3.2 right now) ^_^ Having been primed for poco being DLL only by some old docs, I was happily surprised to open the solution file and found debug_static and release_static configurations already there.

Just tacking this onto the end of this thread so that folks stumbling across this will know that this isn’t an issue any longer. (compiling 1.3.2 right now) ^_^

]]> By: peter http://pocoproject.org/blog/?p=37&cpage=1#comment-104 peter Thu, 23 Nov 2006 19:07:51 +0000 http://appinf.com/poco/blog/?p=37#comment-104 So here is a rough guideline. If you encounter problems, simply mail me or post in the forum. Open Foundation_vs80.sln Go the Configuration Manager and create a new debug_static config. Use debug_shared for the defaults. Now update the properties of the debug_static configuration: - Common: switch from create dll to static library. Be sure to press Apply! Change the output dirs from .\obj\debug_shared to .\obj\debug_static - C/C++: - Preprocessor: remove _USRDLL, Foundation_EXPORTS (also remove POCO_DLL if there) add POCO_STATIC - Library: set output to ..\lib\PocoFoundationmtd.lib repeat for release build, just use release_shared and ..\lib\PocoFoundationmt.lib applications are simpler: add POCO_STATIC and link against the mt*.lib versions and also repeat for CppUnit, Net, XML, Util too, and testsuites and samples... So it's actually quite a lot of work and we are currently lacking the time to do it. But if you manage to do it, we will gladly support you and integrate your work back in the final 1.3 release. thx Peter PS: YOu must update WinTestRunner.h to: #if !defined(POCO_STATIC) #if defined(WinTestRunner_EXPORTS) #define WinTestRunner_API __declspec(dllexport) #else #define WinTestRunner_API __declspec(dllimport) #endif #else #define WinTestRunner_API #endif If you get link errors to _GetAdaptersInfo, add iphlpapi.lib. For network code add ws2_32.lib. for __imp__timeGetTime add winmm.lib So here is a rough guideline.
If you encounter problems,
simply mail me or post in the forum.

Open Foundation_vs80.sln
Go the Configuration Manager and create a new debug_static config. Use debug_shared for the defaults.
Now update the properties of the debug_static configuration:
- Common: switch from create dll to static library. Be sure to press Apply!
Change the output dirs from .\obj\debug_shared to .\obj\debug_static
- C/C++:
- Preprocessor: remove _USRDLL, Foundation_EXPORTS (also remove POCO_DLL if there)
add POCO_STATIC
- Library: set output to ..\lib\PocoFoundationmtd.lib

repeat for release build, just use release_shared and ..\lib\PocoFoundationmt.lib

applications are simpler: add POCO_STATIC and link against the mt*.lib versions

and also repeat for CppUnit, Net, XML, Util too, and
testsuites and samples…

So it’s actually quite a lot of work and we are currently lacking the time to do it.
But if you manage to do it, we will gladly support you and integrate your work
back in the final 1.3 release.
thx
Peter

PS: YOu must update WinTestRunner.h to:
#if !defined(POCO_STATIC)
#if defined(WinTestRunner_EXPORTS)
#define WinTestRunner_API __declspec(dllexport)
#else
#define WinTestRunner_API __declspec(dllimport)
#endif
#else
#define WinTestRunner_API
#endif

If you get link errors to _GetAdaptersInfo, add iphlpapi.lib.
For network code add ws2_32.lib.
for __imp__timeGetTime add winmm.lib

]]> By: paschal http://pocoproject.org/blog/?p=37&cpage=1#comment-103 paschal Thu, 23 Nov 2006 15:57:10 +0000 http://appinf.com/poco/blog/?p=37#comment-103 Please can you provide static builds as well? Sometimes it makes sense to compile statically to minimize the number of files when deploying simple apps. I have tried unsuccessfully to create static libs may be just instructions on how to do this would be helpful. p. Please can you provide static builds as well? Sometimes it makes sense to compile statically to minimize the number of files when deploying simple apps. I have tried unsuccessfully to create static libs may be just instructions on how to do this would be helpful.

p.

]]> By: tom http://pocoproject.org/blog/?p=37&cpage=1#comment-102 tom Thu, 23 Nov 2006 08:02:07 +0000 http://appinf.com/poco/blog/?p=37#comment-102 I just found the cause. the build would fail if it's run from a path which contains any space(' ') inside it. I guess you should put all the path you refer to in your script inside a pair of quotes, as is usually recommended in Windows. I just found the cause. the build would fail if it’s run from a path which contains any space(’ ‘) inside it.

I guess you should put all the path you refer to in your script inside a pair of quotes, as is usually recommended in Windows.

]]> By: peter http://pocoproject.org/blog/?p=37&cpage=1#comment-101 peter Thu, 23 Nov 2006 07:14:58 +0000 http://appinf.com/poco/blog/?p=37#comment-101 Hi Tom, glad you found our library. The link error you mentioned didn't occur in our test environment, so to be able to help you, I need a bit more information: - Did you read the Build tutorial at http://appinf.com/poco/wiki/tiki-index.php?page=FirstStepsWindows ? - Do you use the p drive mapping? (one possible error is that the project that fails links to PocoFoundation via an absolute path (they should be relative though)) - What is the first project that gives you that error? - Does the debug build of that project works (ie PocoFoundationd.lib is found) - Does poco\lib contain a PocoFoundation.lib? - Does Foundation build in release shared mode in the IDE? (it's quite easy to overlook an error in the bat file) Hope we can pin down that error :-) br Peter Hi Tom,
glad you found our library. The link error you mentioned didn’t occur in our test environment, so
to be able to help you, I need a bit more information:
- Did you read the Build tutorial at http://appinf.com/poco/wiki/tiki-index.php?page=FirstStepsWindows ?
- Do you use the p drive mapping? (one possible error is that the project that fails links to PocoFoundation via an absolute path (they should be relative though))
- What is the first project that gives you that error?
- Does the debug build of that project works (ie PocoFoundationd.lib is found)
- Does poco\lib contain a PocoFoundation.lib?
- Does Foundation build in release shared mode in the IDE? (it’s quite easy to overlook an error in the bat file)

Hope we can pin down that error :-)
br
Peter

]]> By: tom http://pocoproject.org/blog/?p=37&cpage=1#comment-100 tom Thu, 23 Nov 2006 03:59:08 +0000 http://appinf.com/poco/blog/?p=37#comment-100 I tried to build with VS2005 in WinXP, either with the IDE or your bat file I got a bunch of link errors, "LINK : fatal error LNK1181: cannot open input file 'PocoFoundation.lib'" How can I solve this problem? Your library seems s quite interesting to me, I am eager to try it. Thanks, tom I tried to build with VS2005 in WinXP, either with the IDE or your bat file I got a bunch of link errors,
“LINK : fatal error LNK1181: cannot open input file ‘PocoFoundation.lib’”
How can I solve this problem?

Your library seems s quite interesting to me, I am eager to try it.

Thanks,
tom

]]> By: alex http://pocoproject.org/blog/?p=37&cpage=1#comment-99 alex Sun, 19 Nov 2006 12:19:08 +0000 http://appinf.com/poco/blog/?p=37#comment-99 Paschal: Unfortunately, Molto has been on the back burner for a looong time (I still have to remove ancient namespace macros :-/ ). I had multiple inquiries on it recently and I will seriously try to push the code out within the next week or two. It will definitely not be a release, but it will compile and be usable. Stay tuned ... Alex Paschal:

Unfortunately, Molto has been on the back burner for a looong time (I still have to remove ancient namespace macros :-/ ). I had multiple inquiries on it recently and I will seriously try to push the code out within the next week or two. It will definitely not be a release, but it will compile and be usable. Stay tuned …

Alex

]]> By: Paschal http://pocoproject.org/blog/?p=37&cpage=1#comment-98 Paschal Sun, 19 Nov 2006 01:46:49 +0000 http://appinf.com/poco/blog/?p=37#comment-98 Alex, I am curious about progress on Molto; A Poco based servlet engine that you mentioned a few months ago. If you need tester I am wiling and ready. I can't help out much with code however because I don't consider myself a c++ guru like you folks. I don't mind the absence of database access if you haven't sorted this out. I can always mix with the excellent libray by Sergey ( OTL ). p. Alex,
I am curious about progress on Molto; A Poco based servlet engine that you mentioned a few months ago. If you need tester I am wiling and ready. I can’t help out much with code however because I don’t consider myself a c++ guru like you folks.
I don’t mind the absence of database access if you haven’t sorted this out. I can always mix with the excellent libray by Sergey ( OTL ).

p.

]]> By: alex http://pocoproject.org/blog/?p=37&cpage=1#comment-97 alex Sat, 18 Nov 2006 15:58:56 +0000 http://appinf.com/poco/blog/?p=37#comment-97 Tim: PocoData is still incubating in the sandbox. Curently, there are SQLite and ODBC connectors (former tested on windows only). Obviously, this is not yet a release-grade material, but you are more than welcome to play with it and give feedback, suggestions or report any potential problems. Newly introduced Foundation::Tuple provides a solid ground for some useful additions such as Data::Recordset. As usual, the amount of available time is the most significant obstacle to everything, so if there is anyone out there willing to donate some time by testing ODBC connector on any *NIX or developing a native connector (PostgreSQL, MySQL, ...) it would be much appreciated. Alex Tim:

PocoData is still incubating in the sandbox. Curently, there are SQLite and ODBC connectors (former tested on windows only). Obviously, this is not yet a release-grade material, but you are more than welcome to play with it and give feedback, suggestions or report any potential problems.
Newly introduced Foundation::Tuple provides a solid ground for some useful additions such as Data::Recordset.
As usual, the amount of available time is the most significant obstacle to everything, so if there is anyone out there willing to donate some time by testing ODBC connector on any *NIX or developing a native connector (PostgreSQL, MySQL, …) it would be much appreciated.

Alex

]]> By: Tim http://pocoproject.org/blog/?p=37&cpage=1#comment-96 Tim Sat, 18 Nov 2006 00:16:45 +0000 http://appinf.com/poco/blog/?p=37#comment-96 No word on Poco Data? I am looking foward to it. tim No word on Poco Data? I am looking foward to it.

tim

]]>