FBX SDK Programmer's Guide > Getting Started > Installing and Configuring >

# Configuring the FBX SDK for Windows

## Downloading and installing the FBX SDK

To download and install the FBX SDK on WIndows:

1. Go to http://www.autodesk.com/fbx.
2. Navigate to the Downloads page, and follow any instructions.
3. Find the version of FBX SDK 2014.0 for Windows.
4. Download the distribution file for Windows to your computer. The distribution file is a setup program.
5. Run the setup program, and follow the instructions.
6. The setup program lets you specify a destination folder. Specify a folder which is new or empty. In this topic, it is called as <yourFBXSDKpath>, your distribution directory for FBX SDK.

You can read the <yourFBXSDKpath>\readme.txt file. The readme.txt file contains detailed information about changes in FBX SDK since the previous version, as well as any last-minute documentation.

Notes:

- The setup program does not modify the Windows registry or the Windows start menu.
- You can have more than one version of the FBX SDK installed on your computer, provided you install each version in a separate folder.

## Uninstalling the FBX SDK

To remove the FBX SDK from your computer:

1. Run <yourFBXSDKpath>\uninstall.exe.

## Runtime libraries for Windows

Make sure to use the appropriate runtime library depending on your version of Visual Studio, and the processor architecture. The following table shows the library directory structure depending on your version of the FBX SDK for Windows.

NoteVisual Studio 2005 is not supported with FBX SDK 2014.0 and later.

Directory Path | Platform | Visual Studio Version | Processor Architecture
--- | --- | --- | ---
<yourFBXSDKpath>\lib\vs2008\x86\ | Windows | Visual Studio 2008 | 32-bit (x86)
<yourFBXSDKpath>\lib\vs2008\x64\ | Windows | Visual Studio 2008 | 64-bit (x64)
<yourFBXSDKpath>\lib\vs2010\x86\ | Windows | Visual Studio 2010 | 32-bit (x86)
<yourFBXSDKpath>\lib\vs2010\x64\ | Windows | Visual Studio 2010 | 64-bit (x64)
<yourFBXSDKpath>\lib\vs2012\x86\ | Windows | Visual Studio 2012 | 32-bit (x86)
<yourFBXSDKpath>\lib\vs2012\x64\ | Windows | Visual Studio 2012 | 64-bit (x64)

The following table presents the FBX SDK library filenames and their descriptions.

NoteDynamic .lib files require that their corresponding .dll file be available at application run-time (see the Application Dependency column in the table below). If you intend on using a dynamic library version of the FBX SDK with your application, you must distribute the appropriate .dll along with your executable.

Library File | Library Description | Required Runtime Library Option | Required Preprocessor Definition | Application Dependency
--- | --- | --- | --- | ---
fbxsdk-2014.0.lib | Dynamic library, release |  | FBXSDK_SHARED | fbxsdk-2014.0.dll
fbxsdk-2014.0d.lib | Dynamic library, debug |  | FBXSDK_SHARED | fbxsdk-2014.0d.dll
fbxsdk-2014.0-md.lib | Statically linked, release | /MD |  |
fbxsdk-2014.0-mdd.lib | Statically linked, debug | /MDd |  |
fbxsdk-2014.0-mt.lib | Statically linked, release | /MT |  |
fbxsdk-2014.0-mtd.lib | Statically linked, debug | /MTd |  |

The following table provides a description of the runtime library options. These descriptions can also be found at: http://msdn.microsoft.com/en-us/library/2kzt1wy3.aspx.

Runtime Library Option | Description
--- | ---
/MT | Causes your application to use the multithread, static version of the run-time library. Defines _MT and causes the compiler to place the library name LIBCMT.lib into the .obj file so that the linker uses LIBCMT.lib to resolve external symbols.
/MTd | Defines _DEBUG and _MT. This option also causes the compiler to place the library name LIBCMTD.lib into the .obj file so that the linker uses LIBCMTD.lib to resolve external symbols.
/MD | Causes your application to use the multithread- and DLL-specific version of the run-time library. Defines _MT and _DLL and causes the compiler to place the library name MSVCRT.lib into the .obj file. Applications compiled with this option are statically linked to MSVCRT.lib. This library provides a layer of code that allows the linker to resolve external references. The actual working code is contained in MSVCR100.DLL, which must be available at run time to applications linked with MSVCRT.lib.
/MDd | Defines _DEBUG, _MT, and _DLL and causes your application to use the debug multithread- and DLL-specific version of the run-time library. It also causes the compiler to place the library name MSVCRTD.lib into the .obj file.

NoteThese libraries can all be linked to Microsoft’s multithreaded C libraries. FBX SDK code, however, is not guaranteed to be thread-safe.

## Configuring Visual Studio

The instructions in this section are based on Visual Studio 2010.

Note

To build and run the sample programs for the FBX SDK, see Building and Running the Sample Programs.

To create a new Visual Studio solution that uses FBX SDK:

1. Start Visual Studio.
2. To create a new project, choose New Project the File menu.
3. Choose Visual C++ Win32.
4. Continue as usual, then click Finish. The new project and solution appears.
5. Right-click on the project, and select Properties. The Property Pages dialog appears.
6. In the property tree on the left of the Property Pages dialog, choose Configuration Properties C/C++ General.
7. In the properties sheet on the right of the dialog, select <Edit> in the Additional Include Directories drop-down box. The Additional Include Directories dialog appears.
8. In the list box on the top of the Additional Include Directories dialog, click the top blank line until you see a control to browse for directories.
9. Use this control to add the full path for the <yourFBXSDKpath>\include directory and click OK.
10. In the tree on the left of the Property Pages dialog, select Code Generation.
11. In the property sheet on the right, choose the type of run-time library for your project in the Runtime Library drop-down box. The list corresponds to the Visual C++ compiler options: /MD, /MDd,/MT, /MTd, and so on. Not all compiler options are available for all versions of Visual Studio (see runtime libraries for Windows).
12. In the Property Pages dialog box, choose Linker General.
13. In the Additional Library Dependencies drop-down box, select <Edit>. The Additional Library Directories dialog appears.
14. Enter the full path for the <yourFBXSDKpath>\lib folder of the FBX SDK distribution.
15. In the Property Pages dialog box, choose Linker Input. In the Additional Dependencies drop-down box, select <Edit>. The Additional Dependencies dialog appears. Add the appropriate FBX SDK library. For a table describing the available FBX SDK library files, see runtime libraries for Windows.
16. In the previous step, if you selected an FBX SDK library that is either for creating /MTd or /MDd runtimes, then you must do the following:
    1. In the Ignore Specific Default Library drop-down box, select <Edit>. The Ignore Specific Default Library dialog appears.
    2. Enter LIBMCT, and click OK.
    3. In the Additional Dependencies drop-down box, select <Edit>. The Additional Dependencies dialog appears.
    4. Enter wininet.lib, and click OK.

NoteIf you are using a dynamic library version of the FBX SDK, add FBXSDK_SHARED to the preprocessor definitions of your project.

## Important notes on preprocessor definitions for your projects

If you are using a dynamic library version of the FBX SDK, add FBXSDK_SHARED to the preprocessor definitions of your project. To do this in Visual Studio, right-click on your project, select: Properties Configuration Properties C/C++ Preprocessor, and edit the Preprocessor Definitions field.

NoteStarting from FBX SDK 2012.0, the following are no longer required:

- The KFBX_DLLINFO preprocessor definition is no longer required for the dynamic library versions.
- If your project uses _SECURE_SCL=0 to link with previous versions of the FBX SDK, it can be removed from the predefined preprocessor identifiers. From FBX SDK 2012.0, the static libraries are built with _SECURE_SCL=1, which is the default value in Visual Studio projects.