question on how to do language bindings to MSHTML's COM interface

Luke Kenneth Casson Leighton lkcl at lkcl.net
Sat Jan 3 14:15:03 CST 2009


> There are a number of parts to your question:
> 1. Is it OK for the application to be a winelib one (i.e. invoked via
> or linked to wine, rather than being "native")?

i'm on the first step - getting python compiled. so i'm in the middle
of an experiment to compile python with wine, and it looks like i
_have_ to make it an "invoked via wine" one.  in fact, stunningly,
that actually succeeded!  using winegcc, a script called python and a
dll called python.exe.so were created.  of course, make install only
copied over the script not the .so duh.

the mistake i've made however is in not compiling with -DMS_WINDOWS.
the issue that i have is that there _is_ no Makefile or Makefile.in
for win32 python, there _is_ no configure script: it's all damn well
done with visual studio .proj files on a hard-coded basis argh.

i had the same difficulty i ran into when cross-compiling with a
mingw32 cross-compiler.

anyway - the first step is going reasonably well.  i'm running into a
bit of bother with python modules (.so extension) - i'll have to
investigate the .proj files a bit more because the only things being
built are _winreg.o, _md5.o and _not_ _winreg.so or _winreg.dll or
wine equivalent.  whoops.

but - this is the first step.  the next step would be to, i assume,
add mshtml as a module?  or perhaps see if someone's already done it,
somewhere, with windows.



More information about the wine-devel mailing list