diff --git a/docs/develop/net/build.html b/docs/develop/net/build.html index 5a82c87354..d09bd2ea93 100644 --- a/docs/develop/net/build.html +++ b/docs/develop/net/build.html @@ -22,87 +22,119 @@ body - +

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 +

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
+ +
    +
  1. Get familiar +

    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? +

    +
    2. + +
  2. Furbish your tools +

    Get the build tools + suite.
    + You'll need CVS, JAM, the fixed LD linker +

    +
    3. + +
  3. May the code be with you +

    For dark reason, you should have the source code to build.
    + So, you must checkout (anonymously) the full OBOS CVS: +

      +
    • Using CVS tool: follow the SourceForge information + on CVS. +
    • If you don't want to fight with 'cvs' command line syntax, I recommand + you using CheckItOut tool, with these settings values: +

      + + + + +
      Project 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 SourceForge.
      + Beware, it's huge, expect around 13MB. +
    +

    +
    4. + +
  4. Build +

    Building the whole Networking Kit stuffs was made easy by Jam rules.
    +Simply run these commands from a Terminal:

    +

    + + + + +
    $ cd /path/to/your/local/openbeos/current
    + $ ./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

-
+ + +
  • Install

    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:

    -
    • - +

    + + +
  • Test, test, test

    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 + or by disabling in Network for net_server) Then, run the OBOS 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 +
    • + + + +
    +
    This document is written by Philippe Houdoin and edited by Niels Reedijk. - Last updated on June 15th, 2003
    + Last updated on June 16th, 2003 +