MAN page from Other wine-20030813-SL8.2.i586.rpm

WINEMAKER

Section: Windows On Unix (1)
Updated: September 27, 2001
Index

NAME

winemaker - generate a build infrastructure for compiling Windows programs on Unix

SYNOPSIS

DESCRIPTION

winemakeris a perl script designed to help you bootstrap theprocess of converting your Windows sources to Winelib programs.

In order to do this winemaker can perform the following operations:

- rename your source files and directories to lowercase in the event theygot all uppercased during the transfer.

- perform Dos to Unix (CRLF to LF) conversions.

- scan the include statements and resource file references to replace thebackslashes with forward slashes.

- during the above step winemaker will also perform a case insensitive searchof the referenced file in the include path and rewrite the include statementwith the right case if necessary.

- winemaker will also check other more exotic issues like '#pragma pack'usage, use of "afxres.h" in non MFC projects, and more. Whenever itencounters something out of the ordinary, winemaker will warn you about it.

- winemaker can also scan a complete directory tree at once, guess what arethe executables and libraries you are trying to build, match them withsource files, and generate the corresponding Makefile.in files.

- finally winemaker will generate a global Makefile.in file calling out to allthe others, and a configure script customized for use with Winelib.

- winemaker knows about MFC-based project and will generate customized files.

OPTIONS

--nobanner: Disables the printing of the banner.
--backup: Directs winemaker to perform a backup of all the source files in which itmakes changes. This is the default.
--nobackup: Tells winemaker not to backup modified source files.
--nosource-fix: Directs winemaker not to try fixing the source files (e.g. Dos to Unixconversion). This prevents complaints if the files are readonly.
--lower-all: Tells winemaker to rename all files and directories to lowercase.
--lower-uppercase: Tells winemaker to only rename files and directories that have an alluppercase name.So "HELLO.C" would be renamed but not "World.c".
--lower-none: Tells winemaker not to rename files and directories to lower case. Notethat this does not prevent the renaming of a file if its extension cannotbe handled as is, e.g. ".Cxx". This is the default.
--lower-include: Tells winemaker that if it does not find the file corresponding to aninclude statement (or other form of file reference for resource files),then it should convert that filename to lowercase. This is the default.
--nolower-include: Tells winemaker not to modify the include statement if it cannot find thereferenced file.
--guiexe | --windows: Specifies that whenever winemaker finds an executable target, or a target ofunknown type, it should assume that it is a graphical application.This is the default.
--cuiexe | --console: Specifies that whenever winemaker finds an executable target, or a target ofunknown type, it should assume that it is a console application.
--dll: This option tells winemaker that whenever it finds a target of unknown type,i.e. for which it does not know whether it is an executable or a library,it should assume it is a library.
--nodlls: This option tells winemaker not to use the standard set of winelib librariesfor imports. That is, any DLL your code uses must be explicitly passed towinemaker with -i options.The standard set of libraries is: advapi32.dll, comdlg32.dll, gdi32.dll,kernel32.dll, odbc32.dll, ole32.dll, oleaut32.dll, shell32.dll, user32.dll,winspool.drv.
--wrap: Specifies that executable targets should be built as libraries and a smallexecutable wrapper generated for them. This technique is sometimes requiredto solve initialization problems occurring on the application startup.
--nowrap: Specifies that no wrapper should be generated for executable targets. This isthe default.
--mfc: Specifies that the targets are MFC based. In such a case winemaker generates aconfigure script with MFC specific options, modifies the include andlibrary paths accordingly, links the target with the MFC library andgenerates wrappers for these targets that are executables.
--nomfc: Specifies that targets are not MFC-based. This option disables use of MFC librarieseven if winemaker encounters files "stdafx.cpp" or "stdafx.h" that would cause itto enable MFC automatically if neither --nomfc nor --mfc was specified.
-Dmacro[=defn]: Adds the specified macro definition to the global list of macro definitions.
-Idir: Appends the specified directory to the global include path.
-Ldir: Appends the specified directory to the global library path.
-idll: Adds the Winelib library to the global list of Winelib libraries to import.
-llibrary: Adds the specified library to the global list of libraries to link with.
--interactive: Puts winemaker in interactive mode. In this mode winemaker will ask you toconfirm each directory's list of targets, and then to provide directory andtarget specific options.
--single-target name: Specifies that there is only one target, and that it is called "name".
--generated-files: Tells winemaker to generate the build infrastructure files, i.e. the specfiles, the wrapper files, the Makefile.in files, the Make.rules.in file, theconfigure.in file and the configure script. This is the default.
--nogenerated-files: Tells winemaker not to generate any of the above files.
--nogenerated-specs: Tells winemaker not to generate the spec files when generating files. This isparticularly useful when using winemaker to generate a build environment andyou already have a spec file.

EXAMPLES

Here is a typical winemaker use:

$ winemaker --lower-uppercase -DSTRICT

The above tells winemaker to scan the current directory and itssubdirectories for source files. Whenever if finds a file or directory whichname is all uppercase, it should rename it to lowercase. It should then fixall these source files for compilation with Winelib and generate Makefiles.The '-DSTRICT' specifies that the STRICT macro must be set when compilingthese sources. Finally winemaker will create a global Makefile.in andconfigure.in, and run autoconf to generate the configure script.

The next step would be:

$ ./configure --with-wine=/usr/local/opt/wine

This generates the makefiles from the Makefile.in files. The generatedmakefiles will fetch the Winelib headers and libraries from the Wineinstallation located in /usr/local/opt/wine.

And finally:

$ make

If at this point you get compilation errors (which is quite likely for areasonably sized project) then you should consult the Winelib User Guide tofind tips on how to resolve them.

For an MFC-based project one would have run the following commands instead:

$ winemaker --lower-uppercase --mfc
$ ./configure --with-wine=/usr/local/opt/wine \

--with-mfc=/usr/local/opt/mfc
$ make

TODO / BUGS

Winemaker should support the Visual Studio project files (.dsp for newerversions and .mak for some older versions). This would allow it to be muchmore accurate, especially for the macro, include and library pathsettings.

Assuming that the windows executable/library is available, we coulduse a pedump-like tool to determine what kind of executable it is (graphicalor console), which libraries it is linked with, and which functions itexports (for libraries). We could then restore all these settings for thecorresponding Winelib target. The problem is that we should have such a toolavailable under the Wine license first.

The wrapper code should be generic, i.e. you should be able to have just onewrapper and specify which library to load using an option.

Furthermore it is not very good at finding the library containing theexecutable: it must either be in the current directory or in theLD_LIBRARY_PATH.

Winemaker does not support message files and the message compiler yet.

AUTHOR

Francois Gouget <fgougetAATTcodeweavers.com> for CodeWeavers

This document was created byman2html,using the manual pages.