Re: UNIX newbie question

[nathan@cco.caltech.edu (Nathan Mates)]

In article <32915a$btu@crl3.crl.com>, Joe Kohn <joko@crl.com> wrote:
>Thanks all, for the hand-holding on getting a jpeg converter compiled. It
>worked like a charm. Too bad I couldn't get the jpeg-5beta to actually
>convert graphics; maybe that'll be tomorrow's project.
>
>One more simple question. I now have a subdirectory that is filled with 
>source code and executables and doc files and many many many other files.
>Is there are rule of thumb as to what files can be deleted after a compile?

    To save space (it means that future makes will take longer), you
can safely remove all files ending in ".o". So 'rm *.o' will clean up
the intermediate files not used in compiling. The files ending in ".c"
are source code files; they should be kept around until you get the
thing working. You can also probably delete the tar file unless you're
paranoid about accidentally killing the source files, etc.

   When you actually get it working, you should keep the executables,
and the manual pages (those tend to end in .1 for most programs). All
the other files are irrelevant, and can be deleted.

Nathan
-- 
* Nathan Mates   http://www.ugcs.caltech.edu/~nathan/               *
* Ftp humor archiver: ftp to cco.caltech.edu, look in pub/humor     *
* Largest collection of Clinton Jokes, other canonical lists        *
* Support Twilight II, the best screen saver for the Apple IIGS!    *