[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: compiling confusion (task cycles)
From: |
Carl Sorensen |
Subject: |
Re: compiling confusion (task cycles) |
Date: |
Fri, 22 Jan 2010 23:52:09 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Mark Polesky <markpolesky <at> yahoo.com> writes:
>
> One thing that would clear up a lot of confusion for me is a
> collection of concise "cycles" for different development
> tasks. Something like this, but correct my mistakes,
> because I'm confused:
>
> Documentation editor's edit/compile cycle:
> Initial:
> make
> make doc
> Cycle:
> [edit source files]
> make <-- is this needed?
The nice thing about doing make is that it is much faster than make doc
and may find some texinfo syntax problems, since it creates the info files.
> make doc
I would only do make doc once I think it's done and ready for submission,
because it takes so long.
And since I have a core-duo processor, I do my make doc in the form of
make -j3 CPU_COUNT=3 doc
It goes much faster.
> Reset:
> make doc-clean
I try to never make doc-clean. I only make doc-clean if I'm getting errors
that don't appear related to any changes I've made.
My preferred reset for making docs is to do the proper touch
touch Doumentation/*.*te*
IIRc.
>
> Developer's edit/install cycle:
> Initial:
> make
> make install
As a developer, I *never* do make install. Make install strips debugging
information from the executable. Just do make.
And my Initial becomes something like;
git branch new-branch
git checkout new-branch
make
> Cycle:
> [edit source files]
> make <-- is this needed?
Only if you've edited a c++ file or convert.ly. If you're just playing
with
scheme, no make is necessary.
> make install
Again, no make install.
> Reset:
> make uninstall
I have never done make uninstall.
My reset is
git checkout master
On *very* rare occasions (only if somebody else suggests it)
I will do
make clean
>
> Developer's edit/test cycle:
> Initial:
> make
> make test-baseline
I would include everything below here as part of the cycle, rather than
as the initial.
> [edit source files]
> make
> make check
> Cycle:
> [edit source files]
> make
> make test-redo
> make test-clean <-- really? (from CG 3.1.5)
I've never used make test-redo or make test-clean. I'd like to have some
clarification on what they're used for.
My cycle is to
[edit source files]
make (if needed)
run the individual regression files to see that the regression is solved
Once I'm pretty sure it's right, I run
make check
to make sure I haven't broken anything.
>
> Also, are there any other common task cycles to mention?
>
> This would be really helpful!
>
> Thanks.
> - Mark
>