Module: docs Branch: master Commit: 42d714a53378989466b7d785c1f3533ad7194aa5 URL: http://source.winehq.org/git/docs.git/?a=commit;h=42d714a53378989466b7d785c1...
Author: André Hentschel nerv@dawncrow.de Date: Fri May 14 18:42:36 2010 +0200
winelib: Update Getting the source.
---
en/winelib-intro.sgml | 14 +++++++------- 1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/en/winelib-intro.sgml b/en/winelib-intro.sgml index ca71a20..6af563f 100644 --- a/en/winelib-intro.sgml +++ b/en/winelib-intro.sgml @@ -219,13 +219,13 @@ <term><option>Getting the source</option></term> <listitem> <para> - First if you can try to get the sources together with the - executables/libraries that they build. In the current state of - winemaker having these around can help it guess what it is that - your project is trying to build. Later, when it is able to - understand Visual C++ projects, and if you use them, this will - no longer be necessary. Usually the executables and libraries - are in a <filename class="Directory">Release</filename> or + First you should try to get the sources together with the + executables/libraries that they build. If you have no + Visual C++ project files available winemaker having these around + can help it guess what it is that your project is + trying to build. Otherwise, it is able to understand + Visual C++ projects. Usually the executables and libraries are + in a <filename class="Directory">Release</filename> or <filename class="Directory">Debug</filename> subdirectory of the directory where the sources are. So it's best if you can transfer the source files and either of these directories to