Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
W
wine-winehq
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
wine
wine-winehq
Commits
905658c4
Commit
905658c4
authored
Feb 27, 2004
by
Dimitrie O. Paun
Committed by
Alexandre Julliard
Feb 27, 2004
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Generate a simple Makefile that uses winegcc to compile.
No longer generate a configure script, that's project policy.
parent
0d203bd7
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
6 additions
and
31 deletions
+6
-31
winemaker
tools/winemaker
+0
-0
winemaker.man
tools/winemaker.man
+6
-31
No files found.
tools/winemaker
View file @
905658c4
This diff is collapsed.
Click to expand it.
tools/winemaker.man
View file @
905658c4
...
...
@@ -13,7 +13,7 @@ winemaker \- generate a build infrastructure for compiling Windows programs on U
]
.br
[
.IR "--lower-include " "| " "--nolower-include "
.IR "--lower-include " "| " "--nolower-include "
] [ " "--mfc " "| " "--nomfc "
]
.br
[
...
...
@@ -21,10 +21,6 @@ winemaker \- generate a build infrastructure for compiling Windows programs on U
]
.br
[
.IR "--wrap " "| " "--nowrap " "] [ " "--mfc " "| " "--nomfc "
]
.br
[
.IR "-Dmacro[=defn] " "] [ " "-Idir " "] [ " "-Ldir " "] [ " "-idll" "] [ " "-llibrary "
]
.br
...
...
@@ -33,7 +29,7 @@ winemaker \- generate a build infrastructure for compiling Windows programs on U
]
.br
[
.IR "--generated-files " "] [ " "--nogenerated-files " "]
[ " "--nogenerated-specs "
.IR "--generated-files " "] [ " "--nogenerated-files " "]
]
.SH DESCRIPTION
...
...
@@ -129,20 +125,9 @@ 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.
.TP
.I --wrap
Specifies that executable targets should be built as libraries and a small
executable wrapper generated for them. This technique is sometimes required
to solve initialization problems occurring on the application startup.
.TP
.I --nowrap
Specifies that no wrapper should be generated for executable targets. This is
the default.
.TP
.I --mfc
Specifies that the targets are MFC based. In such a case winemaker generates a
configure script with MFC specific options, modifies the include and
library paths accordingly, links the target with the MFC library and
generates wrappers for these targets that are executables.
Specifies that the targets are MFC based. In such a case winemaker the include
and library paths accordingly, and links the target with the MFC library.
.TP
.I --nomfc
Specifies that targets are not MFC-based. This option disables use of MFC libraries
...
...
@@ -173,17 +158,10 @@ target specific options.
Specifies that there is only one target, and that it is called "name".
.TP
.I --generated-files
Tells winemaker to generate the build infrastructure files, i.e. the spec
files, the wrapper files, the Makefile.in files, the Make.rules.in file, the
configure.in file and the configure script. This is the default.
Tells winemaker to generate the build the Makefile. This is the default.
.TP
.I --nogenerated-files
Tells winemaker not to generate any of the above files.
.TP
.I --nogenerated-specs
Tells winemaker not to generate the spec files when generating files. This is
particularly useful when using winemaker to generate a build environment and
you already have a spec file.
Tells winemaker not to generate the Makefile.
.SH EXAMPLES
.PP
...
...
@@ -240,9 +218,6 @@ exports (for libraries). We could then restore all these settings for the
corresponding Winelib target. The problem is that we should have such a tool
available under the Wine license first.
.PP
The wrapper code should be generic, i.e. you should be able to have just one
wrapper and specify which library to load using an option.
.PP
Furthermore it is not very good at finding the library containing the
executable: it must either be in the current directory or in the
.IR LD_LIBRARY_PATH .
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment