I found I needed some extra quotes, escaped, to make this work.

cc_wrapper="\"env CCACHE_PREFIX=distcc CCACHE_SLOPPINESS=time_macros
ccache\"”

But even then, it's not really working for me. I get compilation
differences between local and remote and very low levels of parallelism.



On Fri, Sep 20, 2024 at 12:59 PM Graeme Jenkinson <
[email protected]> wrote:

> I use disc to build v8. As long as you are sending compile jobs to the
> same platform it’s fairly trivial. Adding something like:
>
> cc_wrapper="env CCACHE_PREFIX=distcc CCACHE_SLOPPINESS=time_macros ccache”
>
> to args.gn and configuring the hosts for distcc should do the job.
>
> If you’re cross compiling its and/or the platform executing the build jobs
> is different it’s a bit more complicated. You’ll need to set DISTCC_CMDLIST
> to map the compilers on the build server. If you’re intending to use the
> pump mode (which you’ll likely need as preprocessing on the client will
> quickly become the bottleneck) you also have to be able to find the system
> headers on the build server.
>
> I cross compile using a completely different platform and have a document
> describing the setup but it’s slight specific to my environment (I can’t
> recall whether I managed to cache on the remote machines or that this
> wasn’t possible for me. It likely is possible if the platforms are the same).
> This setup has reduced my compile times from 1-2 hours to 10-15 minutes
> from clean.
>
> Let me know if you need some help with this.
>
> Kind regards,
>
> Graeme
>
> On 19 Sep 2024, at 18:02, Erik Corry <[email protected]> wrote:
>
> Hi
>
> The compile times are killing me.
>
> Does anyone have good experiences distributing V8 compilations across
> several workstations? AFAIK distcc used to work, but I'm not sure
> if it still does.
>
> I'm already using ccache, which is great as long as you don't change
> configurations or edit a .h file.
>
> --
> Erik Corry
>
> --
> --
> v8-dev mailing list
> [email protected]
> http://groups.google.com/group/v8-dev
> ---
> You received this message because you are subscribed to the Google Groups
> "v8-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/v8-dev/CAHZxHpiefa5qhtm0qgvgNQgEf0e_CyL4Rfd1Xng%3DZL%3DEyt8t8w%40mail.gmail.com
> <https://groups.google.com/d/msgid/v8-dev/CAHZxHpiefa5qhtm0qgvgNQgEf0e_CyL4Rfd1Xng%3DZL%3DEyt8t8w%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
>
> --
> --
> v8-dev mailing list
> [email protected]
> http://groups.google.com/group/v8-dev
> ---
> You received this message because you are subscribed to the Google Groups
> "v8-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/v8-dev/5B0062AE-B479-415F-B38F-FB61107324E0%40capabilitieslimited.co.uk
> <https://groups.google.com/d/msgid/v8-dev/5B0062AE-B479-415F-B38F-FB61107324E0%40capabilitieslimited.co.uk?utm_medium=email&utm_source=footer>
> .
>

-- 
-- 
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- 
You received this message because you are subscribed to the Google Groups 
"v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-dev/CAHZxHpjYrkPk7YT5oa68vWO0GD%2B3x4ptDUiborQ%3Du9J5A2-u5w%40mail.gmail.com.

Reply via email to