Motorola 6806800C08B User Manual

Page of 52
NetPlane Core Services Overview  User’s Guide (6806800C08B)
NCS Toolkit
Building the Samples
46
   
z
NCS MIBs
These are implemented by NCS services and are used to configure them. They are located 
in the $(TOOLKIT_HOME)/source /mib directory.
z
NCS sample programs and makefiles 
These are provided to jump-start the application development process by providing code 
that is illustrative of the usage of NCS.The sample programs also serve to demonstrate the 
basic capabilities of each service. Application developers can leverage the makefiles 
provided with the sample code to build their development setup for cross-compiling the 
application for all targets supported by NCS
z
NCS tools
These help develop NCS-based applications. They include an SMIDUMP tool used for 
generating code automatically to help implement MIBs
A.4
Building the Samples
This section describes how NCS sample programs can be built for different targets supported 
by NCS.
A.4.1
Development Host Prerequisites
The development host should be based on the SuSE Linux 9.0 (Intel i386 architecture). 
It should also have the following build support installed:
z
MVL cross-compile tool-chain, which is required to build sample applications for a real NCS 
target.
z
SuSE Linux 9.0 native, which is required to build sample applications for a development 
NCS target. (A development target is one in which some NCS target interfaces are provided 
by dummy plug-ins.)
z
NetSNMP 5.1.1 headers available in the (cross) compilation before building the 
“snmptm_demo” product. (Please refer to the Management Access Service Programmer’s 
Reference
 for details.)
A.4.2
"Make" Commands
This section describes a script that allows to build the sample applications.
Description
The script described here allows to build sample applications that are available for most NCS 
services. The script is located in: $TOOLKIT_HOME/source/common and it has to be invoked 
from a BASH shell command prompt. 
More service-specific build instructions, if any, are defined in the respective user’s guides. The 
generated demo binaries and libraries are in the 
$TOOLKIT_HOME/source/common/bin/<target-architecture>
 and 
$TOOLKIT_HOME/source/common/libs/<target-architecture>
 directories 
respectively.