Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hello Kevin,

2011/10/30 Kevin Hunter <hunteke@earlham.edu>:
Hullo List,

I'm currently working in the sc/ module, and I'm in the "make small change,
re-compile, make small change, re-compile" stage.  This is proving very
cumbersome, however, as I'm unable to re-make just the affected files.  For
instance, note my attached output, showing the output of

$ make -j1 | head; sleep; make -j1 | head

Should not at least the first 3 completed executions no longer need to be
re-executed?

This is frustrating because it results in a latency of 5+ minutes on my slow
2-core machine before I can see the results of a code change.

Are there any pointers for me on how I can compile _just the exact_ piece of
code on which I'm working (and affected other snippets, of course)?


 Use make build -srj2 but leave out the "build" at least once before
creating the patch or pushing your changes. What needs most time is
linking and executing our unit tests and with make build you skip the
tests.

Regards,
Markus

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.