>>> Please try to add the "$EXTERNALSYM" directive like:
>>> ...
>>>
>>> Rebuild the ICS packages, does that change anything?
>>
>> Where do I add this code then please ?
>
> In OverbyteIcsLibrary.pas beginning at ~ line 510.
I'm totally NOT component savvy, so I don't know what I'm doing.
Your literal text did not compile and there were conflicts as well, which I
solved by commenting the already present code out, in favour of what I
added.
So I basically added and changed following text right before the word
"implementation"
I hope that is OK ?
Notice the last 4 "function" calls that I had to comment out before it
compiled.
{code}
{$EXTERNALSYM Application}
function Application : TApplication;
{$EXTERNALSYM MakeWord}
function MakeWord(a, b: Byte): Word;
{$EXTERNALSYM MakeLong}
function MakeLong(a, b: Word): Longint;
{$EXTERNALSYM HiWord}
function HiWord(L: DWORD): Word;
{$IFNDEF NOFORMS}
// function Application : TApplication;
{$ENDIF}
{$ENDIF}
// function MakeWord(a, b: Byte): Word;
// function MakeLong(a, b: Word): Longint;
// function HiWord(L: DWORD): Word;
implementation
{code}
Incidently, that DID solve the Application Ambiguity issue !!
Can somebody who knows what (s)he is doing add/change this properly so that
the next update works under CB2009 ?
I'm still completely overwhelmed by following errors:
[BCC32 Error] Overbyteicslibeay.hpp(253): E2015 Ambiguity between 'Byte' and
'System::Byte'
[BCC32 Error] Overbyteicsntlmmsgs.hpp(102): E2015 Ambiguity between 'Byte'
and 'System::Byte'
I wonder, how are the other CB2009 users doing ? No such problems ?
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
