On 10-Nov-08, at 5:00 PM, Brad Hubbard <curlpp_at_brand-hubs.com> wrote:

>
>
> Jean-Philippe Barette-LaPierre wrote:
>>
>> On Mon, Nov 10, 2008 at 8:51 AM, Piotr Dobrogost <curlpp_at_2008.autoera.pl
>> > 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.
> Obviously we don't want to change the structure under *nix as the /
> usr/local/include/curlpp is already "standard".
>

Absolutely, but we were talking more specifically of the source
directory, not the installation directory (which they dont really have
on windows).

> Kindest regards,
> Brad Hubbard
> _______________________________________________
> cURLpp mailing list
> cURLpp_at_rrette.com
> http://www.rrette.com/mailman/listinfo/curlpp

_______________________________________________
cURLpp mailing list
cURLpp_at_rrette.com
http://www.rrette.com/mailman/listinfo/curlpp
Received on 2008-11-11