🚀 go-pugleaf

An Update:  I tried run time creation of the previously mentioned code, a 
rebuild of Indy, and various other attempts, no joy.

However, the follwoing code does work.  So there isn't anything major wrong 
with the Indy build and the SysLog components, but must be something 
specifically wrong with the SendMessage methods.  Has anyone come across 
this before?

void __fastcall TForm1::Button1Click(TObject *Sender)
{
    TIdSysLog * c = new TIdSysLog(NULL);
    c->Host   = "127.0.0.1";
    c->ReceiveTimeout = 15000;
    c->Active = true;

    TIdSysLogMessage * t = new TIdSysLogMessage(NULL);
    t->Msg->Content = "Hi Server";
    t->Severity = slDebug;
    t->Facility = sfUserLevel;
    t->SendToHost("127.0.0.1");

    delete t;
    delete c;
}


"Paul" <plmacca@clara.co.uk> wrote in message 
news:4412d1f1$1@newsgroups.borland.com...
> Hi,
>
> I've built and included Indy9 (as far as I can tell).  I've made a couple 
> of small apps to test the build and components and I get the following 
> error with SysLog (Client) link:
>
> [Linker Error] Unresolved external '__fastcall 
> Idsyslog::TIdSysLog::SendMessageA(const Idsyslogmessage::TIdSysLogMessage 
> *, const bool)' referenced from D:\VSS\SYSLOGSERVER\CLIENTFORM.OBJ
> [Linker Error] Unresolved external '__fastcall 
> Idsyslog::TIdSysLog::SendMessageA(const System::AnsiString, const 
> Idsyslogmessage::TIdSyslogFacility, const 
> Idsyslogmessage::TIdSyslogSeverity)' referenced from 
> D:\VSS\SYSLOGSERVER\CLIENTFORM.OBJ
>
> Any ideas? (test code below).  I'm a bit confused why the method in the 
> header is "SendMessage", the linkers says SendMessageA, and it compiles 
> with either (and makes no difference to the linker error).
>
> Regards
>
> Paul