I appreciate your attention to this. So, I think it might be possible
to get rid of the warnings by adding some dllimports into libcurl, which
would cause libcurlpp to be linked without inline re-definitions of curl
functions. But unfortunately that wouldn't solve the real problem,
namely the fatal errors. Those confound me because it seems to be
complaining that it can't find definitions of template specializations.
That makes no sense, since template specializations should be defined
in-line anyway, so if, in a library, the linker comes upon a template
specialization, it's definition should always be there right? So WTF?
Maybe the microsoft compiler works differently and there's something odd
about the way it defines the specializations and some means by which the
definitions can be lost in between stages. I wouldn't put it past them.

Anyway, I can tell you that there are some iffy definitions in your
current version of curlpp. I don't actually build my project in Visual
Studio ( I use CMake because it generally does most of the platform-fu
fairly successfully) so I can't give you a project file for what I'm
doing, but some things you might want to look at if you get this onto a
windows platform are the dllfct header. This just dllexports everything
when a windows library is being build and dllimports everything when
it's being linked in. It doesn't seem to work that way. Also, when I
left that on, I had to go through curlpp code and remove a bunch of
dllimports and dellexports that were questionably placed, so that might
be a place for you to start. All I really know about Microsoft linkage
is that when we don't use /WD to link everything, nothing works. That's
it :) I don't know why. I don't know what it means. And I really
don't care to learn it because I don't use it often enough to matter and
I have a work piled up in front of me and management starting to ask
what I've been up to the last month or so :)

I appreciate you thinking about this stuff, but I've been digging
through the material online for almost a week and I haven't found
anything that actually explains to me what my problem is sufficiently
for me to able to solve it. I was hoping maybe someone on this list had
run into it and figured out a way to get it to work, but since that's
not the case, I'm unwilling to spend any more time on this approach.

thanks again,

mike

Jean-Philippe Barrette-LaPierre wrote:
> On Tuesday 29 April 2008 12:54 pm, Michael Linck wrote:
>
>> Does anyone know what this means? These don't look like any linker
>> errors that any linker I've ever worked with closely would even think of
>> producing....
>>
>
> Looking at the README.win32 and looking at the errors, I just don't know
> what would be the problem. Can you send your project file? You don't need
> to send the source code of your project. Or maybe if you could send the
> linker commands that you are using?
>
>

-- 
ÐÏࡱá
_______________________________________________
cURLpp mailing list
cURLpp_at_rrette.com
http://www.rrette.com/mailman/listinfo/curlpp