I restarted my machine to free the memory and now it took 8 mins to
recompile the code.
Any faster way to debug the layout crate?
On Sun, Mar 31, 2019 at 12:04 AM Yu Feng wrote:
> Hi Josh,
>
> I am modifying the layout crate:
> https://github.com/servo/servo/tree/master/components/layout
>
> [im
Hi Josh,
I am modifying the layout crate:
https://github.com/servo/servo/tree/master/components/layout
[image: image.png]
On Fri, Mar 29, 2019 at 9:26 PM Josh Bowman-Matthews
wrote:
> Hi Yu,
> Servo can take a long time to build on machines that do not have many
> CPUs or have less than 8GB of
Hi Josh,
I am modifying the layout crate:
https://github.com/servo/servo/tree/master/components/layout
[image: image.png]
On Fri, Mar 29, 2019 at 9:26 PM Josh Bowman-Matthews
wrote:
> Hi Yu,
> Servo can take a long time to build on machines that do not have many
> CPUs or have less than 8GB of
Hi Yu,
Servo can take a long time to build on machines that do not have many
CPUs or have less than 8GB of RAM, unfortunately. I do not know of a way
around this. Which crates are you modifying before building?
Cheers,
Josh
On 3/28/19 7:24 PM, Yu Feng wrote:
Hi,
I am working on a project th
Hi,
I am working on a project that requires hacking into servo's layout engine
and recompiling the code frequently.
However, every time I make a change on the code, it takes > 1 hour to
recompile:
D-10-18-221-69:servo yufeng$ ./mach build --dev
Compiling servo v0.0.1 (/Users/yufeng/research/
5 matches
Mail list logo
