<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Welcome to the POCO Community!</title>
	<atom:link href="http://pocoproject.org/blog/?feed=rss2&#038;p=145" rel="self" type="application/rss+xml" />
	<link>http://pocoproject.org/blog/?p=145</link>
	<description>News and discussion for the POCO Community</description>
	<lastBuildDate>Thu, 09 May 2013 12:05:16 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: guenter</title>
		<link>http://pocoproject.org/blog/?p=145&#038;cpage=1#comment-9</link>
		<dc:creator>guenter</dc:creator>
		<pubDate>Mon, 17 Jul 2006 09:46:40 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=3#comment-9</guid>
		<description>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 ;-)</description>
		<content:encoded><![CDATA[<p>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.</p>
<p>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 <img src='http://pocoproject.org/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Marlow</title>
		<link>http://pocoproject.org/blog/?p=145&#038;cpage=1#comment-8</link>
		<dc:creator>Andrew Marlow</dc:creator>
		<pubDate>Sun, 16 Jul 2006 19:57:06 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=3#comment-8</guid>
		<description>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 &#039;make&#039; and it will make whatever is in that directory. What is going on please?

-Andrew Marlow</description>
		<content:encoded><![CDATA[<p>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:</p>
<p>Makefile:9: /build/rules/global: No such file or directory.</p>
<p>If there is a Makefile in a directory I expect to be able to go that directory, type &#8216;make&#8217; and it will make whatever is in that directory. What is going on please?</p>
<p>-Andrew Marlow</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Marlow</title>
		<link>http://pocoproject.org/blog/?p=145&#038;cpage=1#comment-7</link>
		<dc:creator>Andrew Marlow</dc:creator>
		<pubDate>Sun, 16 Jul 2006 19:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=3#comment-7</guid>
		<description>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?</description>
		<content:encoded><![CDATA[<p>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&#8230;.</p>
<p>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?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: guenter</title>
		<link>http://pocoproject.org/blog/?p=145&#038;cpage=1#comment-6</link>
		<dc:creator>guenter</dc:creator>
		<pubDate>Wed, 12 Jul 2006 13:35:49 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=3#comment-6</guid>
		<description>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).</description>
		<content:encoded><![CDATA[<p>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.</p>
<p>(Yes, we will put up updated documentation referring only the Boost licensed libraries in the next few days).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Mansion</title>
		<link>http://pocoproject.org/blog/?p=145&#038;cpage=1#comment-5</link>
		<dc:creator>James Mansion</dc:creator>
		<pubDate>Wed, 12 Jul 2006 12:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=3#comment-5</guid>
		<description>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&#039;s a desire to protect some of the system to generate revenue, but these components are referenced as part of POCO but there&#039;s no indication that they are witheld, or what the price is for the support contract.)</description>
		<content:encoded><![CDATA[<p>What will the governance process be for submitting changes?</p>
<p>(And are you going to remove the references to NetSSL in the pdf documentation?  I can understand why there&#8217;s a desire to protect some of the system to generate revenue, but these components are referenced as part of POCO but there&#8217;s no indication that they are witheld, or what the price is for the support contract.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: guenter</title>
		<link>http://pocoproject.org/blog/?p=145&#038;cpage=1#comment-4</link>
		<dc:creator>guenter</dc:creator>
		<pubDate>Wed, 12 Jul 2006 06:28:31 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=3#comment-4</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>We currently provide DBLite and NetSSL, as well as a few other packages (Remoting, FastInfoSet, &#8230;) only as part of a support contract/SLA.<br />
However, regarding database support, we will soon start a project to bring a SQL database access library supporting multple database engines to POCO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Jurksztowicz</title>
		<link>http://pocoproject.org/blog/?p=145&#038;cpage=1#comment-3</link>
		<dc:creator>Jeremy Jurksztowicz</dc:creator>
		<pubDate>Tue, 11 Jul 2006 23:09:18 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=3#comment-3</guid>
		<description>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!</description>
		<content:encoded><![CDATA[<p>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!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tranquil</title>
		<link>http://pocoproject.org/blog/?p=145&#038;cpage=1#comment-2</link>
		<dc:creator>tranquil</dc:creator>
		<pubDate>Tue, 11 Jul 2006 16:37:12 +0000</pubDate>
		<guid isPermaLink="false">http://appinf.com/poco/blog/?p=3#comment-2</guid>
		<description>Did you move DBLite out of the bundle? What is the reason and what do you want to use instead?

Cheers,
tranquil</description>
		<content:encoded><![CDATA[<p>Did you move DBLite out of the bundle? What is the reason and what do you want to use instead?</p>
<p>Cheers,<br />
tranquil</p>
]]></content:encoded>
	</item>
</channel>
</rss>
