<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.0 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
--></style>Bryan et al,<br><p style="margin-bottom: 0in;">,</p>
<p style="margin-bottom: 0in;"><br>
</p>
<p style="margin-bottom: 0in;">For someone who hasn't done C in a
dozen years (and never C++), what are the best tools for editing,
compiling, assembling, linking, loading C++ under Ubuntu 8.04 and
8.10? Mandriva? Puppy? Damn Small Linux? I'd like to know for three
targets: PC Launching the object from BASH, ditto from Gnome, and
PIC. For future reference launching the compiled program under KDE
would also be nice. Have these functions now been combined under an
IDE (integrated development environment)? It's really been too long!
What's the correct terminology?</p>
<p style="margin-bottom: 0in;"><br>
</p>
<p style="margin-bottom: 0in;">Thank you,</p>
<p style="margin-bottom: 0in;"><br>
</p>
<p style="margin-bottom: 0in;">Steven</p>
<p style="margin-bottom: 0in;"><br>
</p>
--- On <b>Fri, 12/12/08, Bryan McLellan <i><btm@loftninjas.org></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">From: Bryan McLellan <btm@loftninjas.org><br>Subject: Re: [Gslug-general] meeting<br>To: "Travis" <travis.eeepc@gmail.com><br>Cc: "gslug" <gslug-general@gslug.org><br>Date: Friday, December 12, 2008, 1:40 PM<br><br><pre>On Fri, Dec 12, 2008 at 11:54 AM, Travis <travis.eeepc@gmail.com> wrote:<br>> I asked this on December 10th but didn't hear anything yet."I<br>would like to<br>> learn to "compile from source" on Ubuntu 8.10. Is there<br>> anything I need to do prior to the meeting?"-- Travis in Shoreline<br><br>It depends what you're looking to do. If you wanted to build apache<br>from the ubuntu packaging per se, it would be something like:<br><br>sudo apt-get install build-essential fakeroot<br>mkdir ~/src<br>cd ~/src<br>apt-get source
apache<br>sudo apt-get build-dep apache<br>cd apache-*<br>dpkg-buildpackage<br>cd ..<br>dpkg -i something.deb<br><br>This seems silly until you use it to build and install a package from<br>a newer source, like create:<br><br># /etc/apt/sources.list.d/jaunty.src.sources.list<br>deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty main restricted<br>universe multiverse<br><br>sudo apt-get update<br><br>Then when you run 'apt-get source package', it will grab the latest<br>source apt knows about. you can list these with 'apt-cache showsrc<br>package' and get a specific version with 'apt-get source<br>package=version'. I use this often for grabbing package sources from<br>debian lenny, debian sid, and ubuntu jaunty on ubuntu intrepid<br>machines.<br><br>If you going to compile a package from upstream source, like getting<br>apache from [1] you'll need to look in the particular source tarball<br>for dependencies and instructions. Like<br><br>cd /tmp<br>wget
http://archive.apache.org/dist/httpd/apache_1.3.41.tar.gz<br>tar -xvzf apache_1.3.41.tar.gz<br>cd apache_1.3.41<br>less INSTALL<br><br>Which lists the build instructions as:<br> $ ./configure --prefix=PREFIX<br> $ make<br> $ make install<br> $ PREFIX/bin/apachectl start<br><br>This is different for every piece of software, but lots of tools like<br>autoconf, make, etc are pretty standard. In the above example I<br>recommend setting PREFIX to /usr/local, and I further recommend being<br>very careful about using hand compiled software because it is more<br>difficult to tell where it installed files to and how to uninstall it<br>than when using packaging.<br><br>Bryan<br><br>[1] http://archive.apache.org/dist/httpd/<br>_______________________________________________<br>Gslug-general mailing list<br>Gslug-general@gslug.org<br>http://lists.gslug.org/mailman/listinfo/gslug-general<br></pre></blockquote></td></tr></table><br>