easyloading.netlify.com

1. This tab allows you to specify the behavior of different DLLs and override the possible defaults. To get DirectX running, you will need a long list of DLLs listed. The first step is to click on the New override dropdown box icon and expand the list. Search for the d3d8 DLL. Once found, click Add.
2. With that in mind, once you've copied the DLL you just need to tell Wine to try to use it. You can configure Wine to choose between native and builtin DLLs at two different levels. If you have Default Settings selected in the Applications tab, the changes you make will affect all applications. Or, you can override the global settings on a per-application level by adding and selecting an application in the Applications tab.

1. Wine Dll Override
2. Wine Windows Version
3. Wine Setup
4. Linux Mint Wine

But if using winecfg to set an application-specific DLL override for HitFilm, then it is also necessary to set another application-specific override for HitFilmRenderClient. Still haven't found a way to get activation to work in Wine yet though.

Authors: Wilbur Dale; Francois Gouget; André Hentschel; John Sheets

• 1Winelib Introduction
  • 1.3Getting Started
• 2Portability issues
• 3The Winelib development toolkit
  • 3.1Winemaker
  • 3.3The Spec file
• 4Dealing with the MFC
• 5Building Winelib DLLs

1 Winelib Introduction

1.1 What is Winelib?

Winelib is a development toolkit which allows you to compile your Windows applications on Unix.

Most of Winelib code consists of the Win32 API implementation. Fortunately this part is 100 percent shared with Wine. The remainder consists of Windows compatible headers and tools like the resource compiler (and even these are used when compiling Wine).

Thanks to the above, Winelib supports most C and C++ source code, resource and message files, and can generate graphical or console applications as well as dynamic libraries.

What is not supported is 16-bit source code as the types it depends on (especially segmented pointers) are not supported by Unix compilers. Also missing are some of the more exotic features of Microsoft compilers like native COM support and structured exception handling. So you may need to perform some modifications in your code when recompiling your application with Winelib. This guide is here to help you in this task.

What you gain by recompiling your application with Winelib is the ability to make calls to Unix APIs, directly from your Windows source code. This allows for a better integration with the Unix environment than is allowed by running an unmodified Windows application running in Wine. Another benefit is that a Winelib application can relatively easily be recompiled on a non-Intel architecture and run there without the need for a slow software emulation of the processor.

1.2 System requirements

The requirements for Winelib are similar to those for Wine.

Basically if you can run Wine on your computer then you can run Winelib. But the converse is not true. You can also build Winelib and Winelib applications on platforms not supported by Wine, typically platforms with a non i386 processor. But this is still pretty much uncharted territory. It would be more reasonable to target one of the more mundane i386-based platforms first.

The main difference is that the compiler becomes much more important. It is highly recommended that you use gcc, g++, and the GNU binutils. The more recent your gcc compiler the better. For any serious amount of code you should not consider anything older than gcc 2.95.2. The latest gcc snapshots contain some useful bug fixes and much better support for anonymous structs and unions. This can help reduce the number of changes you have to do in your code but these are not stable releases of the compiler so you may not want to use them in production.

1.3 Getting Started

1.3.1 Winemaker introduction

So what is needed to compile a Windows application with Winelib? Well, it really depends on the complexity of your application but here are some issues that are shared by all applications:

• the case of your files may be bad. For example they could be in all caps: HELLO.C. It's not very nice to work with and probably not what you intended.
• then the case of the filenames in your include statements may be wrong: maybe they include Windows.h instead of windows.h.
• your include statements may use ' instead of '/'. ' is not recognized by Unix compilers while '/' is recognized in both environments.
• you will need to perform the usual DOS to Unix text file conversion otherwise you'll get in trouble when the compiler considers that your ' is not at the end of the line since it is followed by a pesky carriage return.
• you will have to write new makefiles.

The best way to take care of all these issues is to use winemaker.

winemaker is a Perl script which is designed to help you bootstrap the conversion of your Windows projects to Winelib. In order to do this it will go analyze your code, fixing the issues listed above and generate straight Makefiles.

Let's suppose that you are already in the top directory of your sources. Then converting your project to Winelib may be as simple as just running the two commands below (note the dot indicating current directory at the end of the first command):

But of course things are not always that simple, which is why we have this guide at all.

1.3.2 Test Drive

Before starting to work on a big project you may want to try to port a small application. The notepad application from the Wine source tree suits well for testing purposes. It can be found in the programs subdirectory. notepad is a simple application, but has a few C, header and resource files.

Run make clean in the notepad source directory if it contains results of previous builds. Create a separate directory with name notepad2, so it won't conflict with the Wine copy of the application. Copy the sources of notepad (*.c, *.h, and *.rc files) to this directory. Now run the commands mentioned above from the notepad2 directory:

Notice how it fails linking, because of undefined reference to wnsprintfW. This is because we didn't specify the libraries we need to link to. Normally you know which libraries you need or you can find a list in your old Makefile or project file.

To fix that problem, open notepad2/Makefile.in in a text editor and search for an assignment to a variable with IMPORTS as part of its name. There will be a list of import libraries. Now run winemaker again, but with these libraries prefixed by -i:

You are done! Now you can start the application as wine notepad2.exe.so or ./notepad2.exe.

If you come across problems preparing and building this application this probably means that winemaker utility is broken by some changes in Wine. Try asking for help on wine-devel@winehq.org.

1.3.3 Step by step guide

Let's retrace the steps above in more details.

Getting the source

First you should try to get the sources together with the executables/libraries that they build. If you have no Visual C++ project files available winemaker having these around can help it guess what it is that your project is trying to build. Otherwise, it is able to understand Visual C++ projects. Usually the executables and libraries are in a Release or Debug subdirectory of the directory where the sources are. So it's best if you can transfer the source files and either of these directories to Linux. Note that you don't need to transfer the .obj, .pch, .sbr and other files that also reside in these directories; especially as they tend to be quite big.

cd root_dirThen go to the root directory where are your source files. winemaker can deal with a whole directory hierarchy at once so you don't need to go into a leaf directory, quite the contrary. winemaker will automatically generate makefiles in each directory where one is required, and will generate a global makefile so that you can rebuild all your executables and libraries with a single make command.

Making the source writable

Then make sure you have write access to your sources. It may sound obvious, but if you copied your source files from a CD-ROM or if they are in Source Safe on Windows, chances are that they will be read-only. But winemaker needs write access so that it can fix them. You can arrange that by running “chmod -R u+w .”. Also you will want to make sure that you have a backup copy of your sources in case something went horribly wrong, or more likely, just for reference at a later point. If you use a version control system you're already covered.

If you have already modified your source files and you want to make sure that winemaker will not make further changes to them then you can use the --nosource-fix option to protect them.

Running winemaker

Then you'll run winemaker.. Here are the options you will most likely want to use. For a complete list of options see the man page.

--lower-uppercase; --lower-all

These options specify how to deal with files, and directories, that have an 'incorrect' case. --lower-uppercase specifies they should only be renamed if their name is all uppercase. So files that have a mixed case, like Hello.c would not be renamed. --lower-all will rename any file. If neither is specified then no file or directory will be renamed, almost. As you will see later, winemaker may still have to rename some files.

--nobackup

Winemaker normally makes a backup of all the files in which it does more than the standard DOS to Unix conversion. But if you already have (handy) copies of these files elsewhere you may not need these so you should use this option.

--dll; --console

These options lets winemaker know what kind of target you are building. If you have the windows library in your source hierarchy then you should not need to specify --dll. But if you have console executables then you will need to use the corresponding option.

--mfc

This option tells winemaker that you are building an MFC application/library.

-Dmacro=defn; -Idir; -Ldir; -idll; -llibrary

The -i specifies a Winelib library to import via the spec file mechanism. Contrast this with the -l which specifies a Unix library to link with. The other options work the same way they would with a C compiler. All are applied to all the targets found. When specifying a directory with either -I or -L, winemaker will prefix a relative path with $(TOPDIRECTORY)/ so that it is valid from any of the source directories. You can also use a variable in the path yourself if you wish (but don't forget to escape the '$'). For instance you could specify -I$(WINELIB_INCLUDE_ROOT)/msvcrt.

So your command may finally look like:

When you execute winemaker it will first rename files to bring their character case in line with your expectations and so that they can be processed by the makefiles. This later category implies that files with a non lowercase extension will be renamed so that the extension is in lowercase. So, for instance, HELLO.C will be renamed to HELLO.c. Also if a file or directory name contains a space or a dollar, then this character will be replaced with an underscore. This is because these characters cause problems with current versions of autoconf (2.13) and make (3.79).

Source modifications and makefile generation

winemaker will then proceed to modify the source files so that they will compile more readily with Winelib. As it does so it may print warnings when it has to make a guess or identifies a construct that it cannot correct. Finally it will generate the makefiles. Once all this is done you can review the changes that winemaker did to your files by using diff -uw. For instance: diff -uw hello.c.bak hello.c

Running make

This is a pretty simple step: just type make and voila, you should have all your executables and libraries. If this did not work out, then it means that you will have to read this guide further to:

• review the Makefile files to adjust what winemaker thinks are the binaries you are trying to build and which sources should be used for each. See the Winemaker source analysis section for some hints.
• fix the portability issues in your sources. See Portability issues for more details.

2 Portability issues

2.1 Unicode

The wchar_t type has different standard sizes in Unix (4 bytes) and Windows (2 bytes). You need a recent gcc version (2.9.7 or later) that supports the -fshort-wchar option to set the size of wchar_t to the one expected by Windows applications.

If you are using Unicode and you want to be able to use standard library calls (e.g. wcslen, wsprintf), then you must use the msvcrt runtime library instead of glibc. The functions in glibc will not work correctly with 16-bit strings.

2.2 C library

There are two choices available to you regarding which C library to use: the native glibc C library or the msvcrt C library.

Note that under Wine, the crtdll library is implemented using msvcrt, so there is no benefit in trying to use it.

Using glibc in general has the lowest overhead, but this is really only important for file I/O, as many of the functions in msvcrt are simply resolved to glibc.

To use glibc, you don't need to make changes to your application; it should work straight away. There are a few situations in which using glibc is not possible:

1. Your application uses Win32 and C library unicode functions.
2. Your application uses MS specific calls like beginthread(), loadlibrary(), etc.
3. You rely on the precise semantics of the calls, for example, returning -1 rather than non-zero. More likely, your application will rely on calls like fopen() taking a Windows path rather than a Unix one.

In these cases you should use msvcrt to provide your C runtime calls.

Add -mno-cygwin to your compiler flags. This will cause winebuild to resolve your C library calls to msvcrt.dll.

2.3 Compiling Problems

If you get undefined references to Win32 API calls when building your application: if you have a VC++ .dsp file, check it for all the .lib files it imports, and add them to your applications .spec file. winebuild gives you a warning for unused imports so you can delete the ones you don't need later. Failing that, just import all the DLLs you can find in the dlls/ directory of the Wine source tree.

If you are missing GUIDs at the link stage, add -luuid to the link line.

gcc is more strict than VC++, especially when compiling C++. This may require you to add casts to your C++ to prevent overloading ambiguities between similar types (such as two overloads that take int and char respectively).

If you come across a difference between Windows and Wine headers that breaks compilation, try asking for help on wine-devel@winehq.org.

2.4 Improving Performance

By default, the makefiles created by winemaker may pass the -fpic flag to the compiler, which is the right thing to do for most target files, particularly DLLs. However, this option adds a good deal of overhead and isn't necessary for your 'main' executable. You can disable this for the main executable (and only do it for the main executable) by passing the -fno-pic -fno-PIC compiler flags, either in the appropriate makefile rule or a direct compiler command.

Another simple thing you can do to get the best performance from your Winelib app is use a recent version of your compiler. You may be surprised how much of a difference a new compiler release's optimizations and improvements can make.

3 The Winelib development toolkit

3.1 Winemaker

3.1.1 Support for Visual C++ projects

Winemaker supports the Visual C++ project files! Supported filetypes are .dsp, .dsw, .vcproj and .sln. It detects the defines to be used, any custom include path, the list of libraries to link with, and exactly which source files to use to build a specific target.

It is recommended to use Winemaker with a project file if available. If you have to choose between a .dsp file and a .vcproj, then you should use the .dsp, because it offers more information.

The usage is very easy, just replace the path to the source folder with the path to the project file.

3.1.2 Winemaker source analysis

Winemaker can do its work even without a Windows makefile or a Visual Studio project to start from (it would not know what to do with a windows makefile anyway). This involves doing many educated guesses which may be wrong. But by and large it works. The purpose of this section is to describe in more details how winemaker proceeds so that you can better understand why it gets things wrong and how to fix it/avoid it.

At the core winemaker does a recursive traversal of your source tree looking for targets (things to build) and source files. Let's start with the targets.

First are executables and DLLs. Each time it finds one of these in a directory, winemaker puts it in the list of things to build and will later generate a Makefile in this directory. Note that Winemaker also knows about the commonly used Release and Debug directories, so it will attribute the executables and libraries found in these to their parent directory. When it finds an executable or a DLL winemaker is happy because these give it more information than the other cases described below.

If it does not find any executable or DLL winemaker will look for files with a .mak extension. If they are not disguised Visual C++ projects (and currently even if they are), winemaker will assume that a target by that name should be built in this directory. But it will not know whether this target is an executable or a library. So it will assume it is of the default type, i.e. a graphical application, which you can override by using the --cuiexe and --dll options.

Finally winemaker will check to see if there is a file called makefile. If there is, then it will assume that there is exactly one target to build for this directory. But it will not know the name or type of this target. For the type it will do as in the above case. And for the name it will use the directory's name. Actually, if the directory starts with src, winemaker will try to make use of the name of the parent directory instead.

Once the target list for a directory has been established, it will check whether it contains a mix of executables and libraries. If it is so, then it will make it so that each executable is linked with all the libraries of that directory.

If the previous two steps don't produce the expected results (or you think they will not) then you should put winemaker in interactive mode. This will allow you to specify the target list (and more) for each directory.

In each directory winemaker also looks for source files: C, C++ or resource files. If it also found targets to build in this directory it will then try to assign each source file to one of these targets based on their names. Source files that do not seem to match any specific target are put in a global list for this directory, see the EXTRA_xxx variables in the Makefile, and linked with each of the targets. The assumption here is that these source files contain common code which is shared by all the targets. If no targets were found in the directory where these files are located, then they are assigned to the parent's directory. So if a target is found in the parent directory it will also 'inherit' the source files found in its subdirectories.

Finally winemaker also looks for more exotic files like .h headers, .inl files containing inline functions and a few others. These are not put in the regular source file lists since they are not compiled directly. But it will still remember them so that they are processed when the time comes to fix the source files.

Fixing the source files is done as soon as the recursive directory traversal is completed. The two main tasks in this step are fixing the CRLF issues and verifying the case of the include statements.

winemaker makes a backup of each source file (in such a way that symbolic links are preserved), then reads it fixing the CRLF issues and the other issues as it goes. Once it has finished working on a file it checks whether it has done any non CRLF-related modification and deletes the backup file if it did not (or if you used --nobackup).

Checking the case of the include statements (of any form, including files referenced by resource files), is done in the context of that source file's project. This way winemaker can use the proper include path when looking for the file that is included. If winemaker fails to find a file in any of the directories of the include path, it will rename it to lowercase on the basis that it is most likely a system header and that all system headers names are lowercase (this can be overridden by using --nolower-include).

Finally winemaker generates the Makefile files. From the above description you can guess at the items that it may get wrong in this phase: macro definitions, include path, DLL path, DLLs to import, library path, libraries to link with. You can deal with these issues by using winemaker -D, -P, -i, -I, -L and -l options if they are homogeneous enough between all your targets. Otherwise you may want to use winemaker interactive mode so that you can specify different settings for each project / target.

For instance, one of the problems you are likely to encounter is that of the STRICT macro. Some programs will not compile if STRICT is not turned on, and others will not compile if it is. Fortunately all the files in a given source tree use the same setting so that all you have to do is add -DSTRICT on winemaker command line or in the Makefile file(s).

Finally the most likely reasons for missing or duplicate symbols are:

• The target is not importing the right set of DLLs, or is not being linked with the right set of libraries. You can avoid this by using winemaker -P, -i, -L and -l options or adding these DLLs and libraries to the Makefile.
• Maybe you have multiple targets in a single directory and winemaker guessed wrong when trying to match the source files with the targets. The only way to fix this kind of problem is to edit the Makefile file manually.
• Winemaker assumes you have organized your source files hierarchically. If a target uses source files that are in a sibling directory, e.g. if you link with ./hello/world.o then you will get missing symbols. Again the only solution is to manually edit the Makefile file.

3.1.3 The interactive mode

The interactive mode will ask you to confirm or change options while winemaker analyzes your code. This might be useful when compiling MFC or in case you need different settings for each project / target. You should consider adding more options to the following example:

3.1.4 The Makefile files

The Makefile is your makefile. So this is the file to modify if you want to customize things. Here's a detailed description of its content:

This is where the targets for this directory are listed. The names are pretty self-explanatory. SUBDIRS is usually only present in the top-level makefile. For libraries and executables, specify the full name, including the .dll, .a or .exe extension. Note that these names must be in all lowercase.

This section contains the global compilation settings: they apply to all the targets in this makefile. The LIBRARIES variable allows you to specify additional Unix libraries to link with. Note that you would normally not specify Winelib libraries there. To link with a Winelib library, one uses DLL_IMPORTS. The exception is for C++ libraries where you currently don't have a choice but to link with them in the Unix sense. One library you are likely to find here is mfc.

The other variable names should be self-explanatory. There are also CEXTRA, CXXEXTRA and RCEXTRA which allow you to specify additional flags for, respectively, the C compiler, the C++ compiler and the resource compiler. Finally note that all these variables contain the option's name.

Then there is one section per target, each describing the various components that target is made of.

The above variables list the sources that are used to generate the target. Each section will start with a comment indicating the name of the target. Then come a series of variables prefixed with the name of that target. Note that the name of the prefix may be slightly different from that of the target because of restrictions on the variable names.

The above variables specify how to link the target. Note that they add to the global settings we saw at the beginning of this file.

The DLLS field is where you would enumerate the list of DLLs that executable imports. It should contain the full DLL name, but not the -l option.

The above just builds a list of all the object files that correspond to this target. This list is later used for the link command.

This section builds “summary” lists of source files.

The above first defines the default target for this makefile. Here it consists in trying to build all the targets.

Then come additional directives to link the executables and libraries. These are pretty much standard and you should not need to modify them.

3.2 Compiling resource files: wrc

To compile resources you should use the Wine Resource Compiler, wrc for short, which produces a binary .res file. This resource file is then used by winebuild when compiling the spec file (see The Spec file).

Again the makefiles generated by winemaker take care of this for you. But if you were to write your own makefile you would put something like the following:

There are two issues you are likely to encounter with resource files.

The first problem is with the C library headers. wrc does not know where these headers are located. So if an RC file, of a file it includes, references such a header you will get a 'file not found' error. Here are a few ways to deal with this:

• The solution traditionally used by the Winelib headers is to enclose the offending include statement in an #ifndef RC_INVOKED statement where RC_INVOKED is a macro name which is automatically defined by wrc.

• Alternately you can add one or more -I directive to your wrc command so that it finds you system files. For instance you may add -I/usr/include -I/usr/lib/gcc-lib/i386-linux/2.95.2/include to cater to both C and C++ headers. But this supposes that you know where these header files reside which decreases the portability of your makefiles to other platforms.

  Or you could use the C/C++ compiler to perform the preprocessing. To do so, simply modify your makefile as follows:

The second problem is that the headers may contain constructs that wrc fails to understand. A typical example is a function which return a const type. wrc expects a function to be two identifiers followed by an opening parenthesis. With the const this is three identifiers followed by a parenthesis and thus wrc is confused (note: it should in fact ignore all this like the windows resource compiler does). The current work-around is to enclose offending statement(s) in a #ifndef RC_INVOKED.

Using GIF files in resources is problematic. For best results, convert them to BMP and change your .res file.

If you use common controls/dialogs in your resource files, you will need to add #include <commctrl.h> after the #include <windows.h> line, so that wrc knows the values of control specific flags.

3.3 The Spec file

3.3.1 Introduction

In Windows, applications and libraries contain some information which are necessary to make APIs such as GetProcAddress work. So it is necessary to duplicate these data structures in the Unix world to make these same APIs work with Winelib applications and libraries.

Ck2 how to change religion. The spec file is there to solve the semantic gap described above. It provides information about each API exported from a DLL so that the appropriate tables can be generated. Further the information is used to for better relay logging.

A typical spec file will look something like this:

3.3.2 More details

Here is a more detailed description of the spec file format.

Anything after a '#' will be ignored as comments.

This field can be present zero or more times. Each instance defines a function entry point. The prototype defined by EXPORTNAME ([ARGTYPE [ARGTYPE [..]]]) specifies the name available for dynamic linking and the format of the arguments. ORDINAL is replaced by the ordinal number corresponding to the function, or @ for automatic ordinal allocation (Win32 only).

FUNCTYPE should be one of:

pascal

for a Win16 function

stdcall

for a normal Win32 function

cdecl

for a Win32 function using the C calling convention

varargs

for a Win32 function taking a variable number of arguments

thiscall

for a Win32 function using the C++ calling convention

ARGTYPE should be one of:

word

for a 16-bit word

s_word

for a 16-bit signed word

segptr

for a segmented pointer

segstr

for a segmented pointer to a null-terminated string

long

a 32-bit value

ptr

for a linear pointer

str

for a linear pointer to a null-terminated string

wstr

for a linear pointer to a null-terminated wide (16-bit Unicode) string

int64

a 64-bit value

int128

a 128-bit value

float

a 32-bit floating-point value

double

a 64-bit floating-point value

For Win32 functions word, s_word, segptr and segstr are not valid. HANDLERNAME is the name of the actual Wine function that will process the request in 32-bit mode.

Strings should almost always map to str, wide strings to wstr. As the general rule it depends on whether the parameter is IN, OUT or IN/OUT.

• IN: str/wstr
• OUT: ptr
• IN/OUT: str/wstr

It is for debug messages. If the parameter is OUT it might not be initialized and thus it should not be printed as a string.

To declare a function using a variable number of arguments in Win16, specify the function as taking no arguments. The arguments are then available with CURRENT_STACK16->args. In Win32, specify the function as varargs and declare it with a “..” parameter in the C file. See the wsprintf* functions in user.spec and user32.spec for an example.

This field can be present zero or more times. Each instance defines a stub function. It makes the ordinal available for dynamic linking, but will terminate execution with an error message if the function is ever called.

This field can be present zero or more times. Each instance defines an entry that simply maps to a Wine symbol (variable or function); EXPORTNAME</cottde> will point to the symbol SYMBOLNAME that must be defined in C code. This type only works with Win32.

Note: FIXME:The following is not up-to-date.

To link an executable you need to link together: your object files, any Windows libraries that your application depends on, gdi32 for instance, and any additional library that you use. All the libraries you link with should be available as .so libraries. If one of them is available only in .dll form then consult Building Winelib DLLs.

It is also when attempting to link your executable that you will discover whether you have missing symbols or not in your custom libraries. On Windows when you build a library, the linker will immediately tell you if a symbol it is supposed to export is undefined. In Unix, and in Winelib, this is not the case. The symbol will silently be marked as undefined and it is only when you try to produce an executable that the linker will verify all the symbols are accounted for.

So before declaring victory when first converting a library to Winelib, you should first try to link it to an executable (but you would have done that to test it anyway, right?). At this point you may discover some undefined symbols that you thought were implemented by the library. Then, you go to the library sources and fix it. But you may also discover that the missing symbols are defined in, say, gdi32. This is because you did not link the said library with gdi32. One way to fix it is to link this executable, and any other that also uses your library, with gdi32. But it is better to go back to your library makefile and explicitly link it with gdi32.

As you will quickly notice, this has unfortunately not been (completely) done for Winelib own libraries. So if an application must link with ole32, you will also need to link with advapi32, rpcrt4 and others even if you don't use them directly. This can be annoying and hopefully will be fixed soon (feel free to submit a patch).

4 Dealing with the MFC

To use the MFC in a Winelib application you will first have to recompile the MFC with Winelib. In theory it should be possible to write a wrapper for the Windows MFC as described in Building Winelib DLLs. But in practice it does not seem to be a realistic approach for the MFC:

• the huge number of APIs makes writing the wrapper a big task in itself.
• furthermore the MFC contain a huge number of APIs which are tricky to deal with when making a wrapper.
• even once you have written the wrapper you will need to modify the MFC headers so that the compiler does not choke on them.
• a big part of the MFC code is actually in your application in the form of macros. This means even more of the MFC headers have to actually work to in order for you to be able to compile an MFC based application.

This is why this guide includes a section dedicated to helping you compile the MFC with Winelib.

Wine Dll Override

The purpose of this section is to make you aware of potential legal problems. Be sure to read your licenses and to consult your lawyers. In any case you should not consider the remainder of this section to be authoritative since it has not been written by a lawyer.

During the compilation of your program, you will be combining code from several sources: your code, Winelib code, Microsoft MFC code, and possibly code from other vendor sources. As a result, you must ensure that the licenses of all code sources are obeyed. What you are allowed and not allowed to do can vary depending on how you combine the code and if you will be distributing it. For example, if you are releasing your code under the GPL or LGPL, you cannot use MFC because these licenses do not allow covered code to depend on libraries with non-compatible licenses. There is a workaround - in the license for your code you can make an exception for the MFC library. For details see The GNU GPL FAQ.

Wine/Winelib is distributed under the GNU Lesser General Public License. See the license for restrictions on the modification and distribution of Wine/Winelib code. In general it is possible to satisfy these restrictions in any type of application. On the other hand, MFC is distributed under a very restrictive license and the restrictions vary from version to version and between service packs. There are basically three aspects you must be aware of when using the MFC.

First you must legally get MFC source code on your computer. The MFC source code comes as a part of Visual Studio. The license for Visual Studio implies it is a single product that cannot be broken up into its components. So the cleanest way to get MFC on your system is to buy Visual Studio and install it via Wine or on a dual boot Linux box.

Then you must check that you are allowed to recompile MFC on a non-Microsoft operating system! This varies with the version of MFC. The MFC license from Visual Studio 6.0 reads in part:

1.1 General License Grant. Microsoft grants to you as an individual, a personal, nonexclusive license to make and use copies of the SOFTWARE PRODUCT for the sole purposes of designing, developing, and testing your software product(s) that are designed to operate in conjunction with any Microsoft operating system product. [Other unrelated stuff deleted.]

So it appears you cannot even compile MFC for Winelib using this license. Fortunately the Visual Studio 6.0 service pack 3 license reads (the Visual Studio 5.0 license is similar):

1.1 General License Grant. Microsoft grants to you as an individual, a personal, nonexclusive license to make and use copies of the SOFTWARE PRODUCT for the purpose of designing, developing, and testing your software product(s). [Other unrelated stuff deleted]

So under this license it appears you can compile MFC for Winelib.

Finally you must check whether you have the right to distribute an MFC library. Check the relevant section of the license on “redistributables and your redistribution rights”. The license seems to specify that you only have the right to distribute binaries of the MFC library if it has no debug information and if you distribute it with an application that provides significant added functionality to the MFC library.

Here is a set of recommendations for getting the MFC compiled with Winelib:

We recommend running winemaker in --interactive mode to specify the right options for the MFC and the ATL part (to get the include paths right, to not consider the MFC MFC-based, and to get it to build libraries, not executables).

Then when compiling it you will indeed need a number of _AFX_NO_XXX macros. But this is not enough and there are other things you will need to '#ifdef-out'. For instance Wine richedit support is not very good. Here are the AFX options I use:

You will also need custom ones for CMonikerFile, OleDB, HtmlView, ..

We recommend using Wine msvcrt headers (-isystem $(WINE_INCLUDE_ROOT)/msvcrt), though it means you will have to temporarily disable winsock support (#ifdef it out in windows.h).

You should use g++ compiler more recent than 2.95. g++ 2.95 does not support unnamed structs while the more recent ones do, and this helps a lot. Here are the options worth mentioning:

• -fms-extensions (helps get more code to compile)
• -fshort-wchar -DWINE_UNICODE_NATIVE (helps with Unicode support)
• -DICOM_USE_COM_INTERFACE_ATTRIBUTE (to get the COM code to work)

When you first reach the link stage you will get a lot of undefined symbol errors. To fix these you will need to go back to the source and #ifdef-out more code until you reach a “closure”. There are also some files that don't need to be compiled.

Maybe we will have ready-made makefile here someday..

5 Building Winelib DLLs

For one reason or another you may find yourself with a Linux library that you want to use as if it were a Windows DLL. There are various reasons for this including the following:

• You are porting a large application that uses several third-party libraries. One is available on Linux but you are not yet ready to link to it directly as a Linux shared library.
• There is a well-defined interface available and there are several Linux solutions that are available for it (e.g. the ODBC interface in Wine).
• You have a binary only Windows application that can be extended through plugins, such as a text editor or IDE.

The process for dealing with these situations is actually quite simple. You need to write a spec file that will describe the library interface in the same format as a DLL (primarily what functions it exports). Also you will want to write a small wrapper around the library. You combine these to form a Wine built-in DLL that links to the Linux library. Then you modify the DllOverrides in the wine configuration to ensure that this new built-in DLL is called rather than any windows version.

In this section we will look at two examples. The first example is extremely simple and leads into the subject in “baby steps”. The second example is the ODBC interface proxy in Wine. The files to which we will refer for the ODBC example are currently in the dlls/odbc32 directory of the Wine source.

The first example is based very closely on a real case (the names of the functions etc. have been changed to protect the innocent). A large Windows application includes a DLL that links to a third-party DLL. For various reasons the third-party DLL does not work too well under Wine. However the third-party library is also available for the Linux environment. Conveniently the DLL and Linux shared library export only a small number of functions and the application only uses one of those.

Specifically, the application calls a function:

and the linux library exports a corresponding function:

Start by writing the spec file. This file will describe the interface as if it were a DLL. See elsewhere for the details of the format of a spec file (e.g. man winebuild).

In the simple example we want a Wine built-in DLL that corresponds to the MyWin DLL. The spec file is MyWin.dll.spec and looks something like this:

Notice that the arguments are flagged as long even though they are smaller than that. With this example we will link directly to the Linux shared library whereas with the ODBC example we will load the Linux shared library dynamically. The lost heir wings of fire summary.

In the case of the ODBC example you can see this in the file odbc32.spec.

Firstly we will look at the simple example. The main complication of this case is the slightly different argument lists. The f parameter does not have to be passed to the Linux function and the d parameter (theoretically) has to be converted between unsigned long * and unsigned short *. Doing this ensures that the high bits of the returned value are set correctly. Also unlike with the ODBC example we will link directly to the Linux Shared Library.

For a more extensive case we can use the ODBC example. This is implemented as a header file (proxyodbc.h) and the actual C source file (proxyodbc.c). Although the file is quite long it is extremely simple in structure.

DllMain the function is used to initialize the DLL. On the process attach event the function dynamically links to the desired Linux ODBC library (since there are several available) and builds a list of function pointers. It unlinks on the process detach event.

Then each of the functions simply calls the appropriate Linux function through the function pointer that was set up during initialization.

So how do we actually build the Wine built-in DLL? The easiest way is to get winemaker to do the hard work for us. For the simple example we have two source files (the wrapper and the spec file). We also have the 3rd party header and library files of course.

Put the two source files in a suitable directory and then use winemaker to create the build framework, including configure script, makefile etc. You will want to use the following options:

Wine Windows Version

• --nosource-fix (requires winemaker version 0.5.8 or later) to ensure that the two files are not modified (if using an older version, make the two files read-only and ignore the complaints about being unable to modify them).
• --dll --single-target MyWin --nomfc to specify the target.
• --DMightNeedSomething -I3rd_party_include -L3rd_party_lib -lxxxx -lyyyy where these are the locations of the header files etc.

After running winemaker I like to edit the Makefile to add the line CEXTRA = -Wall just before the defines.

Then simply run configure and make as normal (described elsewhere).

So how do you install the proxy and ensure that everything connects up correctly? You have quite a bit of flexibility in this area so what follows are not the only options available.

Ensure that the actual Linux Shared Object is placed somewhere where the Linux system will be able to find it. Typically this means it should be in one of the directories mentioned in the /etc/ld.so.conf file or somewhere in the path specified by LD_LIBRARY_PATH. If you can link to it from a Linux program it should be OK.

Put the proxy shared object (MyWin.dll.so) in the same place as the rest of the built-in DLLs. Alternatively ensure that WINEDLLPATH includes the directory containing the proxy shared object.

If you have both a Windows DLL and a Linux DLL/proxy pair then you will have to ensure that the correct one gets called. The easiest way is probably simply to rename the windows version so that it doesn't get detected. Alternatively you could set a DLL override with winecfg, so that the built-in version is used.

Once you have done this you should be using the Linux Shared Object successfully. If you have problems then set the WINEDEBUG=+module environment variable before running wine to see what is actually happening.

Wine Setup

Suppose you want to convert incoming DOS format filenames to their Unix equivalent. Of course there is no suitable function in the true Microsoft Windows API, but wine provides a function for just this task and exports it from its copy of the kernel32 DLL. The function is wine_get_unix_file_name (defined in winbase.h).

Linux Mint Wine