[Common-dev] CR: remove SYSTEM_ID descriptions from common build guide
Rob Lanphier robla at real.comHi Jamie, Thanks for taking this on. Since pgms and doc writers may not notice the CR, I'm cc'ing the folks who might be interested. The only possible nit I can see is that there's no mod for https://producersdk.helixcommunity.org/docs/quickstart.htm . However, it looks like there's at least minimal mention of the SYSTEM_ID there already, and Steve can add more if the need arises. So, I say check it in. Thanks Rob On Tue, 2004-05-11 at 16:33, Jamie Gordon wrote: > Description: > ----------- > The common "getting started" guide > https://common.helixcommunity.org/2004/devdocs/quickstart > tries to tell users which SYSTEM_ID to use, but the appropriate > SYSTEM_ID depends on the project and should be explained in the > project specific Part 2 guides. We are spending a lot of time > on the server mailing list with people who didn't pay attention > to the part that tells them which to use with the server, > because they already chose a SYSTEM_ID in Part 1. > > Attached diff removes this step from the end of thecommon guide > and adds that step to the helix-client and player build guides. > The server and producer guides already explain which SYSTEM_ID > and compilers to use and do not need to be modified. > > > Files Affected: > -------------- > common/www/2004/devdocs/quickstart.html > helix-client/www/2004/devdocs/quickstart.html > player/www/2004/developer/gtk/quickstart.html > > > > ______________________________________________________________________ > Index: 2004/devdocs/quickstart.html > =================================================================== > RCS file: /cvsroot/common/www/2004/devdocs/quickstart.html,v > retrieving revision 1.12 > diff -u -w -r1.12 quickstart.html > --- 2004/devdocs/quickstart.html 10 May 2004 16:32:15 -0000 1.12 > +++ 2004/devdocs/quickstart.html 11 May 2004 23:16:45 -0000 > @@ -746,76 +746,6 @@ > </tr> > </tbody> > </table> > - <p><a name="999968"></a></p> > - <li>Set your <code>SYSTEM_ID</code> environment variable. The <code>SYSTEM_ID</code> > -environment variable tells the build system what kind of platform you > -are running on. To see your choices, look in <code>BUILD_ROOT/build/umakecf</code>: > - </li> > - <p></p> > - <a name="999969"></a> > - <table class="example" border="0"> > - <tbody> > - <tr> > - <td> > - <pre> > -c:\source\> <strong>cd build<br></strong>c:\source\build> <strong>cd umakecf<br></strong>c:\source\build\umakecf> <strong>dir /b *.cf<br></strong>aix-4.2-powerpc.cf<br>aix-4.3-powerpc.cf<br>freebsd-2.2-i386.cf<br>...<br>win32-i386-vc6.cf<br>win32-i386.cf<br>win32.cf<br>wince-300-ppc.cf<br><br>C:\source\build\umakecf><br><br></pre> > - </td> > - </tr> > - </tbody> > - </table> > - <p><a name="999983"></a>These files hold definitions that will be > -passed to the compiler which are appropriate for that platform. Look at > -the list and see which one most closely matches your system. Then set > -your <code>SYSTEM_ID</code> to that file name (but leave out the ".cf" > -at the end). For Windows using Visual C++ 5, choose <code>win32-i386</code>. > -For Windows using Visual C++ 6, choose <code>win32-i386-vc6</code>. On > -Windows, this may look like: </p> > - <a name="999984"></a> > - <table class="example" border="0"> > - <tbody> > - <tr> > - <td> > - <pre> > -c:\source\build\umakecf> <strong>set SYSTEM_ID=win32-i386-vc6</strong> > - > - </pre> > - </td> > - </tr> > - </tbody> > - </table> > - <p><a name="999985"></a>on Unix in the bash shell this might look > -like: </p> > - <a name="999986"></a> > - <table class="example" border="0"> > - <tbody> > - <tr> > - <td> > - <pre> > -myusername at pi2[~]<strong>export SYSTEM_ID=linux-2.2-libc6-i386</strong> > - > - </pre> > - </td> > - </tr> > - </tbody> > - </table> > - <p><a name="999987"></a>and on MacOSX in the tshell this might look > -like: </p> > - <a name="999988"></a> > - <table class="example" border="0"> > - <tbody> > - <tr> > - <td> > - <pre> > -myusername at pi2[~]<strong>setenv SYSTEM_ID macos-gcc3-pb</strong> > - > - </pre> > - </td> > - </tr> > - </tbody> > - </table> > - <p><a name="999433"></a>For Linux systems, use <code>linux-2.2-libc6-i386</code> > -if you are using gcc 2.95 and <code>linux-2.2-libc6-gcc32-i586</code> > -if you are using gcc 3.2. </p> > </ol> > <p><a name="1001228"></a><a name="part2"></a> > Once you have completed these steps, you can now begin the process of > > Index: 2004/devdocs/quickstart.html > =================================================================== > RCS file: /cvsroot/helix-client/www/2004/devdocs/quickstart.html,v > retrieving revision 1.2 > diff -u -w -r1.2 quickstart.html > --- 2004/devdocs/quickstart.html 18 Mar 2004 06:59:51 -0000 1.2 > +++ 2004/devdocs/quickstart.html 11 May 2004 23:17:11 -0000 > @@ -46,6 +46,77 @@ > method for setting environment variables may differ depending on your platform and shell. </p> <ol> + <p><a name="999968"></a></p> > + <li>Set your <code>SYSTEM_ID</code> environment variable. The <code>SYSTEM_ID</code> > +environment variable tells the build system what kind of platform you > +are running on. To see your choices, look in <code>BUILD_ROOT/build/umakecf</code>: > + </li> > + <p></p> > + <a name="999969"></a> > + <table class="example" border="0" ID="Table1"> > + <tbody> > + <tr> > + <td> > + <pre> > +c:\source\> <strong>cd build<br></strong>c:\source\build> <strong>cd umakecf<br></strong>c:\source\build\umakecf> <strong>dir /b *.cf<br></strong>aix-4.2-powerpc.cf<br>aix-4.3-powerpc.cf<br>freebsd-2.2-i386.cf<br>...<br>win32-i386-vc6.cf<br>win32-i386.cf<br>win32.cf<br>wince-300-ppc.cf<br><br>C:\source\build\umakecf><br><br></pre> > + </td> > + </tr> > + </tbody> > + </table> > + <p><a name="999983"></a>These files hold definitions that will be > +passed to the compiler which are appropriate for that platform. Look at > +the list and see which one most closely matches your system. Then set > +your <code>SYSTEM_ID</code> to that file name (but leave out the ".cf" > +at the end). For Windows using Visual C++ 5, choose <code>win32-i386</code>. > +For Windows using Visual C++ 6, choose <code>win32-i386-vc6</code>. On > +Windows, this may look like: </p> > + <a name="999984"></a> > + <table class="example" border="0" ID="Table2"> > + <tbody> > + <tr> > + <td> > + <pre> > +c:\source\build\umakecf> <strong>set SYSTEM_ID=win32-i386-vc6</strong> > + > + </pre> > + </td> > + </tr> > + </tbody> > + </table> > + <p><a name="999985"></a>on Unix in the bash shell this might look > +like: </p> > + <a name="999986"></a> > + <table class="example" border="0" ID="Table3"> > + <tbody> > + <tr> > + <td> > + <pre> > +myusername at pi2[~]<strong>export SYSTEM_ID=linux-2.2-libc6-i386</strong> > + > + </pre> > + </td> > + </tr> > + </tbody> > + </table> > + <p><a name="999987"></a>and on MacOSX in the tshell this might look > +like: </p> > + <a name="999988"></a> > + <table class="example" border="0" ID="Table4"> > + <tbody> > + <tr> > + <td> > + <pre> > +myusername at pi2[~]<strong>setenv SYSTEM_ID macos-gcc3-pb</strong> > + > + </pre> > + </td> > + </tr> > + </tbody> > + </table> > + <p><a name="999433"></a>For Linux systems, use <code>linux-2.2-libc6-i386</code> > +if you are using gcc 2.95 and <code>linux-2.2-libc6-gcc32-i586</code> > +if you are using gcc 3.2. </p> > + > <p><a name="998971"></a><li>Using your favorite text editor, create a <code>.buildrc</code> file in the HOME directory. See <code>HOME/build/doc/buildrc.html</code> for more information on <code>.buildrc</code> files. Make sure that you have at least the three lines listed below in your <code>.buildrc</code> file:</li></p> <a name="998972"></a> <table border="0" class="example"width="100%"> > > Index: 2004/developer/gtk/quickstart.html > =================================================================== > RCS file: /cvsroot/player/www/2004/developer/gtk/quickstart.html,v > retrieving revision 1.1 > diff -u -w -r1.1 quickstart.html > --- 2004/developer/gtk/quickstart.html 10 May 2004 20:37:03 -0000 1.1 > +++ 2004/developer/gtk/quickstart.html 11 May 2004 23:17:27 -0000 > @@ -39,6 +39,78 @@ > environment variables may differ depending on your platform > and shell.</p> > <ol> > + > + <p><a name="999968"></a></p> > + <li>Set your <code>SYSTEM_ID</code> environment variable. The <code>SYSTEM_ID</code> > + environment variable tells the build system what kind of platform you > + are running on. To see your choices, look in <code>BUILD_ROOT/build/umakecf</code>: > + </li> > + <p></p> > + <a name="999969"></a> > + <table class="example" border="0" ID="Table1"> > + <tbody> > + <tr> > + <td> > + <pre> > +c:\source\> <strong>cd build<br></strong>c:\source\build> <strong>cd umakecf<br></strong>c:\source\build\umakecf> <strong>dir /b *.cf<br></strong>aix-4.2-powerpc.cf<br>aix-4.3-powerpc.cf<br>freebsd-2.2-i386.cf<br>...<br>win32-i386-vc6.cf<br>win32-i386.cf<br>win32.cf<br>wince-300-ppc.cf<br><br>C:\source\build\umakecf><br><br></pre> > + </td> > + </tr> > + </tbody> > + </table> > + <p><a name="999983"></a>These files hold definitions that will be > + passed to the compiler which are appropriate for that platform. Look at > + the list and see which one most closely matches your system. Then set > + your <code>SYSTEM_ID</code> to that file name (but leave out the ".cf" > + at the end). For Windows using Visual C++ 5, choose <code>win32-i386</code>. > + For Windows using Visual C++ 6, choose <code>win32-i386-vc6</code>. On > + Windows, this may look like: </p> > + <a name="999984"></a> > + <table class="example" border="0" ID="Table2"> > + <tbody> > + <tr> > + <td> > + <pre> > +c:\source\build\umakecf> <strong>set SYSTEM_ID=win32-i386-vc6</strong> > + > + </pre> > + </td> > + </tr> > + </tbody> > + </table> > + <p><a name="999985"></a>on Unix in the bash shell this might look > + like: </p> > + <a name="999986"></a> > + <table class="example" border="0" ID="Table3"> > + <tbody> > + <tr> > + <td> > + <pre> > +myusername at pi2[~]<strong>export SYSTEM_ID=linux-2.2-libc6-i386</strong> > + > + </pre> > + </td> > + </tr> > + </tbody> > + </table> > + <p><a name="999987"></a>and on MacOSX in the tshell this might look > + like: </p> > + <a name="999988"></a> > + <table class="example" border="0" ID="Table4"> > + <tbody> > + <tr> > + <td> > + <pre> > +myusername at pi2[~]<strong>setenv SYSTEM_ID macos-gcc3-pb</strong> > + > + </pre> > + </td> > + </tr> > + </tbody> > + </table> > + <p><a name="999433"></a>For Linux systems, use <code>linux-2.2-libc6-i386</code> > + if you are using gcc 2.95 and <code>linux-2.2-libc6-gcc32-i586</code> > + if you are using gcc 3.2. </p> > + > <li>Using your favorite text editor, create a .buildrc file in the > <code>HOME</code> directory. See <code>BUILD_ROOT/build/doc/buildrc.html</code> > for more information on .buildrc files. Make sure that you have > > ______________________________________________________________________ > _______________________________________________ > Common-dev mailing list > Common-dev at lists.helixcommunity.org > http://lists.helixcommunity.org/mailman/listinfo/common-dev -- Rob Lanphier, Development Support Manager - RealNetworks Helix Community: http://helixcommunity.org Development Support: http://www.realnetworks.com/products/support/devsupport.html