make for Nonprogrammers by Dru Lavigne -- If you're a typical FreeBSD user, you may never have compiled C source code on your own. Yet if you've ever issued a make command, it's compiled code for you. How does it do that? What does it do, anyway? And what else can it do? Dru Lavigne answers all of these questions.
Especially useful is this great way to help automate updating your system sources.
On my test system, I already had cvsup up and running and had created a sup file in /root/cvs-supfile. So, I added these lines to /etc/make.conf:
Note: In order for this to work, you must have cvsup-without-gui installed and have configured a SUPFILE at the specified location. If you've installed cvsup-without-gui but haven't yet created a SUPFILE, replace that SUPFILE line with these:
When filling in SUPHOST=, please choose a mirror geographically close to you. Also, review the three files in /usr/share/examples/cvsup to pick and choose which parts of the operating system, ports, and docs you wish to update.
When you've finished, run make update from /usr/src to update the specified sources.
I highly recommend adding OnLAMP to your RSS reader, if only for Dru's FreeBSD articles. Always great information.
03/26/05: Helpful "make" Tips
make for Nonprogrammers by Dru Lavigne -- If you're a typical FreeBSD user, you may never have compiled C source code on your own. Yet if you've ever issued a make command, it's compiled code for you. How does it do that? What does it do, anyway? And what else can it do? Dru Lavigne answers all of these questions.
Especially useful is this great way to help automate updating your system sources.I highly recommend adding OnLAMP to your RSS reader, if only for Dru's FreeBSD articles. Always great information.