Project Properties


Project properties can be accessed through the normal means of right-clicking on the desired project and selecting the Properties menu. Properties pages are platform-specific. Items that are Android-specific will be prefixed with [Android] in this document.

General Properties

This page contains the general properties for the project.

Debugging Properties

This page selects the debugger and options. The Nsight Tegra Debugger is used to debug the projects. roperties pages are platform-specific. Items that are Android-specific will be prefixed with [Android] in this document.

Deployment

This page allows you to edit the deploy options of the project.

Android Directories

This page allows you to edit the locations of the Android SDK, Android ANT, JDK, and Android NDK.

C/C++ Properties

This category contains pages for configuring C/C++ compiler options, such as additional include directories, or whether or not to generate debug info.

Using Precompiled Headers

Nsight Tegra supports the use of precompiled headers.

On the Precompiled Header tab, you can select whether to create or use a precompiled header during the build.

To use the precompiled header, first set Precompiled Header to Use on the project level, and create two files for the precompiled header: stdafx.h and stdafx.cpp. Names of the files without the extension must match the Precompiled Header File property. In stdafx.cpp add the only line:

#include "stdafx.h"

Include any headers you want to precompile in the stdafx.h.

Nsight Tegra forces inclusion of the precompiled header into every file that has the Precompiled Header property set to Use. However, it is better to include it manually; otherwise, the Visual Studio Intellisense might not work as expected. Note that precompiled header files are not passed to the linker/librarian.

It is also possible to print the included headers in the Output window. To configure this, set C/C++ > General > Echo Included Headers to Yes. This will make the compiler print the name of each header file used, indented with dots based on #include depth. If you are using GCC, precompiled headers will also be printed; invalid ones are printed with x and valid ones are printed with !. Clang does not print included precompiled headers at all.

On the Language tab, you can select the language standard that you want the compiler to use.

This property dictates which rules the GCC or Clang compiler will use when processing the files. This affects what grammar is correct, and what language features are supported and recognized.

Linker Properties

This category contains pages for linker options.

Ant Build Properties

This page will only appear if your platform is Tegra-Android.

This page contains options for the Android SDK ANT build.

Gradle Build Properties

Please check the official Gradle 4.4.1 manual and https://developer.android.com/studio/build/gradle-tips for the additional details on integration of Android SDK build tools with Gradle 4.4.1 with help of Android Gradle plugin 2.3.

Maven Publishing Property Page

The values of Maven Publishing page properties are supplied to a Gradle build script and written into a POM XML file at publishing.

For additional information, please check the following links:

https://maven.apache.org/guides/mini/guide-naming-conventions.html

https://maven.apache.org/pom.html#Maven_Coordinates

https://maven.apache.org/guides/introduction/introduction-to-repositories.html

https://github.com/wupdigital/android-maven-publish/releases/tag/3.2.0

Additional Dependencies Property Page

NDK Build Properties

This page will only appear if your platform is Tegra-Android.

This page displays properties for projects that build with NDK-BUILD. It is only available when the configuration type is set to Make Application.


NVIDIA® GameWorks™ Documentation Rev. 1.0.200601 ©2014-2020. NVIDIA Corporation. All Rights Reserved.