2 .TH WINEMAKER 1 "September 27, 2001" "Version 0.5.8" "Windows On Unix"
4 winemaker \- generate a build infrastructure for compiling Windows programs on Unix
8 .IR "--nobanner " "] [ " "--backup " "| " "--nobackup " "] [ "--nosource-fix "
12 .IR "--lower-none " "| " "--lower-all " "| " "--lower-uppercase "
16 .IR "--lower-include " "| " "--nolower-include "
20 .IR "--guiexe " "| " "--windows " "| " "--cuiexe " "| " "--console " "| " "--dll " "| " "--nodlls "
24 .IR "--wrap " "| " "--nowrap " "] [ " "--mfc " "| " "--nomfc "
28 .IR "-Dmacro[=defn] " "] [ " "-Idir " "] [ " "-Ldir " "] [ " "-idll" "] [ " "-llibrary "
32 .IR "--interactive " "] [ " "--single-target name "
36 .IR "--generated-files " "] [ " "--nogenerated-files " "] [ " "--nogenerated-specs "
42 is a perl script designed to help you bootstrap the
43 process of converting your Windows sources to Winelib programs.
45 In order to do this winemaker can perform the following operations:
47 - rename your source files and directories to lowercase in the event they
48 got all uppercased during the transfer.
50 - perform Dos to Unix (CRLF to LF) conversions.
52 - scan the include statements and resource file references to replace the
53 backslashes with forward slashes.
55 - during the above step winemaker will also perform a case insensitive search
56 of the referenced file in the include path and rewrite the include statement
57 with the right case if necessary.
59 - winemaker will also check other more exotic issues like '#pragma pack'
60 usage, use of "afxres.h" in non MFC projects, and more. Whenever it
61 encounters something out of the ordinary, winemaker will warn you about it.
63 - winemaker can also scan a complete directory tree at once, guess what are
64 the executables and libraries you are trying to build, match them with
65 source files, and generate the corresponding Makefile.in files.
67 - finally winemaker will generate a global Makefile.in file calling out to all
68 the others, and a configure script customized for use with Winelib.
70 - winemaker knows about MFC-based project and will generate customized files.
75 Disables the printing of the banner.
78 Directs winemaker to perform a backup of all the source files in which it
79 makes changes. This is the default.
82 Tells winemaker not to backup modified source files.
85 Directs winemaker not to try fixing the source files (e.g. Dos to Unix
86 conversion). This prevents complaints if the files are readonly.
89 Tells winemaker to rename all files and directories to lowercase.
92 Tells winemaker to only rename files and directories that have an all
94 So "HELLO.C" would be renamed but not "World.c".
97 Tells winemaker not to rename files and directories to lower case. Note
98 that this does not prevent the renaming of a file if its extension cannot
99 be handled as is, e.g. ".Cxx". This is the default.
101 .I "--lower-include "
102 Tells winemaker that if it does not find the file corresponding to an
103 include statement (or other form of file reference for resource files),
104 then it should convert that filename to lowercase. This is the default.
106 .I "--nolower-include "
107 Tells winemaker not to modify the include statement if it cannot find the
110 .IR "--guiexe " "| " "--windows"
111 Specifies that whenever winemaker finds an executable target, or a target of
112 unknown type, it should assume that it is a graphical application.
115 .IR "--cuiexe " "| " "--console"
116 Specifies that whenever winemaker finds an executable target, or a target of
117 unknown type, it should assume that it is a console application.
120 This option tells winemaker that whenever it finds a target of unknown type,
121 i.e. for which it does not know whether it is an executable or a library,
122 it should assume it is a library.
125 This option tells winemaker not to use the standard set of winelib libraries
126 for imports. That is, any DLL your code uses must be explicitly passed to
127 winemaker with -i options.
128 The standard set of libraries is: advapi32.dll, comdlg32.dll, gdi32.dll,
129 kernel32.dll, odbc32.dll, ole32.dll, oleaut32.dll, shell32.dll, user32.dll,
133 Specifies that executable targets should be built as libraries and a small
134 executable wrapper generated for them. This technique is sometimes required
135 to solve initialization problems occurring on the application startup.
138 Specifies that no wrapper should be generated for executable targets. This is
142 Specifies that the targets are MFC based. In such a case winemaker generates a
143 configure script with MFC specific options, modifies the include and
144 library paths accordingly, links the target with the MFC library and
145 generates wrappers for these targets that are executables.
148 Specifies that targets are not MFC-based. This option disables use of MFC libraries
149 even if winemaker encounters files "stdafx.cpp" or "stdafx.h" that would cause it
150 to enable MFC automatically if neither --nomfc nor --mfc was specified.
153 Adds the specified macro definition to the global list of macro definitions.
156 Appends the specified directory to the global include path.
159 Appends the specified directory to the global library path.
162 Adds the Winelib library to the global list of Winelib libraries to import.
165 Adds the specified library to the global list of libraries to link with.
168 Puts winemaker in interactive mode. In this mode winemaker will ask you to
169 confirm each directory's list of targets, and then to provide directory and
170 target specific options.
172 .I --single-target name
173 Specifies that there is only one target, and that it is called "name".
176 Tells winemaker to generate the build infrastructure files, i.e. the spec
177 files, the wrapper files, the Makefile.in files, the Make.rules.in file, the
178 configure.in file and the configure script. This is the default.
180 .I --nogenerated-files
181 Tells winemaker not to generate any of the above files.
183 .I --nogenerated-specs
184 Tells winemaker not to generate the spec files when generating files. This is
185 particularly useful when using winemaker to generate a build environment and
186 you already have a spec file.
190 Here is a typical winemaker use:
192 $ winemaker --lower-uppercase -DSTRICT
194 The above tells winemaker to scan the current directory and its
195 subdirectories for source files. Whenever if finds a file or directory which
196 name is all uppercase, it should rename it to lowercase. It should then fix
197 all these source files for compilation with Winelib and generate Makefiles.
198 The '-DSTRICT' specifies that the STRICT macro must be set when compiling
199 these sources. Finally winemaker will create a global Makefile.in and
200 configure.in, and run autoconf to generate the configure script.
202 The next step would be:
204 $ ./configure --with-wine=/usr/local/opt/wine
206 This generates the makefiles from the Makefile.in files. The generated
207 makefiles will fetch the Winelib headers and libraries from the Wine
208 installation located in /usr/local/opt/wine.
214 If at this point you get compilation errors (which is quite likely for a
215 reasonably sized project) then you should consult the Winelib User Guide to
216 find tips on how to resolve them.
218 For an MFC-based project one would have run the following commands instead:
220 $ winemaker --lower-uppercase --mfc
222 $ ./configure --with-wine=/usr/local/opt/wine \\
224 --with-mfc=/usr/local/opt/mfc
231 Winemaker should support the Visual Studio project files (.dsp for newer
232 versions and .mak for some older versions). This would allow it to be much
233 more accurate, especially for the macro, include and library path
236 Assuming that the windows executable/library is available, we could
237 use a pedump-like tool to determine what kind of executable it is (graphical
238 or console), which libraries it is linked with, and which functions it
239 exports (for libraries). We could then restore all these settings for the
240 corresponding Winelib target. The problem is that we should have such a tool
241 available under the Wine license first.
243 The wrapper code should be generic, i.e. you should be able to have just one
244 wrapper and specify which library to load using an option.
246 Furthermore it is not very good at finding the library containing the
247 executable: it must either be in the current directory or in the
248 .IR LD_LIBRARY_PATH .
250 Winemaker does not support message files and the message compiler yet.
255 The Winelib User Guide:
257 http://wine.codeweavers.com/docs/winelib-user/
263 Francois Gouget <fgouget@codeweavers.com> for CodeWeavers
projects / wine / blob