make builds everything

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

make builds everything

Malte Meyn-3
Hi list,

first of all, I’d like thank those who made the make output less
verbose, this makes errors much easier to find. Is there a reason for
building every .o file every time a single .cc file is changed? It’s
very time-consuming when you want to test little changes …

make[1]: Entering directory '/home/malte/lilypond/build/scripts/build'
[…]
make[1]: Entering directory '/home/malte/lilypond/build/lily'
Making lily/out/accidental-engraver.o < cc
Making lily/out/accidental-placement.o < cc
Making lily/out/accidental.o < cc
Making lily/out/align-interface.o < cc
Making lily/out/ambitus-engraver.o < cc
[…]

Cheers,
Malte

Reply | Threaded
Open this post in threaded view
|

Re: make builds everything

Han-Wen Nienhuys-3
On Sat, Mar 21, 2020 at 6:12 PM Malte Meyn <[hidden email]> wrote:
>
> Hi list,
>
> first of all, I’d like thank those who made the make output less
> verbose, this makes errors much easier to find. Is there a reason for
> building every .o file every time a single .cc file is changed? It’s
> very time-consuming when you want to test little changes …

AFAIK it doesn't do this. If you're concerned about build speed I can
recommend installing and enabling ccache, which will speed up many
incremental builds.


--
Han-Wen Nienhuys - [hidden email] - http://www.xs4all.nl/~hanwen

Reply | Threaded
Open this post in threaded view
|

Re: make builds everything

Malte Meyn-3


Am 21.03.20 um 19:19 schrieb Han-Wen Nienhuys:

> On Sat, Mar 21, 2020 at 6:12 PM Malte Meyn <[hidden email]> wrote:
>>
>> Hi list,
>>
>> first of all, I’d like thank those who made the make output less
>> verbose, this makes errors much easier to find. Is there a reason for
>> building every .o file every time a single .cc file is changed? It’s
>> very time-consuming when you want to test little changes …
>
> AFAIK it doesn't do this.

Hm … Trying I don’t have this problem either. I think it’s rather
“building every .o file every time a single .h file is changed” …

> If you're concerned about build speed I can
> recommend installing and enabling ccache, which will speed up many
> incremental builds.
>
>

Reply | Threaded
Open this post in threaded view
|

Re: make builds everything

David Kastrup
Malte Meyn <[hidden email]> writes:

> Am 21.03.20 um 19:19 schrieb Han-Wen Nienhuys:
>> On Sat, Mar 21, 2020 at 6:12 PM Malte Meyn <[hidden email]> wrote:
>>>
>>> Hi list,
>>>
>>> first of all, I’d like thank those who made the make output less
>>> verbose, this makes errors much easier to find. Is there a reason for
>>> building every .o file every time a single .cc file is changed? It’s
>>> very time-consuming when you want to test little changes …
>> AFAIK it doesn't do this.
>
> Hm … Trying I don’t have this problem either. I think it’s rather
> “building every .o file every time a single .h file is changed” …

It should depend on just what .h file is changed.  Some are included by
a whole lot of C files.

--
David Kastrup

Reply | Threaded
Open this post in threaded view
|

Re: make builds everything

Malte Meyn-3


Am 21.03.20 um 20:54 schrieb David Kastrup:

> Malte Meyn <[hidden email]> writes:
>
>> Am 21.03.20 um 19:19 schrieb Han-Wen Nienhuys:
>>> On Sat, Mar 21, 2020 at 6:12 PM Malte Meyn <[hidden email]> wrote:
>>>>
>>>> Hi list,
>>>>
>>>> first of all, I’d like thank those who made the make output less
>>>> verbose, this makes errors much easier to find. Is there a reason for
>>>> building every .o file every time a single .cc file is changed? It’s
>>>> very time-consuming when you want to test little changes …
>>> AFAIK it doesn't do this.
>>
>> Hm … Trying I don’t have this problem either. I think it’s rather
>> “building every .o file every time a single .h file is changed” …
>
> It should depend on just what .h file is changed.  Some are included by
> a whole lot of C files.
>

This came to me the moment I went to bed: I changed something in grob.h
or stencil.h, that’s of course a lot of dependencies. Sorry for the noise!

Reply | Threaded
Open this post in threaded view
|

Re: make builds everything

Jean-Charles Malahieude-2
In reply to this post by Malte Meyn-3
Le 21/03/2020 à 18:11, Malte Meyn a écrit :
> Hi list,
>
> first of all, I’d like thank those who made the make output less
> verbose, this makes errors much easier to find.

It is, unfortunately, sometimes too little verbose: say I've omitted a
closing brace in a texinfo @-command. The only thing I get is

[…]
Making Documentation/fr/out-www/translation-lily-images (hard links)

Please check the logfile

   /home/jcharles/GIT/Traduc/Documentation/fr/notation.texi2pdf.log

for errors

make[3]: ***
[/home/jcharles/GIT/Traduc/stepmake/stepmake/texinfo-rules.make:85:
out-www/notation.pdf] Error 1
make[3]: *** Deleting file 'out-www/notation.pdf'
make[2]: ***
[/home/jcharles/GIT/Traduc/stepmake/stepmake/generic-targets.make:167:
WWW-1] Error 2
make[1]: ***
[/home/jcharles/GIT/Traduc/stepmake/stepmake/generic-targets.make:167:
WWW-1] Error 2
make: ***
[/home/jcharles/GIT/Traduc/stepmake/stepmake/generic-targets.make:185:
doc-stage-1] Error 2

Compilation exited abnormally with code 2 at Mon Mar 23 14:40:40
[end of terminal output]

and at the bottom of notation.texi2pdf.log

[919][920][921][922]
4893652 bytes written
/usr/bin/texi2dvi:
/home/jcharles/GIT/Traduc/scripts/build/out/xetex-with-options exited
with bad status, quitting.

As I've updated some files, I would have preferred the old way
instead of, like with .ly files, trying to obtain a MWE !

How would it be possible to access the Nirvana, or to reinstate some
verbosity in this case, with:

[484][485][486]
2455109 bytes written

/home/jcharles/GIT/Stable/Documentation/fr/out-www/notation/world.texi:53:
Emer
gency stop.
<to be read again>
                    @par
l.53


Cheers,
--
Jean-Charles

Reply | Threaded
Open this post in threaded view
|

Re: make builds everything

Dan Eble
On Mar 23, 2020, at 10:06, Jean-Charles Malahieude <[hidden email]> wrote:
>
> Le 21/03/2020 à 18:11, Malte Meyn a écrit :
>> Hi list,
>> first of all, I’d like thank those who made the make output less verbose, this makes errors much easier to find.
>
> It is, unfortunately, sometimes too little verbose: say I've omitted a closing
...
> How would it be possible to access the Nirvana, or to reinstate some verbosity in this case, with:

make VERBOSE=1 ...
(Verbosity, not Nirvana.)

Regards,

Dan