Hi Przemek,

> Please try to use hbmk2 to compile some OLE server examples.
> 
>   hbmk2 olesrv1.hbp
> 
>   hbmk2: Processing local make script: hbmk.hbm
>   Error BASE/1066  Argument error: conditional (Quit)
>   Error BASE/1066  Argument error: conditional
>   Called from FN_EXPAND(0)
>   Called from HBC_PROCESSONE(0)
>   Called from HBMK2(0)
>   Called from MAIN(0)
> 
> It's caused by source=... commands.
> If you change:
>   sources={mingw}hbolesrv-mingw.def
> to
>   {mingw}hbolesrv-mingw.def
> then it works correctly.

With such syntax the .def files are simply ignored in .hbc files, 

> Can you fix it?

Ops, I've found it, thank you. It was older oversight 
(missed to pass obligatory parameter to FN_EXPAND()), 
and only affected *nix builds.

> BTW. If you decided to split olesrv?.hbp files then I suggest to move
> -hbdynvm to hbolesrv.hbc hbolesrv.c code is designed for inproc DLLs
> only.

Target mode selection is not supported in .hbc file, 
because I think it could easily make things too 
confusing. It looks cleaner to select mode form a .hbp 
file, so that it's easy to see what will happen.

Let's see how OLE server creation will evolve and 
maybe we can further simplify some things.

Another thing I noticed is that I cannot build 
watcom servers, not clients. For servers it 
complains about 'Error! E2030: file clib3s.lib(cstrtwwt): multiple starting 
addresses found', 
for clients there are unresolved symbol, even 
if I comment the special -cflag in .hbp.

I think watcom should truly be fixed by switching 
to default callconv on the Harbour level, though 
in this case for win/watcom builds all HB_EXPORT 
declarations need have a __cdecl modifier added 
between return type and function name. And this is 
currently not possible without creating a new scheme 
for public C function declaration (at least I could 
not find a painless solution).

> I think also that hbolesrv.hbc should contain also libs=hbwin so user
> can easy use it to create his own inproc DLLs.

You're right, I've added it.

Viktor

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to