🚀 go-pugleaf

"Frank" <frank.hofmann@stahlwerk-thueringen.de> wrote in message
news:41a1d512$1@newsgroups.borland.com...

> There's an include error between winsock.h of bcb
> and winsock2.h which comes with the indy package...

winsock2.h does not ship with Indy.  It ships with BCB, as does winsock.h.
They are both Microsoft headers, not Borland headers, and Microsoft did not
make the two headers compatible with each other.  Most Internet components,
particular those that ship with BCB by default, still use WinSock v1.x and
thus winsock.h.  Indy, on the other hand, uses WinSock 2.x and thus
winsock2.h instead.  The two do not co-exist in the same project very well.
Blame Microsoft, not Borland or Indy.  Are you trying to use other
Internet-related components in your project in addition to Indy?  If so,
why?

> I tried to define _WINSOCK_ in the cpp of my projectfile to
> prevent the include of winsock.h but it seems that the compiler
> includes the file before that #define statement...

The best place to make such a define is in the Prohect Options instead.
However, making such a define effects winsock2.h as well, so I do not advise
you to go that route in the first place.

> Please help....

Please go to http://www.deja.com and search through the newsgroup archives.
This issue has been discussed many many times before.

> With newer Versions of Indy the Installtion fails on my
> system. (install okay, can't use components)

Please provide more details.


Gambit