Accessing a COM component

5 Messages

andersoxie

Accessing a COM component

Reply Threaded

Hej

I am trying to access the Skype COM component. I started the Eiffel
Studio 6.2 EiffelCOM Wizard 2.0 and started to generate. It seemed
initially very promising but then I got some link errors, e.g.

wecom.lib(wecom_skype4comlib_callchannel.obj) : error LNK2001:
unresolved external symbol "public: void __thiscall
ecom_runtime_ce::free_memory_bstr(wchar_t *)" (?
free_memory_bstr@ecom_runtime_ce@@QAEXPA_W@Z)
driver.exe : fatal error LNK1120: 14 unresolved externals
NMAKE : fatal error U1077: '"C:\Program\Microsoft SDKs\Windows\v6.0
\\VC\Bin\link.EXE"' : return code '0x460'
Stop.

ERROR: Eiffel compilation failed

I have but the complete log at http://www.bsharp.se/skypeCOM.txt
since it is large.

Anyone that can give a hint about the reason for the failure.

Regards

Anders

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/eiffel_software/join
(Yahoo! ID required)

<*> To change settings via email:
mailto:eiffel_software-digest@...
mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

Iliyan Gochev

Re: Accessing a COM component

Reply Threaded

Hi Andres,

That most probably happens because you have Eiffel COM libs compiled with
earlier version of Visual Studio.
To rebuild them open a command prompt, navigate to
%ISE_EIFFEL/library/com/Clib and execute finish_freezing.exe --library.
Note that you have to do that for com/Clib_runtime too.

On my setup the command is like this:
D:\EiffelStudio6.2\library\com\Clib>..\..\..\studio\spec\windows\bin\finish_freezing.exe
--library

Best regards,
Iliyan Gochev

On Sun, Jul 13, 2008 at 4:25 PM, andersoxie <anders@...> wrote:

> Hej
>
> I am trying to access the Skype COM component. I started the Eiffel
> Studio 6.2 EiffelCOM Wizard 2.0 and started to generate. It seemed
> initially very promising but then I got some link errors, e.g.
>
> wecom.lib(wecom_skype4comlib_callchannel.obj) : error LNK2001:
> unresolved external symbol "public: void __thiscall
> ecom_runtime_ce::free_memory_bstr(wchar_t *)" (?
> free_memory_bstr@ecom_runtime_ce@@QAEXPA_W@Z)
> driver.exe : fatal error LNK1120: 14 unresolved externals
> NMAKE : fatal error U1077: '"C:\Program\Microsoft SDKs\Windows\v6.0
> \\VC\Bin\link.EXE"' : return code '0x460'
> Stop.
>
> ERROR: Eiffel compilation failed
>
> I have but the complete log at http://www.bsharp.se/skypeCOM.txt
> since it is large.
>
> Anyone that can give a hint about the reason for the failure.
>
> Regards
>
> Anders
>
>
>

[Non-text portions of this message have been removed]

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/eiffel_software/join
(Yahoo! ID required)

<*> To change settings via email:
mailto:eiffel_software-digest@...
mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

andersoxie

Re: Accessing a COM component

Reply Threaded

Hej

thanks, it worked after re-compiling the libs. I am now able to
access the COM-component but when I try to register an event
(callback from the COM-component) I get problems. It seems to
register the event in the COM-component but when the COM-component
fires the event I get an exception in the Eiffel program as follow:

Unknown routine (visible?): Developer exception. (DEVELOPER_EXCEPTION)
----------------------------------------------------------------------
---------
Class / Object Routine Nature of
exception Effect
----------------------------------------------------------------------
---------
ROOT_CLASS root's creation Unknown routine
(visible?):
<00000000031103E4> Developer
exception. Exit
----------------------------------------------------------------------
---------
ROOT_CLASS root's
creation
<00000000031103E4> Routine
failure. Exit
----------------------------------------------------------------------
---------

Call stack:

ObjectClassRoutine
------------------
[0x3B7A690] WEL_MSG cwin_dispatch_message ( @ 0 )
[0x3B7A690] WEL_MSG dispatch ( @ 1 )
[0x3B7A684] ROOT_CLASS message_loop (From WEL_APPLICATION) ( @ 37 )
[0x3B7A684] ROOT_CLASS run (From WEL_APPLICATION) ( @ 8 )
[0x3B7A684] ROOT_CLASS make (From WEL_APPLICATION) ( @ 7 )

I interpret the result as that the event reach the wel message loop
but it does not know where to send it.

Any ideas?

Regards

Anders

--- In eiffel_software@..., "Iliyan Gochev"
<iliyan.gochev@...> wrote:
>
> Hi Andres,
>
> That most probably happens because you have Eiffel COM libs
compiled with
> earlier version of Visual Studio.
> To rebuild them open a command prompt, navigate to
> %ISE_EIFFEL/library/com/Clib and execute finish_freezing.exe --
library.
> Note that you have to do that for com/Clib_runtime too.
>
> On my setup the command is like this:
> D:\EiffelStudio6.2
\library\com\Clib>..\..\..\studio\spec\windows\bin\finish_freezing.exe

> --library
>
> Best regards,
> Iliyan Gochev
>
> On Sun, Jul 13, 2008 at 4:25 PM, andersoxie <anders@...> wrote:
>
> > Hej
> >
> > I am trying to access the Skype COM component. I started the

Eiffel
> > Studio 6.2 EiffelCOM Wizard 2.0 and started to generate. It seemed
> > initially very promising but then I got some link errors, e.g.
> >
> > wecom.lib(wecom_skype4comlib_callchannel.obj) : error LNK2001:
> > unresolved external symbol "public: void __thiscall
> > ecom_runtime_ce::free_memory_bstr(wchar_t *)" (?
> > free_memory_bstr@ecom_runtime_ce@@QAEXPA_W@Z)
> > driver.exe : fatal error LNK1120: 14 unresolved externals
> > NMAKE : fatal error U1077: '"C:\Program\Microsoft
SDKs\Windows\v6.0

> > \\VC\Bin\link.EXE"' : return code '0x460'
> > Stop.
> >
> > ERROR: Eiffel compilation failed
> >
> > I have but the complete log at http://www.bsharp.se/skypeCOM.txt
> > since it is large.
> >
> > Anyone that can give a hint about the reason for the failure.
> >
> > Regards
> >
> > Anders
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/eiffel_software/join
(Yahoo! ID required)

<*> To change settings via email:
mailto:eiffel_software-digest@...
mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

Colin LeMahieu

Re: Accessing a COM component

Reply Threaded

There's a project configuration option called "visible" You'll need to
make sure the class or feature you're calling from the callback is
'visible'

--- In eiffel_software@..., "andersoxie" <anders@...> wrote:

>
> Hej
>
> thanks, it worked after re-compiling the libs. I am now able to
> access the COM-component but when I try to register an event
> (callback from the COM-component) I get problems. It seems to
> register the event in the COM-component but when the COM-component
> fires the event I get an exception in the Eiffel program as follow:
>
> Unknown routine (visible?): Developer exception. (DEVELOPER_EXCEPTION)
> ----------------------------------------------------------------------
> ---------
> Class / Object Routine Nature of
> exception Effect
> ----------------------------------------------------------------------
> ---------
> ROOT_CLASS root's creation Unknown routine
> (visible?):
> <00000000031103E4> Developer
> exception. Exit
> ----------------------------------------------------------------------
> ---------
> ROOT_CLASS root's
> creation
> <00000000031103E4> Routine
> failure. Exit
> ----------------------------------------------------------------------
> ---------
>
> Call stack:
>
> ObjectClassRoutine
> ------------------
> [0x3B7A690] WEL_MSG cwin_dispatch_message ( @ 0 )
> [0x3B7A690] WEL_MSG dispatch ( @ 1 )
> [0x3B7A684] ROOT_CLASS message_loop (From WEL_APPLICATION) ( @ 37 )
> [0x3B7A684] ROOT_CLASS run (From WEL_APPLICATION) ( @ 8 )
> [0x3B7A684] ROOT_CLASS make (From WEL_APPLICATION) ( @ 7 )
>
> I interpret the result as that the event reach the wel message loop
> but it does not know where to send it.
>
> Any ideas?
>
> Regards
>
> Anders
>
>
> --- In eiffel_software@..., "Iliyan Gochev"
> <iliyan.gochev@> wrote:
> >
> > Hi Andres,
> >
> > That most probably happens because you have Eiffel COM libs
> compiled with
> > earlier version of Visual Studio.
> > To rebuild them open a command prompt, navigate to
> > %ISE_EIFFEL/library/com/Clib and execute finish_freezing.exe --
> library.
> > Note that you have to do that for com/Clib_runtime too.
> >
> > On my setup the command is like this:
> > D:\EiffelStudio6.2
> \library\com\Clib>..\..\..\studio\spec\windows\bin\finish_freezing.exe
> > --library
> >
> > Best regards,
> > Iliyan Gochev
> >
> > On Sun, Jul 13, 2008 at 4:25 PM, andersoxie <anders@> wrote:
> >
> > > Hej
> > >
> > > I am trying to access the Skype COM component. I started the
> Eiffel
> > > Studio 6.2 EiffelCOM Wizard 2.0 and started to generate. It seemed
> > > initially very promising but then I got some link errors, e.g.
> > >
> > > wecom.lib(wecom_skype4comlib_callchannel.obj) : error LNK2001:
> > > unresolved external symbol "public: void __thiscall
> > > ecom_runtime_ce::free_memory_bstr(wchar_t *)" (?
> > > free_memory_bstr@ecom_runtime_ce@@QAEXPA_W@Z)
> > > driver.exe : fatal error LNK1120: 14 unresolved externals
> > > NMAKE : fatal error U1077: '"C:\Program\Microsoft
> SDKs\Windows\v6.0
> > > \\VC\Bin\link.EXE"' : return code '0x460'
> > > Stop.
> > >
> > > ERROR: Eiffel compilation failed
> > >
> > > I have but the complete log at http://www.bsharp.se/skypeCOM.txt
> > > since it is large.
> > >
> > > Anyone that can give a hint about the reason for the failure.
> > >
> > > Regards
> > >
> > > Anders
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

andersoxie

Re: Accessing a COM component

Reply Threaded

Hej

it worked, I am up and running with the COM-component.

Thanks,

Anders

--- In eiffel_software@..., "colinlema" <clemahieu@...>
wrote:
>
> There's a project configuration option called "visible" You'll need
to
> make sure the class or feature you're calling from the callback is
> 'visible'
>
> --- In eiffel_software@..., "andersoxie" <anders@>
wrote:
> >
> > Hej
> >
> > thanks, it worked after re-compiling the libs. I am now able to
> > access the COM-component but when I try to register an event
> > (callback from the COM-component) I get problems. It seems to
> > register the event in the COM-component but when the COM-
component
> > fires the event I get an exception in the Eiffel program as
follow:
> >
> > Unknown routine (visible?): Developer exception.
(DEVELOPER_EXCEPTION)
> > ------------------------------------------------------------------
----
> > ---------
> > Class / Object Routine Nature of
> > exception Effect
> > ------------------------------------------------------------------
----
> > ---------
> > ROOT_CLASS root's creation Unknown routine
> > (visible?):
> > <00000000031103E4> Developer
> > exception. Exit
> > ------------------------------------------------------------------
----
> > ---------
> > ROOT_CLASS root's
> > creation
> > <00000000031103E4> Routine
> > failure. Exit
> > ------------------------------------------------------------------
----
> > ---------
> >
> > Call stack:
> >
> > ObjectClassRoutine
> > ------------------
> > [0x3B7A690] WEL_MSG cwin_dispatch_message ( @ 0 )
> > [0x3B7A690] WEL_MSG dispatch ( @ 1 )
> > [0x3B7A684] ROOT_CLASS message_loop (From WEL_APPLICATION) ( @
37 )
> > [0x3B7A684] ROOT_CLASS run (From WEL_APPLICATION) ( @ 8 )
> > [0x3B7A684] ROOT_CLASS make (From WEL_APPLICATION) ( @ 7 )
> >
> > I interpret the result as that the event reach the wel message
loop

> > but it does not know where to send it.
> >
> > Any ideas?
> >
> > Regards
> >
> > Anders
> >
> >
> > --- In eiffel_software@..., "Iliyan Gochev"
> > <iliyan.gochev@> wrote:
> > >
> > > Hi Andres,
> > >
> > > That most probably happens because you have Eiffel COM libs
> > compiled with
> > > earlier version of Visual Studio.
> > > To rebuild them open a command prompt, navigate to
> > > %ISE_EIFFEL/library/com/Clib and execute finish_freezing.exe --
> > library.
> > > Note that you have to do that for com/Clib_runtime too.
> > >
> > > On my setup the command is like this:
> > > D:\EiffelStudio6.2
> >

\library\com\Clib>..\..\..\studio\spec\windows\bin\finish_freezing.exe

> > > --library
> > >
> > > Best regards,
> > > Iliyan Gochev
> > >
> > > On Sun, Jul 13, 2008 at 4:25 PM, andersoxie <anders@> wrote:
> > >
> > > > Hej
> > > >
> > > > I am trying to access the Skype COM component. I started the
> > Eiffel
> > > > Studio 6.2 EiffelCOM Wizard 2.0 and started to generate. It

seemed

> > > > initially very promising but then I got some link errors, e.g.
> > > >
> > > > wecom.lib(wecom_skype4comlib_callchannel.obj) : error LNK2001:
> > > > unresolved external symbol "public: void __thiscall
> > > > ecom_runtime_ce::free_memory_bstr(wchar_t *)" (?
> > > > free_memory_bstr@ecom_runtime_ce@@QAEXPA_W@Z)
> > > > driver.exe : fatal error LNK1120: 14 unresolved externals
> > > > NMAKE : fatal error U1077: '"C:\Program\Microsoft
> > SDKs\Windows\v6.0
> > > > \\VC\Bin\link.EXE"' : return code '0x460'
> > > > Stop.
> > > >
> > > > ERROR: Eiffel compilation failed
> > > >
> > > > I have but the complete log at

http://www.bsharp.se/skypeCOM.txt

> > > > since it is large.
> > > >
> > > > Anyone that can give a hint about the reason for the failure.
> > > >
> > > > Regards
> > > >
> > > > Anders
> > > >
> > > >
> > > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>