From 1e90e223970d86aa499de569010d4988bb867858 Mon Sep 17 00:00:00 2001 From: Niels Sascha Reedijk Date: Mon, 16 Jun 2003 04:44:15 +0000 Subject: [PATCH] Updated build instructions. This may attract more testers of the network kit. git-svn-id: file:///srv/svn/repos/haiku/trunk/current@3532 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- docs/develop/net/build.html | 118 +++++++++++++++++++++++++++--------- 1 file changed, 90 insertions(+), 28 deletions(-) diff --git a/docs/develop/net/build.html b/docs/develop/net/build.html index fcee0984e5..5a82c87354 100644 --- a/docs/develop/net/build.html +++ b/docs/develop/net/build.html @@ -1,9 +1,8 @@ - - - - -OpenBeOS Network Kit - + + + +OpenBeOS Network Kit + - - + -

OpenBeOS Network Kit: Build & installation instructions

- -

Building the whole Networking Kit stuffs was made easy by Jam rules.
-When you have downloaded/updated your local code tree, simply run these commands from -a Terminal:

- - - - - -
$ cd /path/to/your/local/openbeos/current
-$ jam NetworkingKit -
- -
- -
Philippe Houdoin, May 16th, 2003
- - - + +

OpenBeOS Network Kit: Build & installation instructions

+

Although the stack isn't quite finished, you can already test some basics. + You'll have to get the code, build it, install it and run it. There isn't yet + an easier way of getting the network stack, we're far from ready to release + a binary package.

+

So, if you accept your mission :

+

a) First, go to team + web page.

+
+

Have a look around and see the current status of the stack. Have a glance + over the jobs, perhaps there's something that interests you?

+
+

b) Get the build tools + suite.

+
+

You'll need CVS, JAM, the fixed LD linker

+
+

c) Then, you should checkout (anonymously) the full OBOS CVS.

+
+

SourceForge has some information + on CVS. If you don't want to fight with 'cvs' command line syntax, I recommand + you using CheckItOut tool.

+

Enter these values:
+ Projet Name: open-beos
+ Location: /path/to/where/you/want/to/store/OBOS/cvs/tree/locally
+ Module Name: current
+ Only check "Open Tracker once Completed" option, if you + want.
+ There, click "Go". Patience, it take time (and bandwidth!)

+

Other solution: download and unzip the current CVS snapshot + tarball from: Expect around 13MB.

+
+

d) Open a Terminal, cd to your all new local CVS current directory.

+
+

Then:

+ 
+     $ ./configure
+     $ jam NetworkingKit
+

It should build all networking kit stuffs. If you encount any compile or + link errors, report it to the network team mailing list.

+
+

e) Installation

+
+

Installation script or jam rule is a task uncompleted. So, currently, you + have to install by hands. It sucks, I know.

+

The network stuff binaries are now under your local current/distro/x86.R1/*

+

To install:

+
+ +

f) Test the stack

+
+

You should free one of your /dev/net/*/0 network card (by disable in BONEyard, + or by disabling in Network for net_server) Then, run the ifconfig tool from + Terminal to see (and start) the stack detected interface(s) Last, play with + ping, arp, traceroute, etc. Also check out the details on the stack + design.

+
+
This document is written by Philippe + Houdoin and edited by Niels Reedijk. + Last updated on June 15th, 2003
+ +