i2p/haiku-beta6
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated build instructions. This may attract more testers of the network kit.

Browse Source 
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@3532 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Niels Sascha Reedijk
2003-06-16 04:44:15 +00:00
parent 2c67210865
commit 1e90e22397
1 changed files with 90 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/develop/net/build.html
+90 -28
View File
@@ -1,9 +1,8 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<HTML>
<HEAD>
<TITLE>OpenBeOS Network Kit</TITLE>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>OpenBeOS Network Kit</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<STYLE type="text/css">
body
{
@@ -21,26 +20,89 @@ body
background-color: #ffffff;
}
</STYLE>
</HEAD>
<BODY text=#000000 vLink=#0000a0 aLink=#0000ff link=#0000c0 bgColor=#ffffff>
</head>
<H1>OpenBeOS Network Kit: Build &amp; installation instructions</H1>
<P>Building the whole Networking Kit stuffs was made easy by Jam rules.<BR>
When you have downloaded/updated your local code tree, simply run these commands from
a Terminal:</P>
<TABLE cellpadding=6 bgcolor=#E5E5E5 border=0>
<TR>
<TD><TT>$ cd /path/to/your/local/openbeos/current<BR>
$ jam NetworkingKit</TT>
</TD>
</TR>
</TABLE>
<HR>
<H6>Philippe Houdoin, May 16th, 2003</H6>
</BODY>
</HTML>
<body>
<h1>OpenBeOS Network Kit: Build &amp; installation instructions</h1>
<p>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. </p>
<p>So, if you accept your mission :</p>
<h4>a) First, go to <a href="http://open-beos.sourceforge.net/tms/team.php?id=7">team
web page</a>.</h4>
<blockquote>
<p>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?</p>
</blockquote>
<h4>b) Get the <a href="http://open-beos.sourceforge.net/dev.php">build tools
suite</a>.</h4>
<blockquote>
<p>You'll need CVS, JAM, the fixed LD linker</p>
</blockquote>
<h4>c) Then, you should checkout (anonymously) the full OBOS CVS. </h4>
<blockquote>
<p>SourceForge has some <a href="http://sourceforge.net/cvs/?group_id=33869">information
on CVS</a>. If you don't want to fight with 'cvs' command line syntax, I recommand
you using <a href="http://www.bebits.com/app/3407">CheckItOut</a> tool.</p>
<p> Enter these values: <br>
<em>Projet Name</em>: open-beos <br>
<em>Location</em>: /path/to/where/you/want/to/store/OBOS/cvs/tree/locally<br>
<em>Module Name</em>: current <br>
Only check <em>&quot;Open Tracker once Completed&quot;</em> option, if you
want. <br>
There, click &quot;<em>Go</em>&quot;. Patience, it take time (and bandwidth!)</p>
<p>Other solution: download and unzip the current CVS <a href="http://cvs.sourceforge.net/cvstarballs/open-beos-cvsroot.tar.gz%20">snapshot
tarball</a> from: Expect around 13MB.</p>
</blockquote>
<h4>d) Open a Terminal, cd to your all new local CVS current directory. </h4>
<blockquote>
<p> Then:</p>
<pre>
$ ./configure
$ jam NetworkingKit</pre>
<p>It should build all networking kit stuffs. If you encount any compile or
link errors, report it to the network team mailing list.</p>
</blockquote>
<h4>e) Installation</h4>
<blockquote>
<p>Installation script or jam rule is a task uncompleted. So, currently, you
have to install by hands. It sucks, I know.</p>
<p>The network stuff binaries are now under your local <em>current/distro/x86.R1/*</em></p>
<p>To install:</p>
</blockquote>
<ul>
<li> open your <em>current/distro/x86.R1/beos/system/add-ons/kernel/drivers/bin</em><br>
</li>
<li> copy the <em>net_stack_driver</em> and <em>net_server_driver</em> into
your <em>/boot/home/config/add-ons/kernel/drivers/bin</em><br>
</li>
<li> create in your <em>/boot/home/config/add-ons/kernel/drivers/dev/net</em>
two symlinks <em>&quot;net_stack_driver&quot;</em> and <em>&quot;net_server_driver&quot;</em>,
targetting the ones in ../../bin/net_{stack|server}_driver (create this 'dev/net'
directory if needed)<br>
</li>
<li> copy the whole <em>current/distro/x86.R1/beos/system/add-ons/kernel/</em><br>
network folder to your <em>/boot/home/config/add-ons/kernel</em><br>
</li>
<li> copy the <em>libnet.so</em> and <em>libnetapi.so</em> libraries from current/distro/
x86.R1/beos/system/lib to a <em>lib</em> where your networking kit binaries are
located.<br>
</li>
<li> copy the command line net apps from <em>current/distro/x86.R1/beos/bin</em>
<br>
into your <em>/boot/home/config/bin</em> (or another folder of your choice)</li>
</ul>
<h4>f) Test the stack</h4>
<blockquote>
<p>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 <a href="http://philippe.houdoin.free.fr/phil/beos/openbeos/network_kit/">stack
design.</a></p>
</blockquote>
<h6>This document is written by <a href="mailto:[email protected]">Philippe
Houdoin</a> and edited by <a href="mailto:[email protected]">Niels Reedijk</a>.
Last updated on June 15th, 2003</h6>
</body>
</html>