RE: [VB4Linux-Dev] (no subject)

[Scott B. <js...@go...>]

What would have to happen if you want this to really work is:

1 - Use Wine or some other api layer to use the Windows OCX/DLL bins.
    This would stick you pretty much into a Intel hole.  *You*
    could write a 386/486/Pentium emu to dig you out of this, but that
    adds a lot to the project.

2 - Support only OCX'x/DLL's that can be recompiled with the VB4LNX 
    system.  
    This does limit you on some things, but it keeps you more portable,
    and makes the code a lot less to deal with.

3 - Wine support and OCX/DLL recompiles. (A little of 1 & 2)
    This solves the most problems, and keeps the code to a minimum.

I think 3 is the KISS choice.  Just a thought or two...

scott

On Tue, 21 Nov 2000, Abhijit Paithankar wrote:

> how portable is it?
> and if it is portable executable, it should be in binary format....which
> means it is readily usable !
> 
> 
> > > ya...Linux versions of VB OCX or DLLs would be good...
> > > any idea of what exactly an OCX is...I mean...fileformat information?
> > >
> >
> > PE (Portable executable) I think.
> >
> 
> _______________________________________________
> VB4Linux-Dev mailing list
> VB4...@li...
> http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev
> 
>