Hi Luc, I know of no issues (other than that this would restrict you to running on x86, but perhaps that's not an issue for you). I don't think anyone's done it before, but I could be wrong.
Incidentally, if you're sticking with x86 only, you should consider just shipping your Windows .exe unchanged, and using Wine instead of Winelib. It works just as well, and it's a lot easier. That's what was done for Picasa. If you haven't already seen it, you might want to look at my Wine for Windows ISVs page, http://kegel.com/wine/isv I expect you'll run into some issues when testing your Windows executable on Linux with Wine. When you do, I'd be glad to try to help resolve them (though I might need you to send me a copy of the software so I can reproduce the trouble locally). - Dan On 7/19/06, Luc-Eric Rousseau <[EMAIL PROTECTED]> wrote:
thanks. Are there any known issue with the native microsoft WSH (Windows Scripting Host)DLL under wine? Has this this been done with a WineLib app in the past? > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > 2) one application we'd like to port uses active scripting > (VBScript). Basically we wrote some features in VBScript, > which in turn automating our application (like macros in > Photoshop CS). What would be our options for this if we were > to use WinLib? (MainWin ships with VBscript and JScript) > > Wine doesn't currently support VBScript (unless you install > WSH from Microsoft). > That could be added, but it'd be a substantial effort.
--
