From: <pst...@us...> - 2008-11-16 00:39:11
|
Revision: 633 http://jazzplusplus.svn.sourceforge.net/jazzplusplus/?rev=633&view=rev Author: pstieber Date: 2008-11-16 00:39:06 +0000 (Sun, 16 Nov 2008) Log Message: ----------- Updated build instructions to assume root privileges. Modified Paths: -------------- web/htdocs/buildingjazz/index.php web/htdocs/buildingtex2rtf/index.php web/htdocs/buildingwx/index.php Modified: web/htdocs/buildingjazz/index.php =================================================================== --- web/htdocs/buildingjazz/index.php 2008-11-16 00:30:22 UTC (rev 632) +++ web/htdocs/buildingjazz/index.php 2008-11-16 00:39:06 UTC (rev 633) @@ -64,27 +64,14 @@ </P> <H3>Building Jazz++ for Linux</H3> -<P> -I'm going to assume you do not have root privileges on your Linux box. Given -this assumption, we'll create a directory called <TT>Jazz++</TT> under your -home directory. This directory will hold the source tree that will be obtained -using Subversion, a build directory call <TT>Build</TT> and a test installation -directory called <TT>TestInstall</TT> that will be generated by the build -sequence. The need for the source directory is obvious. Separating the build -directory from the source tree will allow you to remove the build output -without damaging the source tree. The installation directory will be created -during the build process, and its location will remove the need for root -privileges on your Linux box. -</P> <OL> <LI> -Create a <TT> Jazz++</TT> directory under your home directory and change -directory to the newly created directory. +Change directory to the <TT>OutsideSource</TT> you created when building +wxWidgets. <PRE> cd -mkdir Jazz++ -cd Jazz++ +cd OutsideSource </Pre> </LI> @@ -108,14 +95,14 @@ </LI> <LI> -Change directory to <TT>Jazz++</TT> under your home directory and create a -directory called <TT>Build</TT> that is in parallel with the <TT>jazz</TT> +Change directory to <TT>OutsideSource</TT> under your home directory and create +a directory called <TT>JazzBuild</TT> that is in parallel with the <TT>jazz</TT> source tree directory, and change directory to that location. <PRE> cd .. -mkdir Build -cd Build +mkdir JazzBuild +cd JazzBuild </PRE> </LI> @@ -125,23 +112,20 @@ <PRE> ../jazz/configure \ - --prefix=$HOME/Jazz++/TestInstall \ + --prefix=/usr/local/Jazz++ \ --enable-debug \ --enable-alsa \ --enable-sequencer2 </PRE> The <TT>prefix</TT> option is used so that the <TT>make install</TT> step -found later in these instructions, will not require root privileges. It is -also useful to run <TT>make install</TT> with this prefix option, so that the -resulting install will create a copy of the <TT>jazz.cfg</TT> file that is -independent of the one distributed in the source tree. The configuration file -is modified by the Jazz++ binary. If the version of the <TT>jazz.cfg</TT> file -in your svn working directory was altered, this could lead to update conflicts -when updating the code using Subversion. This may lead to problems using -Jazz++ as a result. -<BR> -<BR> +found later in these instructions, will create a separate Jazz++ directory for +the installation. <TT>make install</TT> will create a copy of the +<TT>jazz.cfg</TT> file that is independent of the one distributed in the source +tree. The configuration file is modified by the Jazz++ binary. If the version +of the <TT>jazz.cfg</TT> file in your svn working directory was altered, this +could lead to update conflicts when updating the code using Subversion. This +may lead to problems using Jazz++ as a result. </LI> <LI> @@ -157,16 +141,18 @@ If all goes well with the build, install Jazz++ using the following command. <PRE> +su make install +exit </PRE> </LI> </OL> <P> You should now have a <TT>jazz</TT> binary in -<TT>$HOME/Jazz++/TestInstall/bin</TT>. If the code prompts you for a Jazz++ +<TT>/usr/local/Jazz++/bin</TT>. If the code prompts you for a Jazz++ configuration file, select the <TT>jazz.cfg</TT> file found in -<TT>$HOME/Jazz++/TestInstall/share/Jazz++</TT>. +<TT>/usr/local/Jazz++/share/Jazz++</TT>. </P> <H3>Building Jazz++ for Mac OS X 10.5.2</H3> @@ -215,8 +201,6 @@ modified by the Jazz++ binary. If the version in your svn working directory was altered, this could lead to update conflicts when updating the code. This may lead to problems using Jazz++. -<BR> -<BR> </LI> <LI> Modified: web/htdocs/buildingtex2rtf/index.php =================================================================== --- web/htdocs/buildingtex2rtf/index.php 2008-11-16 00:30:22 UTC (rev 632) +++ web/htdocs/buildingtex2rtf/index.php 2008-11-16 00:39:06 UTC (rev 633) @@ -25,28 +25,14 @@ </P> <H3>Building Tex2RTF for Linux</H3> -<P> -I'm going to assume you do not have root privileges on your Linux box. Given -this assumption, we'll create a directory called <TT>Jazz++</TT> under your -home directory. This directory will hold the source tree for tex2rtf and -Jazz++ that will be obtained using Subversion, a build directory call -<TT>Tex2rtfBuild</TT> and a test installation directory called -<TT>TestInstall</TT> that will be generated by the build sequence. The need -for the source directory is obvious. Separating the build directory from the -source tree will allow you to remove the build output without damaging the -source tree. The installation directory will be created during the build -process, and its location will remove the need for root privileges on your -Linux box. -</P> <OL> <LI> -Create a <TT> Jazz++</TT> directory under your home directory and change -directory to the newly created directory. +Change directory to the <TT>OutsideSource</TT> directory you created when +building wxWidgets. <PRE> cd -mkdir Jazz++ -cd Jazz++ +cd OutsideSource </Pre> </LI> @@ -70,9 +56,10 @@ </LI> <LI> -Change directory to <TT>Jazz++</TT> under your home directory and create a -directory called <TT>Tex2rtfBuild</TT> that is in parallel with the -<TT>tex2rtf</TT> source tree directory, and change directory to that location. +Change directory to the <TT>OutsideSource</TT> directory under your home +directory and create a directory called <TT>Tex2rtfBuild</TT>. This directory +should be in parallel with the <TT>tex2rtf</TT> source tree directory. Change +directory to that location. <PRE> cd .. @@ -82,19 +69,12 @@ </LI> <LI> -Run the <TT>configure</TT> command generated by the <TT>autoreconf<TT> -command with the following options. +Run the <TT>configure</TT> script generated by the <TT>autoreconf</TT> +command. <PRE> -../tex2rtf/configure \ - --prefix=$HOME/Jazz++/TestInstall \ - --enable-debug +../tex2rtf/configure </PRE> - -The <TT>prefix</TT> option is used so that the <TT>make install</TT> step -found later in these instructions, will not require root privileges. -<BR> -<BR> </LI> <LI> @@ -110,14 +90,16 @@ If all goes well with the build, install tex2rtf using the following command. <PRE> +su make install +exit </PRE> </LI> </OL> <P> You should now have a <TT>tex2rtf</TT> binary in -<TT>$HOME/Jazz++/TestInstall/bin</TT>. +<TT>/usr/local/bin</TT>. </P> <?php Modified: web/htdocs/buildingwx/index.php =================================================================== --- web/htdocs/buildingwx/index.php 2008-11-16 00:30:22 UTC (rev 632) +++ web/htdocs/buildingwx/index.php 2008-11-16 00:39:06 UTC (rev 633) @@ -23,7 +23,7 @@ version of wxWidgets was compiled for Windows, Linux, and the Mac. The Windows build was generated using Visual Studio. Either Visual Studio .NET 2005 or Visual Studio .NET 2008 can be used on Windows. The Linux install was tested -using Fedora 8 using GCC 4.1.2 and Mandriva 2008.0 using GCC 4.2.2. The Mac +using Fedora 9 using GCC 4.3.0 and Mandriva 2008.0 using GCC 4.2.2. The Mac build was tested using Mac OS X 10.5.2 and GCC 4.0.1. </P> @@ -202,12 +202,13 @@ </PRE> </LI> -<LI> Create a directory called <TT>WxBuild</TT> in parallel with the -<TT>wxWidgets-2.8</TT> directory and change directory to that location. +<LI> Create two directories called <TT>WxBuildRelease</TT> and +<TT>WxBuildDebug</TT> in parallel with the <TT>wxWidgets-2.8</TT> directory and +change directory to the <TT>WxBuildDebug</TT> directory. <PRE> -mkdir WxBuild -cd WxBuild +mkdir WxBuildRelease WxBuildDebug +cd WxBuildDebug </PRE> </LI> @@ -232,7 +233,7 @@ The <TT>prefix</TT> option is used so that the resulting wxWidgets build will be installed in a non-standard location to prevent conflicts with OS -installed versions. +installed versions and to make it easy to remove the installation. </LI> <LI> Run <TT>make</TT> using the following command. This will write a file @@ -248,13 +249,48 @@ <PRE> su make install +exit </PRE> </LI> +<LI>Now repeat with in the <TT>WxBuildRelease</TT> directory with the following +configure options and install the release version as root. + +<PRE> +cd ../WxBuildRelease +../wxWidgets-2.8/configure \ + --prefix=/usr/local/wx289 \ + --disable-no_exceptions \ + --disable-no_rtti \ + --disable-compat26 \ + --disable-unicode \ + --with-regex=builtin \ + --enable-std_iostreams \ + --enable-std_string \ + --enable-stl \ + --with-gtk +make 2>&1 | tee BuildLog +su +make install +exit +</PRE> +</LI> + <LI> +Install the release version of the wxWidgets build last to insure this version +is the default configuration. If you installed the debug version last, simply +re-install the release version. You can run the following command to determine +the default configuration. + +<PRE> +wx-config --list +</PRE> +</LI> + +<LI> Make sure your <TT>PATH</TT> and <TT>LD_LIBRARY_PATH</TT> environment variables are set to find the non-stock wxWidgets binaries and libraries just -created before building Jazz++. Adding the following lines in +created before building Tex2RTF and Jazz++. Adding the following lines in <TT>.bash_profile</TT> will do the trick. <PRE> @@ -264,9 +300,7 @@ After adding the above lines to your <TT>.bash_profile</TT> file, it is necessary to reload your bash environment to make these changes -available. Use the following command to accomplish this; -<BR> -<BR> +available. Use the following command to accomplish this. <PRE> source .bash_profile @@ -356,9 +390,7 @@ After adding the above lines to your <TT>.bash_profile</TT> file, it is necessary to reload your bash environment to make these changes -available. Use the following command to accomplish this; -<BR> -<BR> +available. Use the following command to accomplish this. <PRE> source .bash_profile This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |