(disclaimer: I am not currently employed by a browser vendor, but frequently
contribute to WebKit’s Inspector)
It would be constructive to talk more about the longer term devtools strategy
and architecture for Servo’s browser.
Maybe at a future work week, folks can hash out some ideas in a
high
Hi,
I read something about devtools in recent meeting notes [1].
I don't know to which extent it will be useful, but I wanted to share
the RemoteDebug initiative [2]. There might be things that can be pulled
out from this project.
David
[1] https://github.com/mozilla/servo/wiki/Meeting-2014-
On 05/07/14 21:00, Jack Moffitt wrote:
Cargo is updated almost daily to track rust master. So we'd need one
rustc to build cargo, and one to build servo in the general case.
Ah, yes of course. I was confused between rustc used by Cargo to build
other stuff and rustc used to build Cargo itself.
Cargo is updated almost daily to track rust master. So we'd need one
rustc to build cargo, and one to build servo in the general case.
jack.
On Sat, Jul 5, 2014 at 1:01 PM, Simon Sapin wrote:
> In https://github.com/mozilla/servo/wiki/Meeting-2014-06-30 :
>
>> The other Cargo issue is you have t
In https://github.com/mozilla/servo/wiki/Meeting-2014-06-30 :
The other Cargo issue is you have to have a master checkout for it
and then a snapshot for Servo, which means two builds of rustc, which
is not so nice. It'll all work itself out eventually, though.
I don’t think using Cargo in Serv
5 matches
Mail list logo
