Module: wine Branch: master Commit: 4c9405a83cf9776432fd5e60647c6f97ea79f658 URL: http://source.winehq.org/git/wine.git/?a=commit;h=4c9405a83cf9776432fd5e6064...
Author: André Hentschel nerv@dawncrow.de Date: Sun Aug 16 15:33:11 2009 +0200
winemaker: Update manual.
---
tools/winemaker.man.in | 9 ++++----- 1 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/tools/winemaker.man.in b/tools/winemaker.man.in index 9ae2874..f0e8aed 100644 --- a/tools/winemaker.man.in +++ b/tools/winemaker.man.in @@ -1,5 +1,5 @@ ." -*- nroff -*- -.TH WINEMAKER 1 "May 2009" "@PACKAGE_STRING@" "Wine Developers Manual" +.TH WINEMAKER 1 "Aug 2009" "@PACKAGE_STRING@" "Wine Developers Manual" .SH NAME winemaker - generate a build infrastructure for compiling Windows programs on Unix .SH SYNOPSIS @@ -214,13 +214,12 @@ $ make In some cases you will have to edit the Makefile or sourcefiles by yourself. .PP Assuming that the windows executable/library is available, we could -use a pedump-like tool to determine what kind of executable it is (graphical +use winedump to determine what kind of executable it is (graphical or console), which libraries it is linked with, and which functions it 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. +corresponding Winelib target. .PP -Furthermore it is not very good at finding the library containing the +Furthermore winemaker 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 . .PP