Project:Sandbox

= Working With AirTies Software Build Profiles =

Introduction
What are Profiles? '''

Creating a Workspace Directory Structure
Introduction... Introduction... Introduction... Introduction... Introduction... Introduction... Introduction... Introduction... Introduction... ''' The most widely used directory structure for working with various Software Build Profiles is as follows:       ~/test/target/buildsys/ ...    The exact name of the test and target' directories is up to you. However, the convention would be to use test and then various subdirectory names that are meaningful to you.  '   Some people choose to use subdirectory names like:        a, b, c, etc. ''' ''Or, a descriptive product name such as:       BGW210, NVG599-2.4G_HEAD, etc.   Certainly, it is never a problem to use additional subdirectories as you wish, such as:        ~/test/NVG599/2.4G_HEAD/buildsys/, ~/test/NVG599/5G_HEAD/buildsys/, etc. 

Building and Image for a Specific Product
In the following examples, we will use the series of NVG599 profiles as an example. '''       First, we will want to create our overall working directory:       ~/test# mkdir MVG599'''    The exact name of the test and target' directories is up to you. However, the convention would be to use test and then various subdirectory names that are meaningful to you.  '   Some people choose to use subdirectory names like:        a, b, c, etc. ''' ''Or, a descriptive product name such as:       BGW210, NVG599-2.4G_HEAD, etc.   Certainly, it is never a problem to use additional subdirectories as you wish, such as:        ~/test/NVG599/2.4G_HEAD/buildsys/, ~/test/NVG599/5G_HEAD/buildsys/, etc. 

Building and Image for a Specific Product
Introduction... Introduction... Introduction... Introduction... Introduction... Introduction... Introduction... Introduction... Introduction... ''' The most widely used directory structure for working with various Software Build Profiles is as follows:      ~/test/target/buildsys/ ...    The exact name of the test and target' directories is up to you. However, the convention would be to use test and then various subdirectory names that are meaningful to you.  '   Some people choose to use subdirectory names like:        a, b, c, etc. ''' ''Or, a descriptive product name such as:       BGW210, NVG599-2.4G_HEAD, etc.   Certainly, it is never a problem to use additional subdirectories as you wish, such as:        ~/test/NVG599/2.4G_HEAD/buildsys/, ~/test/NVG599/5G_HEAD/buildsys/, etc.