From bc14dd30a8e03e28c9d28ab4c5b6e52e8d7c8d26 Mon Sep 17 00:00:00 2001 From: Bill Wendling Date: Sat, 28 Mar 2009 10:24:15 +0000 Subject: [PATCH] Update the Visual Studio docs. Patch by Stefanus! git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@67940 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/GettingStartedVS.html | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/docs/GettingStartedVS.html b/docs/GettingStartedVS.html index 35413c6f4f7..37bdd30b085 100644 --- a/docs/GettingStartedVS.html +++ b/docs/GettingStartedVS.html @@ -337,9 +337,9 @@ int main() { -

Note: this will only work for trivial C programs. Non-trivial programs - (and any C++ program) will have dependencies on the GCC runtime that - won't be satisfied by the Microsoft runtime libraries.

+

Note: this will only work for trivial C programs. Non-trivial programs + (and any C++ program) will have dependencies on the GCC runtime that won't + be satisfied by the Microsoft runtime libraries.

  • Execute the native code program:

    @@ -360,6 +360,17 @@ int main() {
    +
      +
    • In Visual C++, if you are linking with the x86 target statically, the + linker will remove the x86 target library from your generated executable or + shared library because there are no references to it. You can force the + linker to include these references by using + "/INCLUDE:_X86TargetMachineModule" when linking. In the Visual + Studio IDE, this can be added in +Project Properties->Linker->Input->Force Symbol References. +
    • +
    +

    If you are having problems building or using LLVM, or if you have any other general questions about LLVM, please consult the Frequently Asked Questions page.

    -- 2.34.1