javascriptcore support status

[adam webkit]

Hi,

I wanted to know if the JavaScriptCore is still supported in the
Chrome port of WebKit. The Windows build instruction located at
http://www.chromium.org/developers/how-tos/build-instructions-windows
mention that it is no longer supported. However, Gettting around page
located at http://www.chromium.org/developers/how-tos/getting-around-the-chrome-...
mentions that one can use Chrome_kjs.sln.

I am exploring the idea of using the Chrome port with JSC as I like
the port better in terms of architecture and at the same time
constrained by JIT only design of V8. My target platform does not
allow JIT(not a technical issue but it is a restricted platform).

Thanks.

[Darin Fisher]

We don't support the JSC build anymore, and it would probably require a fair bit of work to make it work again.  I'm pretty sure we don't want to maintain the configuration going forward as it increases complexity.

-Darin

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
   http://groups.google.com/a/chromium.org/group/chromium-dev

[Evan Martin]

I updated the docs (removed references to KJS).

I suspect the "quick introduction to the solution file" at
http://sites.google.com/a/chromium.org/dev/developers/how-tos/getting-around-the-chrome-source-code
may be obsolete in the new GYP world. If someone can confirm that it
is, I would probably just delete it -- I think the overview below is
more helpful anyway.

PS: It would be cool if we had a per-directory text file that
described what the directory was for; then we could autogenerate the
docs on that page and they wouldn't bitrot like they currently have.

[Dirk Pranke]

On Wed, Nov 10, 2010 at 9:44 AM, Evan Martin <ev...@chromium.org> wrote:
> PS: It would be cool if we had a per-directory text file that
> described what the directory was for; then we could autogenerate the
> docs on that page and they wouldn't bitrot like they currently have.
>

And the READMEs wouldn't bitrot? Granted, at least you could update
them in the same CL you updated the code, but I would bet most of the
time people would forget to update them.

-- Dirk