taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> Returning to this issue after a long pause, I suddenly had a new idea, > which is to use something akin to 'use-modules' instead of 'load' on the > files. (I need a procedure and not a macro, and don't actually need to > 'use' the modules, so I use 'resolve-interface' in the patch below. > Don't know if there's a better suited procedure for this purpose.) Sounds good. > The tricky part is turning file names into module names, If that’s the only tricky part, I think we’re doing OK. ;-) > This entails the least amount of duplicated effort from all the variants > we had so far, and finishes in below 2 minutes on my machine. (I think > the only remaining duplication is the compilation of the modules during > 'resolve-interface' and their compilation via 'compile-file', and the > former cannot be done in parallel, so we could again cut the time to > below half of what it is now, if we solved that.) Not bad! I just tried it on my laptop, and it was indeed fast. > From 77ac65593a94673872c477bbbd18eb2465c76030 Mon Sep 17 00:00:00 2001 > From: =?UTF-8?q?Taylan=20Ulrich=20Bay=C4=B1rl=C4=B1/Kammer?= > <taylanbayi...@gmail.com> > Date: Fri, 27 Nov 2015 09:27:55 +0100 > Subject: [PATCH] build: pull: Compile .scm files in one process. > > * guix/build/pull.scm (call-with-process, report-build-progress) > (p-for-each): Remove. > (build-guix): Load and compile files in one process. Go for it! Thank you, and apologies for the looong delay! Ludo’.
