From 8ddc2f87c9d33e6de2da094f7e17cba2bf6c4ee7 Mon Sep 17 00:00:00 2001 From: Petr Mrázek Date: Sun, 5 Feb 2012 04:28:20 +0100 Subject: Update docs. --- Compile.html | 23 ++++++++++++++++++----- 1 file changed, 18 insertions(+), 5 deletions(-) (limited to 'Compile.html') diff --git a/Compile.html b/Compile.html index 35e4ff3e..c6d7226d 100644 --- a/Compile.html +++ b/Compile.html @@ -391,15 +391,27 @@ Grab it from Microsoft's site.

  • open a cmd.exe window and run "cpan XML::LibXML" (obviously without the quotes). This can take a while to complete.
  • Same with "cpan XML::LibXSLT".
  • +

    If you already have a different version of perl (for example the one from cygwin), you can run into some trouble. Either remove the other perl install from PATH, or install libxml and libxslt for it instead. Strawberry perl works though and has all the required packages.

    Build

    -

    Open the build folder and double click the batch script there. This will eventually open -a cmake GUI window. Here, set CMAKE_INSTALL_PREFIX to your DF folder and set up any other -options you're interested in. Hit configure and generate, close the GUI.

    -

    This crates a folder under build/ that contains the solution files for MSVC.

    -

    When you open the solution, make sure you never use the Debug builds. Those aren't +

    There are several different batch files in the build folder along with a script that's used for picking the DF path.

    +

    First, run set_df_path.vbs and point the dialog that pops up at your DF folder that you want to use for development. +Next, run one of the scripts with generate prefix. These create the MSVC solution file(s):

    + +

    Then you can either open the solution with MSVC or use one of the msbuild scripts:

    + +

    When you open the solution in MSVC, make sure you never use the Debug builds. Those aren't binary-compatible with DF. If you try to use a debug build with DF, you'll only get crashes. So pick either Release or RelWithDebInfo build and build the INSTALL target.

    +

    The debug scripts actually do RelWithDebInfo builds.

    @@ -463,6 +475,7 @@ to look at machine code without getting crazy :)

    Good linux tools: