1.3.6 Coming Next Week
If everything goes well and no serious issues come up, 1.3.6 will be released next Tuesday. Please use the time to do some more testing with the 1.3.6 branch.
November 17, 2009
12 Comments »
RSS feed for comments on this post.
TrackBack URI
Great! Will be awaiting with great interest!
Comment by Viet on November 17, 2009, 19:07
Hopefully it works under OS X:)
Comment by Nathan on November 19, 2009, 11:09
> Hopefully it works under OS X:)
It does. That’s where I’m working most of the time.
Comment by guenter on November 19, 2009, 11:15
So you are Mac lover too! Today is Sunday, I hope everything is going well and you have wonderful Sunday too!
Comment by Viet on November 21, 2009, 23:00
It doesn’t. See the forum post by someone else. If you use a couple of debug flags, that are common with debug projects in OS X poco projects crash. Works in release mode tho.
Comment by Nathan on November 22, 2009, 10:44
Okay, I changed the build settings for Mac OS X to match those used by Xcode projects. The main issue seems to be the use of -D_GLIBCXX_DEBUG=1 -D_GLIBCXX_DEBUG_PEDANTIC=1 by Xcode projects. I can now successfully run and debug Xcode-built projects linked with POCO libs.
Comment by guenter on November 22, 2009, 17:45
You are the best!! Any chance of Poco making it on GitHub?
Comment by Nathan on November 22, 2009, 19:10
>Any chance of Poco making it on GitHub?
To avoid hijacking this thread, I have posted this issue on the forum Wishlist.
Comment by alex on November 22, 2009, 19:52
Yes, git can be compared to SVN, as you did in that thread. But github is a different beast. I think people are suggesting it because Poco needs more community:
1. Git allows community.
2. People can fork your code, make contributions, and issue a pull request (if you approve).
3. Get more adoption and visibilty.
4. Probably get more revenue.
I also think that Poco needs cleaner bug system. I would highly recommend you guys check out MongoDB. In about a year that entire project has just blown up, rapid adoption, tons of users forking and contributing bugs, and it columinated with a 4.3 million dollar funding round.
Comment by electic on November 23, 2009, 00:27
1.3.6 still does not seem to work in os x debug mode. Use the sample ServerApplication project in an default xcode command line project.
Call this in Application initialize method:
ThreadPool::defaultPool().addCapacity(500);
you get this in debug mode:
malloc: *** error for object 0×7fff7067b500: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
seems to work in release however…
Comment by John on November 25, 2009, 17:07
> 1.3.6 still does not seem to work in os x debug mode.
Perhaps related to this problem?
Comment by alex on November 25, 2009, 22:25
Works for me on 10.5 and Xcode 3.1.3. Haven’t tested on 10.6 yet. In any case, finding out the correct build flags and changing build/config/Darwin shouldn’t be too hard…
Comment by guenter on November 25, 2009, 22:29