Building From Source: Difference between revisions

From MediaWiki
Jump to navigationJump to search
Line 1: Line 1:
= Preparing The Build Machine =
= Preparing The Build Machine =
You will need to install [http://fedoraproject.org Fedora Core 6] onto your development system. If you want to build a 64 bit version (''x86_64'') of the '''NST''', you will need to download the ''x86_64'' version of 64 [http://fedoraproject.org Fedora Core 6].
If you don't want to use physical hardware, you can use a Virtual Machine (even running under Windows) to do your '''NST''' development under. We have found that either ''VMWare Server'' (our preference) or ''VMWare Player'' from [http://www.vmware.com/ VMware] can be used (even if you want to build a ''x86_64'' version of the '''NST'''). We have also found that [http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx Virtual PC] can be used.


= Getting the NST Source Code =
= Getting the NST Source Code =

Revision as of 07:35, 3 August 2007

Preparing The Build Machine

You will need to install Fedora Core 6 onto your development system. If you want to build a 64 bit version (x86_64) of the NST, you will need to download the x86_64 version of 64 Fedora Core 6.

If you don't want to use physical hardware, you can use a Virtual Machine (even running under Windows) to do your NST development under. We have found that either VMWare Server (our preference) or VMWare Player from VMware can be used (even if you want to build a x86_64 version of the NST). We have also found that Virtual PC can be used.

Getting the NST Source Code

There are several ways to acquire the source code for NST developement (one can find an entire section related to this in the NST FAQ).

For our purposes we will choose the anonymous CVS approach. This permits one to build a current snapshot of the NST distribution as it is being developed.

The following demonstrates how one can create a: nst sub-directory on a Fedora Core 6 based system, and then populate it with the current NST source code (NOTE: Just press the Enter key when prompted for the password as there is no password required for anonymous access):

Checking Out The Current Source Code
[root@localhost ~]# mkdir $HOME/nst
[root@localhost ~]# cd $HOME/nst
[root@localhost nst]# CVSROOT=":pserver:anonymous@nst.cvs.sourceforge.net:/cvsroot/nst"
[root@localhost nst]# export CVSROOT
[root@localhost nst]# cvs login
Logging in to :pserver:anonymous@nst.cvs.sourceforge.net:2401/cvsroot/nst
CVS password:
[root@localhost nst]# cvs co .

   ... You should see file names streaming by in your
       console window - it may take several moments to
       download all of the source files ...

[root@localhost nst]#

As time goes on, you may want to update your source files (the NST developers check in new code quite frequently). Use the following commands:

Updating The Source Code
[root@localhost ~]# cd $HOME/nst
[root@localhost nst]# CVSROOT=":pserver:anonymous@nst.cvs.sourceforge.net:/cvsroot/nst"
[root@localhost nst]# export CVSROOT
[root@localhost nst]# cvs update -Pd

   ... You should see directory names streaming by in your
       console window as CVS searches for updated files ...

[root@localhost nst]#

As setting the CVSROOT variable can be quite tedious, it is recommended that you include its definition in your: "~/.bashrc" file. Add the following lines to the end of: "~/.bashrc".

CVSROOT=":pserver:anonymous@nst.cvs.sourceforge.net:/cvsroot/nst"; export CVSROOT;

Installing Packages

Building a ISO Image

Tweaking The Configure/Build Process

The Magic "${HOME}/.nst" Directory

"${HOME}/.nst/configure.sh"

"${HOME}/.nst/disable.txt"

"${HOME}/.nst/post_install.sh"