1. EuCOM: Migrating from Eu v3.1.1 To Eu v4.0.3
- Posted by Rad Jan 13, 2012
- 1275 views
Hi,
I am using EuCOM in my application and encountering the following errors while trying to run my v3.1.1 application under v4.0.3:
D:\EUPHORIA\EuWin32Lib\0.70.20\Include\win32lib.ew:10090
<0074>:: Errors resolving the following references:
..\..\..\EuWin32Lib\0.70.20\Include\win32lib.ew (10066): OleInitialize
..\..\..\EuWin32Lib\0.70.20\Include\win32lib.ew (10070): OleUninitialize
..\..\..\EuWin32Lib\0.70.20\Include\win32lib.ew (10090): OleUninitialize
OleUninitialize()
^
--- Defined Words ---
EU4
EU4_0
EU4_0_3
WINDOWS
WIN32
CONSOLE
EUI
-------------------
The concerned w32ole.ew file is now included as
include w32ole.ew as ole
in w32file.ew, which is included in win32lib.ew.
Do I have to change win32lib.ew to refer to ole functions like -
ole:OleInitialize()
Please advise how to proceed?
Thanks & Regards,
Rad.
2. Re: EuCOM: Migrating from Eu v3.1.1 To Eu v4.0.3
- Posted by mattlewis (admin) Jan 13, 2012
- 1240 views
I am using EuCOM in my application and encountering the following errors while trying to run my v3.1.1 application under v4.0.3:
...
Do I have to change win32lib.ew to refer to ole functions like -
ole:OleInitialize()
It seems like that should work. I believe that the problem is that both w32ole.ew and eucom.ew declare a global OleInitizlize symbol. Still, unless you've modified your copy of win32lib.ew to include eucom.ew, it should be smart enough to find the OleInitialize in w32ole.ew.
Try adding "include w32ole.ew" in win32lib.ew. If that doesn't work, then you probably need to update with namespace qualifiers. I'll investigate the broader issue.
Matt
3. Re: EuCOM: Migrating from Eu v3.1.1 To Eu v4.0.3
- Posted by Rad Jan 14, 2012
- 1215 views
Thanks Matt.
Including w32ole.ew within win32lib.ew settled the issue.
Thanks & Regards,
Rad.
