Re: compiling confusion (task cycles)

[Graham Percival]

On Fri, Jan 22, 2010 at 02:45:19PM -0800, Mark Polesky wrote:
> Documentation editor's edit/compile cycle:
>   Initial:
>     make
>     make doc

Yes, although many people would want to do something like
  make -j3
  make doc -j3 CPU_COUNT=3


>   Cycle:
>     [edit source files]
>     make    <-- is this needed?

Not if the source files are all in Documentation/.  If you change
scm/ files (i.e. the docstrings), then it is.

>     make doc

This might work.  But if you're editing a file in notation/, and
don't do anything to notation.tely, your changes won't be
compiled.  In order to compile your changes, you need to
  touch notation.tely

this is a bug in the build system, but nobody wants to mess with
it (for good reason).

>   Reset:
>     make doc-clean

Yes, although a reset is only needed if something goes wrong.
This happens about twice a month.

If something goes seriously wrong, a "make clean" will also be
required.

If something goes really seriously wrong, a "make distclean" and
new "./configure" will also be required.


> Developer's edit/install cycle:
>   Initial:
>     make
>     make install
>   Cycle:
>     [edit source files]
>     make    <-- is this needed?

Theoretically, make install should build whatever's necessary, but
I wouldn't be at all surprised if there's a bug.

>     make install

This would/should also build make doc if all goes well.

>   Reset:
>     make uninstall

Why would a developer install stuff?  In any case, the reset would
need a doc-clean and clean as well.

> Developer's edit/test cycle:
>   Initial:
>     make
>     make test-baseline
>     [edit source files]
>     make
>     make check

I'm not certain if the check is part of the baseline.

Cheers,
- Graham