On Tuesday 13 May 2008 12:12, Jean-Philippe Barrette-LaPierre wrote:
> On Tuesday 13 May 2008 11:48 am, Michael Linck wrote:
> > First off, you need this one (with or w/o slash at the end) for your
> > CURL_INC_DIR:
> >
> > /home/jin/Workspace/Test/Network/curllib/include/
>
> The problem there was :
> > export CPPFLAGS = -I~/Workspace/Test/Network/curllib/include
>
> Because there was no spaces between "-I" and
> "~/Workspace/Test/Network/curllib/include", the shell
> wasn't able to expand the "~", so the directory was the actual
> path "~/Workspace/Test/Network/curllib/include" which isn't valid
> if not expanded.

Hello Jewn-Philippe Barrette-Lapierre!
First of all, I would like to thank you for your very quick response.
(I was surprised to receive reply from a mailing list within an hour)
And Secondly, I would like you to know that I really appreciate your help.

Unfortunately, though, '~/' in -I and was not the issue. I expanded it to full
absolute path, and the configure still didn't pick up the cURL installation..
in desperate measure, I included C headers (instead of C++ wrappers) that came
with cURL.. And this was sufficient to meet the needs of my simple
application.

Although it is working, I still wish to address this issue and include proper
C++ wrappers in my application..
I will try what Michael suggested and let you guys know!

Thank you!

--
Jin
_______________________________________________
cURLpp mailing list
cURLpp_at_rrette.com
http://www.rrette.com/mailman/listinfo/curlpp