File: Tutorial.Build.txt

package info (click to toggle)
openni 1.5.4.0%2Bdfsg-8
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 45,580 kB
  • sloc: cpp: 116,706; ansic: 58,807; sh: 10,287; cs: 7,698; java: 7,402; python: 1,547; makefile: 492; xml: 167
file content (32 lines) | stat: -rw-r--r-- 2,026 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
/**
@page build_and_run_sample Building and running a sample application

This step is needed to ensure that OpenNI was installed properly, and that the development environment 
is properly set up to enable you to build OpenNI-based applications.

To build and run a sample application:
-# Make sure you have the latest Microsoft Platform SDK installed (You
		can currently download this via the following hyperlink: 
		<a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=a55b6b43-e24f-4ea3-a93e-40c0ec4f68e5&DisplayLang=en">Microsoft's
		Platform SDK Web Install</a>).
-# Open Windows Explorer (or your favorite file navigator), and browse to OpenNI installation directory 
		(default: C:\\Program Files\\OpenNI)
-# In OpenNI directory browse to: Samples\\NiSimpleViewer.
-# Open the suitable project file, NiSimpleViewer.vcxproj, and build the application. If the build
		fails, contact PrimeSense support.
-# After successfully building the project, before trying to run it, please ensure that the 
		SamplesConfig.xml file is correctly configured:
		-# Browse to the 'Data' directory (the default location of this directory is C:\\Program Files\\OpenNI\\Data).
		-# Open the SamplesConfig.xml for editing using a text editor (additional information can under @ref xmlscripts).

@note Throughout the sample applications tutorial you will encounter use of relative paths in the sample 
application source files. Note that when your application is executed from within a debugging environment 
such as Microsoft Visual Studio, paths which are not absolute may not be resolved relatively to the 
output executable.

@note Therefore, in order for the sample application to execute correctly in Debug mode, you should modify 
the Working Directory to be the sub-folder into which the executable is located.
You can also use Visual Studio's macro \$(TargetDir) instead of setting an actual path.

@note Use "Project Properties"->"Debugging"->"Working Directory" to set the value.
*/