[vwnc] Using an SDK with VW

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

On Feb 28, 2008, at 8:51 PM, Ajaya Ghosh wrote:

> Hi list,
>         I would like to have some guidelines for using an external  
> SDK with VW.
>         It is supplied with two .dll files from which it is indented  
> to trigger the api calls.The problem that I am facing is that the  
> supplied dll files have no header files supplied,         so I am  
> not able to use the ExternalInterface builder tool.
>         I would like to other optional ways to integrate an  
> ExternalInterface class with api functions.

Do you have documentation on the APIs at least? Most platforms have  
some sort of objdump thing that will let you extract the names of the  
exported ordinals, but without docs, you're left guessing as to what  
their arguments are, plus their return values.

--
Travis Griggs
Objologist
What's next, Intel Processors branded with "Apple Outside" stickers?


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Ajaya Ghosh wrote:
> Hi list,
>         I would like to have some guidelines for using an external SDK
> with VW.
>         It is supplied with two .dll files from which it is indented
> to trigger the api calls.The problem that I am facing is that the
> supplied dll files have no header files supplied,         so I am not
> able to use the ExternalInterface builder tool.
>         I would like to other optional ways to integrate an
> ExternalInterface class with api functions.
The interface builder tool has several issues that can make it unwieldy
to use, so a lot of people don't use it and define their
ExternalInterface methods manually. As long as you know the type info of
the API calls you can go right ahead and implement your
ExternalInterface methods manually.


Two warnings:

-If your smalltalk side function or type definitions reference a type
that has not been declared yet the system will not complain, instead it
will silently add a definition for the missing type as a void* .

-There are some issues with loading packages from Store that contain an
external interface, a workaround is to define a postLoadBlock on the
package that recompiles all methods of the external interface after the
package  has been loaded.



Success!

Reinout
-------

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc