On Fri, Jun 12, 2009 at 8:39 AM, xexaxo<wineforum-user@xxxxxxxxxx> wrote: > So I have the following questions about he structure of wine, and the implementation it on the different platforms/architectures. > > 1. During compile winelib and all ( or selected ) modules of wine ( ie dll ) are made in native target linux ( in mine case ppc32 ) binaries/libraries. Yes. > 2. During the first run of wine a ~/.wine/ folder is created with all the *.reg and *inf files. Now correct me if I'm wrong wine calls winebuild to compile/convert the existing *.dll.so files by making them a Win PE32. Making a Win PE header file with all the necessary EXPORT and IMPORT functions but the EXPORT functions are actually implemented in a native way ( common on the platform and CPU architecture ) No...they're ELF binaries, not PE. > 3. After the creation of .wine directory the program can be loaded and executed. All the IMPORT functions are handled properly but is there any "conversion" between the different architectures. Meaning does the parameters passed to the library are handled in a ASM or in any higher programing language. No, there is no conversion. Which is why wine on the PPC isn't very useful, since it can't run Win32 applications, unless you wrap it with a CPU emulator, like the old Darwine project used to do. -- -Austin
