-
Notifications
You must be signed in to change notification settings - Fork 99
Compiling
trentmeester edited this page Apr 25, 2012
·
10 revisions
Before forking and cloning nvmecompliance to a local system, the hosting environment should be created. The following Linux environment, or an equivalent one, should be created to host the compliance suite.
- A 64 bit Linux distribution:
* Linux 2.6.35-30-server #56-Ubuntu SMP Mon Jul 11 21:37:42 UTC 2011 x86_64 GNU/Linux (Ubuntu Server 10.10 64 bit)
* 32 bit distributions are not recommended since a compliance suite, to be effective, will need to test 64 bit accesses - Install boost libraries
* For complete details see boost (v/1.42)
* Example Ubuntu: "sudo apt-get install libboost1.42-all-dev" - Install doxygen
* v/1.7.1
* Example Ubuntu: "sudo apt-get install doxygen" - Install libxml++ and thus any dependencies like libxml2
* For complete details see libxml++ (v/2.6)
* Example Ubuntu: "sudo apt-get install libxml++2.6-dev libxml++2.6-doc"
The Linux make system is utilized with a default target to allow compiling the tnvme application. Other targets of interest are as follows:
- clean
* removes object files
* removes intermediate output files - clobber
* removes doxygen generated documentation
* removes log files produced by tnvme
* removes RPM package manager produced files - doc
* Creates doxygen HTML output files from the source code files
- Reference shell script tnvme/classHierarchy.sh to view the output from this action - rpm
* Create RPM package manager files to allow installing tnvme to a target system