[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Eliminating more recursive make invocations
From: |
Rik |
Subject: |
Re: Eliminating more recursive make invocations |
Date: |
Sun, 12 Jul 2015 18:37:08 -0700 |
7/12/15
FYI,
Under the new build system it is more difficult, but still possible to
re-build just a single file. I've been working on the m-files that
generate the images for the Manual and as soon as you touch one it re-makes
all the images in the file (7) with four different extensions (.txt, .png,
.pdf, .eps). This is super slow and bad for my testing purposes.
Here is an example that shows the general scheme for re-building a single
file; Use -C followed by the relative path to the top-level directory and a
relative path from the top-level to the file to rebuild.
make -C ../.. ./doc/interpreter/extended.pdf
Hope this helps someone else.
--Rik
- Re: in-tree builds and recursive make invocations, (continued)
- Re: in-tree builds and recursive make invocations, Rik, 2015/07/13
- Re: in-tree builds and recursive make invocations, John W. Eaton, 2015/07/15
- Re: in-tree builds and recursive make invocations, Rik, 2015/07/15
- Re: in-tree builds and recursive make invocations, John W. Eaton, 2015/07/16
- Re: in-tree builds and recursive make invocations, Rik, 2015/07/16
- Re: in-tree builds and recursive make invocations, John W. Eaton, 2015/07/16
- Re: in-tree builds and recursive make invocations, Rik, 2015/07/16
Re: Eliminating more recursive make invocations, Rik, 2015/07/12
Re: Eliminating more recursive make invocations,
Rik <=
Re: Eliminating more recursive make invocations, Rik, 2015/07/13