yep, I created a *branch* for the directory structure changes: http://www.bitbucket.org/jpbarrette/curlpp-directory-changes/overview/
On Tue, Nov 11, 2008 at 7:59 AM, Piotr Dobrogost <[EMAIL PROTECTED]>wrote: > > Jean > > Jean-Philippe Barette-LaPierre wrote: > > On Mon, Nov 10, 2008 at 8:51 AM, Piotr Dobrogost <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Jean > > > > I think we should make cURLpp folder structure more standard. We > > should either add include/curlpp/include folder in the root of > > current tree or add include folder in the current curlpp folder. > > There we should put all files clients of lib could need to include > > (interface of the library). That how it's in libcurl. This way > > during building of lib itself I could set CURLPP_PATH to the root > > folder of the project's tree and then use it in the same way as I > > use other paths i.e. CURLPP_PATH/include, LIBCURL_PATH/include, > > OPENSSL_PATH/include etc. > > > > > > Either folder structure suits me. > > Ok. We are missing standard src folder as well. > > I propose to > > 1. change the name of current curlpp folder from curlpp to src > 2. make current utilspp folder a subfolder of src folder > 3. make include folder in the root folder (under curlpp-0.7.2 folder) and > make new folder curlpp as subfolder under include. > 4. move header files which establish interface of the library to the new > /include/curlpp folder > > Changing folder structure makes changes to configure scripts necessary and > I don't know this stuff. > Could you be so kind and make all these changes (folder structure and > configure stuff) by yourself? > > Regards > Piotr Dobrogost > _______________________________________________ > cURLpp mailing list > cURLpp@rrette.com > http://www.rrette.com/mailman/listinfo/curlpp >
_______________________________________________ cURLpp mailing list cURLpp@rrette.com http://www.rrette.com/mailman/listinfo/curlpp
