The way to do this sort of thing is to specify the sequence of directories you
want built with the
--seq=fname
command line option. Sequence files can #include other files. See the
documentation in the top-level file
tools/build-sequence
If you are hacking HOL frequently, please read the manual at Manual/Developers,
and if there’s stuff not there, please suggest possible fixes (or make pull
requests to fix it of course).
I hope this helps,
Michael
On 22/12/17, 05:01, "Mario Castelán Castro" <marioxcc...@yandex.com> wrote:
Hello.
When modifying HOL4 itself, sometimes building “hol.bare” suffices to
test the effects of the change.
A complete build from scratch with -j 2 (I have 2 hardware threads)
takes around 1,600 s in my computer. Changing “early” files (like those
in “src/1”) causes nearly everything to be re-built, so the time is
around the same. Is it possible to build *only* “hol.bare”?. This would
make testing the effect of my changes much more convenient.
I tried with “bin/build bin/hol.bare” but it fails with “Multi-dir build
not implemented yet”.
Thanks.
--
Do not eat animals; respect them as you respect people.
https://duckduckgo.com/?q=how+to+(become+OR+eat)+vegan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
hol-info mailing list
hol-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hol-info
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
hol-info mailing list
hol-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hol-info
