André Hentschel : winelib: Tell about projectfile support.
Alexandre Julliard
julliard at winehq.org
Sun May 16 10:50:07 CDT 2010
Module: docs
Branch: master
Commit: c15cfe275af5bb904da272cb0c11d345d6a1663b
URL: http://source.winehq.org/git/docs.git/?a=commit;h=c15cfe275af5bb904da272cb0c11d345d6a1663b
Author: André Hentschel <nerv at dawncrow.de>
Date: Fri May 14 18:42:32 2010 +0200
winelib: Tell about projectfile support.
---
en/winelib-toolkit.sgml | 49 ++++++++++++++++++----------------------------
1 files changed, 19 insertions(+), 30 deletions(-)
diff --git a/en/winelib-toolkit.sgml b/en/winelib-toolkit.sgml
index bede8bc..ebd5c07 100644
--- a/en/winelib-toolkit.sgml
+++ b/en/winelib-toolkit.sgml
@@ -7,39 +7,28 @@
<sect2 id="vc-projects">
<title id="vc-projects.title">Support for Visual C++ projects</title>
<para>
- Unfortunately Winemaker does not support the Visual C++ project
- files, ...yet. Supporting Visual C++ project files (the
- <filename>.dsp</filename> and some <filename>.mak</filename> files
- for older versions of Visual C++) is definitely on
- the list of important Winemaker improvements as it will allow it to
- properly detect 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. All things that the current version of
- Winemaker has to guess or that you have to tell it as will become
- clear in the next section.
+ Winemaker supports the Visual C++ project
+ files! Supported filetypes are <filename>.dsp</filename>,
+ <filename>.dsw</filename>, <filename>.vcproj</filename>
+ and <filename>.sln</filename>. 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.
</para>
<para>
- When the time comes Winemaker, and its associated build system, will
- need some extensions to support:
+ It is recommended to use Winemaker with a
+ project file if available. If you have to choose between a
+ <filename>.dsp</filename> file and a <filename>.vcproj</filename>,
+ then you should use the <filename>.dsp</filename>,
+ because it offers more information.
</para>
- <itemizedlist>
- <listitem>
- <para>
- per file defines and include paths. Visual C++ projects allow
- the user to specify compiler options for each individual file
- being compiled. But this is probably not very frequent so it
- might not be that important.
- </para>
- </listitem>
- <listitem>
- <para>
- multiple configurations. Visual C++ projects usually have at
- least a 'Debug' and a 'Release' configuration which are compiled
- with different compiler options. How exactly we deal with these
- configurations remains to be determined.
- </para>
- </listitem>
- </itemizedlist>
+ <para>
+ The usage is very easy, just replace the path to the sourcefolder
+ with the path to the projectfile.
+ </para>
+ <programlisting>
+ $ winemaker --lower-uppercase myproject.vcproj
+ $ make
+ </programlisting>
</sect2>
<sect2 id="source-analysis">
More information about the wine-cvs
mailing list