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 <fengyu8...@gmail.com> wrote: > 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 < > j...@joshmatthews.net> 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 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 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/other/servo/ports/servo) >> > Finished dev [unoptimized + debuginfo] target(s) in 72m 22s >> > [Warning] Could not generate notification! Optional Python module >> 'pyobjc' >> > is not installed. >> > Build Completed in 1:12:24 >> > >> > I am pretty sure that's not the correct way, and could someone please >> share >> > hints about debugging/compiling the layout engine in an efficient and >> > modular way? >> > >> > Thanks, >> > Yu >> > >> >> _______________________________________________ >> dev-servo mailing list >> dev-servo@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-servo >> > > > -- > --Yu > -- --Yu _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
