I will share all my source & make environment, including .diff patches
to ATL/WTL/MFC so any wtl mfc activex project should compile. I intend
to supply example projects for MFC GUI and ODBC, WTL apps and ATL com
controls all compiled with winelib on Linux. I will show how to compile
the C runt
On Mon, 22 Sep 2003, Boaz Harrosh wrote:
> I must confess I am using a 2 month old wine but ...
>
> from wininet.dll:
>Gopher[*]
>InternetErrorDlg
>InternetSetFilePointer
>
> from rasapi32.dll
> RasSetEntryDialParamsA/W
> IsAsyncMoniker
> RasGetErrorStringA
> RasDialA
> Ras
Hi Boaz,
Some of InternetErrorDlg is implemented in the latest version of Wine.
Mike
Boaz Harrosh wrote:
I must confess I am using a 2 month old wine but ...
from wininet.dll:
Gopher[*]
InternetErrorDlg
InternetSetFilePointer
I must confess I am using a 2 month old wine but ...
from wininet.dll:
Gopher[*]
InternetErrorDlg
InternetSetFilePointer
from rasapi32.dll
RasSetEntryDialParamsA/W
IsAsyncMoniker
RasGetErrorStringA
RasDialA
RasGetConnectStatusA
CreateAsyncBindCtx - this one is actually there only it is
On Mon, 22 Sep 2003, Boaz Harrosh wrote:
> Winebuild would not recognize stubs for linking. So an app that runs
> under wine will not compile under winelib. ( stubbed functions are
> linked to but are not actually used).
You'd have to provide manually written stubs. What functions are you
missi
Le lun 22/09/2003 à 10:30, Boaz Harrosh a écrit :
> Winebuild would not recognize stubs for linking. So an app that runs
> under wine will not compile under winelib. ( stubbed functions are
> linked to but are not actually used).
If it's a "real" stub (ie, one in the spec file), then the app won
Winebuild would not recognize stubs for linking. So an app that runs
under wine will not compile under winelib. ( stubbed functions are
linked to but are not actually used).
[Q] What should one do with all these stub functions? redefine them in a
separate file? would it make any logic to tell w
