Winelib and MFC and mixing native Windows DLLs

[Raghavan Gurumurthy]

I am trying to build my MFC-based Windows application on Linux.

First question - I read in the Winelib user guide that I have to build MFC
completely on Winelib as well. Is this really a must? Is there no other
alternative?

Second question - If my Windows application uses 10 DLLs, do I have to build
all these 10 DLLs in addition to the executable on Winelib? Or can I leave
the 10 DLLs run in 'native' mode and only convert the executable to be built
with Winelib?

Thanks in advance,
Raghavan

[Tim Hentenaar]

On Thu, 13 May 2004 09:37:04 -0700
Raghavan Gurumurthy  wrote:
> I am trying to build my MFC-based Windows application on Linux.
>
> First question - I read in the Winelib user guide that I have to build MFC completely on Winelib as well. Is this really a must? Is there no other alternative?

I believe you'd have to build MFC on Winelib.
> Second question - If my Windows application uses 10 DLLs, do I have to build all these 10 DLLs in addition to the executable on Winelib? Or can I leave the 10 DLLs run in 'native' mode and only convert the executable to be built with Winelib?

You should be able to leave them in 'native' mode.

Tim

[Shachar Shemesh]

Raghavan Gurumurthy wrote:
> Second question - If my Windows application uses 10 DLLs, do I have to 
> build all these 10 DLLs in addition to the executable on Winelib? Or 
> can I leave the 10 DLLs run in 'native' mode and only convert the 
> executable to be built with Winelib?

I think that depends on whether the functions exported from the DLL are 
exported using "dllexport", or using a "def" file. More to the point, it 
depends on whether these have a C++ name mangeling, or whether they are 
C functions.

If the later, you should be able to leave them as PE DLLs. If the 
former, you are likely to not be able to link with them any more.

Shachar