[chromium-dev] Re: networking code in src/third_party/WebKit/WebCore/platform/network/mac

2009-10-05 Thread Darin Fisher 
Our networking code lives under
/trunk/src/net
We use the code in WebCore/platform/network/chromium, even on Mac OS X.

-Darin


On Mon, Oct 5, 2009 at 11:06 PM, hap 497  wrote:

>
> Hi,
>
> Can you please tell me if chromium on Mac OS X uses the networking
> code in src/third_party/WebKit/WebCore/platform/network/mac?
> Or the code there is for Webkit? I asked because chromium has this
> 'sandbox' architecture, so I am not sure if chromium's networking code
> is totally different (chromium specified) because of this difference
> in architecture.
>
> Thank you.
>
> >
>

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

[chromium-dev] Unkown Error During Building Chromium for Linux

2009-10-05 Thread उज्जवल लामिछाने 

While building chromium in Fedora 10, a strange build error has been
encountered.

The tail of the log of build(hammer --verbose) process is:


[ujj...@ujjwol Desktop]$ tail VerboseChromeBuild.txt
Copying /home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/
sconsbuild/Debug/obj/chrome/_chrome_intermediate/repack/zh-CN.pak to /
home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/sconsbuild/
Debug/locales/zh-CN.pak ...
Copying /home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/
sconsbuild/Debug/obj/chrome/_chrome_intermediate/repack/zh-TW.pak to /
home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/sconsbuild/
Debug/locales/zh-TW.pak ...
Copying /home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/
sconsbuild/Debug/obj/chrome/_chrome_intermediate/repack/default.pak
to /home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/
sconsbuild/Debug/themes/default.pak ...
g++ -o /home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/
sconsbuild/Debug/obj/chrome/page_cycler_tests/test/page_cycler/
page_cycler_test.o -c -fno-rtti -fno-threadsafe-statics -Werror -
pthread -fno-exceptions -Wall -D_FILE_OFFSET_BITS=64 -m32 -march=geode
-pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/
include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/
include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -
I/usr/include/freetype2 -I/usr/include/libpng12 -O0 -g -
D__STDC_FORMAT_MACROS -DCHROMIUM_BUILD -DUNIT_TEST -DGTEST_HAS_RTTI=0 -
D_DEBUG -I/home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/
sconsbuild/Debug/obj/_global_intermediate/chrome -I/home/Ujjwol/
chromium/home/chrome-svn/tarball/chromium/src -I/home/Ujjwol/chromium/
home/chrome-svn/tarball/chromium/src/skia/config -I/home/Ujjwol/
chromium/home/chrome-svn/tarball/chromium/src/third_party/skia/include/
core -I/home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/
third_party/skia/include/effects -I/home/Ujjwol/chromium/home/chrome-
svn/tarball/chromium/src/skia/ext -I/home/Ujjwol/chromium/home/chrome-
svn/tarball/chromium/src/third_party/harfbuzz/src -I/home/Ujjwol/
chromium/home/chrome-svn/tarball/chromium/src/third_party/harfbuzz/
contrib -I/home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/
testing/gtest/include /home/Ujjwol/chromium/home/chrome-svn/tarball/
chromium/src/chrome/test/page_cycler/page_cycler_test.cc
g++ -o /home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/
sconsbuild/Debug/obj/test_shell/npapi_layout_test_plugin/__/
npapi_layout_test_plugin/PluginObject.os -c -fno-rtti -fno-threadsafe-
statics -Werror -pthread -fno-exceptions -Wall -D_FILE_OFFSET_BITS=64 -
m32 -march=geode -O0 -g -fPIC -D__STDC_FORMAT_MACROS -DCHROMIUM_BUILD -
DENABLE_CHANNEL_MESSAGING=1 -DENABLE_DATABASE=1 -DENABLE_DATAGRID=0 -
DENABLE_OFFLINE_WEB_APPLICATIONS=1 -DENABLE_DASHBOARD_SUPPORT=0 -
DENABLE_DOM_STORAGE=1 -DENABLE_JAVASCRIPT_DEBUGGER=0 -
DENABLE_JSC_MULTIPLE_THREADS=0 -DENABLE_ICONDATABASE=0 -
DENABLE_NOTIFICATIONS=0 -DENABLE_XSLT=1 -DENABLE_XPATH=1 -
DENABLE_SHARED_WORKERS=0 -DENABLE_SVG=1 -DENABLE_SVG_ANIMATION=1 -
DENABLE_SVG_AS_IMAGE=1 -DENABLE_SVG_USE=1 -
DENABLE_SVG_FOREIGN_OBJECT=1 -DENABLE_SVG_FONTS=1 -DENABLE_VIDEO=1 -
DENABLE_WORKERS=1 -DBUILDING_CHROMIUM__=1 -DUSE_SYSTEM_MALLOC=1 -
DWTF_USE_PTHREADS=1 -DU_STATIC_IMPLEMENTATION -D_DEBUG -I/home/Ujjwol/
chromium/home/chrome-svn/tarball/chromium/src/third_party/icu/public/
common -I/home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/
third_party/icu/public/i18n -I/home/Ujjwol/chromium/home/chrome-svn/
tarball/chromium/src -I/home/Ujjwol/chromium/home/chrome-svn/tarball/
chromium/src/third_party/npapi -I/home/Ujjwol/chromium/home/chrome-svn/
tarball/chromium/src/third_party/npapi/bindings -I/home/Ujjwol/
chromium/home/chrome-svn/tarball/chromium/src/third_party/WebKit/
JavaScriptCore -I/home/Ujjwol/chromium/home/chrome-svn/tarball/
chromium/src/third_party/WebKit/JavaScriptCore/wtf /home/Ujjwol/
chromium/home/chrome-svn/tarball/chromium/src/webkit/tools/
npapi_layout_test_plugin/PluginObject.cpp
g++ -o /home/Ujjwol/chromium/home/chrome-svn/tarball/chromium/src/
sconsbuild/Debug/obj/test_shell/npapi_layout_test_plugin/__/
npapi_layout_test_plugin/TestObject.os -c -fno-rtti -fno-threadsafe-
statics -Werror -pthread -fno-exceptions -Wall -D_FILE_OFFSET_BITS=64 -
m32 -march=geode -O0 -g -fPIC -D__STDC_FORMAT_MACROS -DCHROMIUM_BUILD -
DENABLE_CHANNEL_MESSAGING=1 -DENABLE_DATABASE=1 -DENABLE_DATAGRID=0 -
DENABLE_OFFLINE_WEB_APPLICATIONS=1 -DENABLE_DASHBOARD_SUPPORT=0 -
DENABLE_DOM_STORAGE=1 -DENABLE_JAVASCRIPT_DEBUGGER=0 -
DENABLE_JSC_MULTIPLE_THREADS=0 -DENABLE_ICONDATABASE=0 -
DENABLE_NOTIFICATIONS=0 -DENABLE_XSLT=1 -DENABLE_XPATH=1 -
DENABLE_SHARED_WORKERS=0 -DENABLE_SVG=1 -DENABLE_SVG_ANIMATION=1 -
DENABLE_SVG_AS_IMAGE=1 -DENABLE_SVG_USE=1 -
DENABLE_SVG_FOREIGN_OBJECT=1 -DENABLE_SVG_FONTS=1 -DENABLE_VIDEO=1 -
DENABLE_WORKERS=1 -DBUILDING_CHROMIUM__=1 -DUSE_SYSTEM_MALLO

[chromium-dev] Re: networking code in src/third_party/WebKit/WebCore/platform/network/mac

2009-10-05 Thread Jeremy Orlow 
er _don't_ use what's in WebCore I mean

On Mon, Oct 5, 2009 at 11:08 PM, Jeremy Orlow  wrote:

> I'm 99% sure we use what's in third_party
>
> On Mon, Oct 5, 2009 at 11:06 PM, hap 497  wrote:
>
>>
>> Hi,
>>
>> Can you please tell me if chromium on Mac OS X uses the networking
>> code in src/third_party/WebKit/WebCore/platform/network/mac?
>> Or the code there is for Webkit? I asked because chromium has this
>> 'sandbox' architecture, so I am not sure if chromium's networking code
>> is totally different (chromium specified) because of this difference
>> in architecture.
>>
>> Thank you.
>>
>> >>
>>
>

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

[chromium-dev] Re: networking code in src/third_party/WebKit/WebCore/platform/network/mac

2009-10-05 Thread Jeremy Orlow 
I'm 99% sure we use what's in third_party
On Mon, Oct 5, 2009 at 11:06 PM, hap 497  wrote:

>
> Hi,
>
> Can you please tell me if chromium on Mac OS X uses the networking
> code in src/third_party/WebKit/WebCore/platform/network/mac?
> Or the code there is for Webkit? I asked because chromium has this
> 'sandbox' architecture, so I am not sure if chromium's networking code
> is totally different (chromium specified) because of this difference
> in architecture.
>
> Thank you.
>
> >
>

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

[chromium-dev] networking code in src/third_party/WebKit/WebCore/platform/network/mac

2009-10-05 Thread hap 497 

Hi,

Can you please tell me if chromium on Mac OS X uses the networking
code in src/third_party/WebKit/WebCore/platform/network/mac?
Or the code there is for Webkit? I asked because chromium has this
'sandbox' architecture, so I am not sure if chromium's networking code
is totally different (chromium specified) because of this difference
in architecture.

Thank you.

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

[chromium-dev] Question about linux pixel tests

2009-10-05 Thread Drew Wilson 
Are some pixel tests currently disabled on the linux release buildbots? I'm
trying to rebaseline some tests that are currently marked as FAIL in
test_expectations, but I can't grab linux images because the .png files
don't exist in the archive grabbed by the rebaseline tool.
As an example, I'm looking at
http://build.chromium.org/buildbot/layout_test_results/webkit-rel-linux/28080/layout-test-results.zip
and
trying to find fast/css/last-of-type-pseudoclass-expected.png (it's not in
there).

-atw

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

[chromium-dev] xp purify unit freak out this evening

2009-10-05 Thread Matt Mueller 

This night xp purify failed with a bunch of new leaks:
http://build.chromium.org/buildbot/waterfall/builders/XP%20Unit%20(purify)/builds/5856/steps/purify%20test:%20unit/logs/stdio

After looking at the stdio for the 10th time I finally saw that the
test didn't exit cleanly, which would explain why atexit and singleton
stuff showed up so much in the leaks.

The last lines were:
[--] 2 tests from DnsMasterTest
[ RUN  ] DnsMasterTest.ConcurrentLookupTest
ERROR:root:src/build\Release\unit_tests.exe exited with non-zero
result code -1073741819

Is this sufficient to blame the flakiness on that test, or are the
logs buffered so it might have actually died in some other test?

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

[chromium-dev] Re: Drive Chrome Automation from Outside Browser Process

2009-10-05 Thread Jeremy Orlow 
How is this different from ChromeBot?
How you control things depends on what level of "realism" you want.  If
you're just verifying the sites work correctly, you might just use the code
the UI tests use.  If you want to actually simulate button clicks and such,
then you'll need something more like selenium.  If you just care about
testing the rendering engine, then you could just hook straight into the
WebKit API (note that it's not _quite_ done yet...so you'd need to use Glue
some as well).

I think maybe you should explore what's there a bit more and/or figure out
exactly what you want to test so you can ask more specific questions.

J

On Mon, Oct 5, 2009 at 7:12 PM, TJ Shah  wrote:

>
> Hi,
>
> I have recently started working on Chrome Release process automation
> where I want to automate Visiting various sites (e.g. Top 200 sites)
> using Chrome and other browsers and look for possible App-compat
> issues. I am fairly new to this kind of automation in Chrome, so
> looking for possible ways to automate that.
>
> I found some references to using Automation Proxy, Web Driver and
> Selenium, but not sure on where to get more information on those
> tools. Can someone throw some light here? Which is better and more
> supported? Any previous work done in this kind of area? Looking for
> more longer term cross-plat tool which we can reply on.
>
> Remember, I want to drive the chrome automation from outside browser
> process so test doesn't die when browser crashes. So I think, In-proc
> browser will be of little help here.
>
> Any help will be appreciated !!!
>
> Thanks,
> TJ
> >
>

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

[chromium-dev] Drive Chrome Automation from Outside Browser Process

2009-10-05 Thread TJ Shah 

Hi,

I have recently started working on Chrome Release process automation
where I want to automate Visiting various sites (e.g. Top 200 sites)
using Chrome and other browsers and look for possible App-compat
issues. I am fairly new to this kind of automation in Chrome, so
looking for possible ways to automate that.

I found some references to using Automation Proxy, Web Driver and
Selenium, but not sure on where to get more information on those
tools. Can someone throw some light here? Which is better and more
supported? Any previous work done in this kind of area? Looking for
more longer term cross-plat tool which we can reply on.

Remember, I want to drive the chrome automation from outside browser
process so test doesn't die when browser crashes. So I think, In-proc
browser will be of little help here.

Any help will be appreciated !!!

Thanks,
TJ
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---

[chromium-dev] buildbot failure in Chromium on Linux Builder (ChromeOS), revision 28075

2009-10-05 Thread buildbot 
Automatically closing tree for "compile" on "Linux Builder (ChromeOS)"

http://build.chromium.org/buildbot/waterfall/builders/Linux%20Builder%20%28ChromeOS%29/builds/4050

http://build.chromium.org/buildbot/waterfall/waterfall?builder=Linux%20Builder%20%28ChromeOS%29

--=>  Automatically closing tree for "compile" on "Linux Builder (ChromeOS)"  
<=--

Revision: 28073, 28074, 28075
Blame list: e...@chromium.org,slightly...@chromium.org,viettrung...@chromium.org

Buildbot waterfall: http://build.chromium.org/

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

[chromium-dev] buildbot failure in Chromium on Linux Interactive Tests (dbg), revision 28075

2009-10-05 Thread buildbot 
Automatically closing tree for "compile" on "Linux Interactive Tests (dbg)"

http://build.chromium.org/buildbot/waterfall/builders/Linux%20Interactive%20Tests%20%28dbg%29/builds/2317

http://build.chromium.org/buildbot/waterfall/waterfall?builder=Linux%20Interactive%20Tests%20%28dbg%29

--=>  Automatically closing tree for "compile" on "Linux Interactive Tests 
(dbg)"  <=--

Revision: 28073, 28074, 28075
Blame list: e...@chromium.org,slightly...@chromium.org,viettrung...@chromium.org

Buildbot waterfall: http://build.chromium.org/

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

[chromium-dev] [extensions] first cut at beta bug list

2009-10-05 Thread Aaron Boodman 

As promised in today's extensions meeting, I've taken a first pass to
identify extensions beta bugs. As a sort of new novelty, I've also
attempted to use the Priority and Size labels, so that we can know
what we should do first, and how much it's going to hurt.

Please see:
http://code.google.com/p/chromium/issues/list?q=Area:extensions+releaseblock:beta&sort=pri&colspec=ID+Pri+Status+Summary+Owner+Mstone+Size

Extensions people: Please take a careful look through this and check
my work. Go ahead and add anything you think should be on the list or
comment if you think something should not be.

Special note: All browser action and popup bugs on mac and linux are
blocked behind the extensions team deciding that we are definitely
doing this feature. We hope to make this decision Friday this week
with the help of the UI posse.

Thanks!

- a

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

[chromium-dev] Re: buildbot failure in Chromium on Linux Builder (Views dbg), revision 28054

2009-10-05 Thread Erik Kay 
It was actually me.  My revert is already in. (I had resolved my merge
conflict with your change poorly)
Erik


On Mon, Oct 5, 2009 at 3:16 PM, John Gregg  wrote:

> Looks like a merge problem with my recent change to render_messages.h
> regarding WebPreferences.  I can submit a fix.   -John
>
> On Mon, Oct 5, 2009 at 3:03 PM,  wrote:
>
>>  http://build.chromium.org/buildbot/waterfall/
>>
>> Automatically closing tree for "compile" on "Linux Builder (Views dbg)"
>>
>>
>> http://build.chromium.org/buildbot/waterfall/builders/Linux%20Builder%20%28Views%20dbg%29/builds/1824
>>
>> Revision: 28053, 28054
>> Blame list: erik...@chromium.org,fin...@chromium.org
>>
>>  Linux Builder (Views dbg)
>> Build 
>> 1824
>>   update
>> scripts
>> stdio
>> update
>> stdio
>> compile
>> failed
>> stdio
>>
>> Changed by: *erik...@chromium.org*
>> Changed at: *Mon 05 Oct 2009 15:00:08*
>> Branch: *src*
>> Revision: *28053*
>>
>> Changed files:
>>
>>- *chrome/browser/extensions/extension_host.cc*
>>- *chrome/browser/views/browser_bubble_win.cc*
>>- *chrome/browser/extensions/extension_host.h*
>>- *chrome/common/render_messages.h*
>>- *chrome/test/data/extensions/samples/set_page_color/popup.html*
>>
>> Comments:
>>
>> Allow popups to close themselves with window.close().
>>
>> This also fixes an issue where not all of the parts of WebPreferences were 
>> being serialized/deserialized across IPC.
>>
>> BUG=23832
>> TEST=run set_page_color extension, when it sets the color, the popup
>> should close
>>
>> Review URL: http://codereview.chromium.org/243096
>>
>>  Changed by: *fin...@chromium.org*
>> Changed at: *Mon 05 Oct 2009 15:00:18*
>> Branch: *src*
>> Revision: *28054*
>>
>> Changed files:
>>
>>- *chrome/app/generated_resources.grd*
>>
>> Comments:
>>
>> Landing a patch (http://codereview.chromium.org/249054) from an external 
>> contributor (Thiago Farina). Description from original changelist:
>>
>> Add ellipses to |Add| and |Edit| buttons of Search engine manager(keyword 
>> view), since they opens another window and
>> does not, for example, add or edit the selected item.
>>
>> BUG=16380
>> TEST=Open the search engine manager and see if the |Add| and the |Edit| 
>> button has the "..." in the end.
>>
>> Review URL: http://codereview.chromium.org/257053
>>
>>
>> >>
>>
>>
>

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

[chromium-dev] Re: buildbot failure in Chromium on Linux Builder (Views dbg), revision 28054

2009-10-05 Thread John Gregg 
Looks like a merge problem with my recent change to render_messages.h
regarding WebPreferences.  I can submit a fix.   -John
On Mon, Oct 5, 2009 at 3:03 PM,  wrote:

>  http://build.chromium.org/buildbot/waterfall/
>
> Automatically closing tree for "compile" on "Linux Builder (Views dbg)"
>
>
> http://build.chromium.org/buildbot/waterfall/builders/Linux%20Builder%20%28Views%20dbg%29/builds/1824
>
> Revision: 28053, 28054
> Blame list: erik...@chromium.org,fin...@chromium.org
>
>  Linux Builder (Views dbg)
> Build 
> 1824
>   update
> scripts
> stdio
> update
> stdio
> compile
> failed
> stdio
>
> Changed by: *erik...@chromium.org*
> Changed at: *Mon 05 Oct 2009 15:00:08*
> Branch: *src*
> Revision: *28053*
>
> Changed files:
>
>- *chrome/browser/extensions/extension_host.cc*
>- *chrome/browser/views/browser_bubble_win.cc*
>- *chrome/browser/extensions/extension_host.h*
>- *chrome/common/render_messages.h*
>- *chrome/test/data/extensions/samples/set_page_color/popup.html*
>
> Comments:
>
> Allow popups to close themselves with window.close().
>
> This also fixes an issue where not all of the parts of WebPreferences were 
> being serialized/deserialized across IPC.
>
> BUG=23832
> TEST=run set_page_color extension, when it sets the color, the popup
> should close
>
> Review URL: http://codereview.chromium.org/243096
>
>  Changed by: *fin...@chromium.org*
> Changed at: *Mon 05 Oct 2009 15:00:18*
> Branch: *src*
> Revision: *28054*
>
> Changed files:
>
>- *chrome/app/generated_resources.grd*
>
> Comments:
>
> Landing a patch (http://codereview.chromium.org/249054) from an external 
> contributor (Thiago Farina). Description from original changelist:
>
> Add ellipses to |Add| and |Edit| buttons of Search engine manager(keyword 
> view), since they opens another window and
> does not, for example, add or edit the selected item.
>
> BUG=16380
> TEST=Open the search engine manager and see if the |Add| and the |Edit| 
> button has the "..." in the end.
>
> Review URL: http://codereview.chromium.org/257053
>
>
> >
>
>

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

[chromium-dev] buildbot failure in Chromium on Chromium Linux x64, revision 28055

2009-10-05 Thread buildbot 
Automatically closing tree for "compile" on "Chromium Linux x64"

http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Linux%20x64/builds/913

http://build.chromium.org/buildbot/waterfall/waterfall?builder=Chromium%20Linux%20x64

--=>  Automatically closing tree for "compile" on "Chromium Linux x64"  <=--

Revision: 28052, 28053, 28054, 28055
Blame list: 
ana...@chromium.org,erik...@chromium.org,fin...@chromium.org,sidc...@chromium.org

Buildbot waterfall: http://build.chromium.org/

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

[chromium-dev] buildbot failure in Chromium on Linux Builder (Views dbg), revision 28054

2009-10-05 Thread buildbot 
Automatically closing tree for "compile" on "Linux Builder (Views dbg)"

http://build.chromium.org/buildbot/waterfall/builders/Linux%20Builder%20%28Views%20dbg%29/builds/1824

http://build.chromium.org/buildbot/waterfall/waterfall?builder=Linux%20Builder%20%28Views%20dbg%29

--=>  Automatically closing tree for "compile" on "Linux Builder (Views dbg)"  
<=--

Revision: 28053, 28054
Blame list: erik...@chromium.org,fin...@chromium.org

Buildbot waterfall: http://build.chromium.org/

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

[chromium-dev] buildbot failure in Chromium on Modules XP, revision 28045

2009-10-05 Thread buildbot 
Automatically closing tree for "net_unittests" on "Modules XP"

http://build.chromium.org/buildbot/waterfall/builders/Modules%20XP/builds/16715

http://build.chromium.org/buildbot/waterfall/waterfall?builder=Modules%20XP

--=>  Automatically closing tree for "net_unittests" on "Modules XP"  <=--

Revision: 28041, 28042, 28043, 28044, 28045
Blame list: 
jhawk...@chromium.org,nsylv...@chromium.org,pkast...@chromium.org,s...@chromium.org

Buildbot waterfall: http://build.chromium.org/

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

[chromium-dev] Re: Changed WebKit build flags, may require clobber after sync

2009-10-05 Thread Yaar Schnitman 
I fixed gyp_chromium to automatically include features_override.gypi:
http://src.chromium.org/viewvc/chrome?view=rev&revision=28035

On Mon, Oct 5, 2009 at 10:13 AM, Tony Chang  wrote:

>
> If you're getting linker errors about missing symbols for
> WebNotifications, then you're probably running gyp_chromium manually
> (which I think is most people using the make build or building 64
> bit).
>
> To fix, add -Isrc/build/features_override.gypi to gyp_chromium (see
> src/DEPS where it's added to the gclient invocation of gyp_chromium).
>
>
>
> On Mon, Oct 5, 2009 at 9:11 AM, John Gregg  wrote:
> > Hi all,
> > I checked in a change yesterday which sets ENABLE_NOTIFICATIONS=1 for the
> > Chromium build of WebKit (in features_override.gypi).  If you sync up and
> > are seeing linking errors regarding notifications, this should be fixed
> by
> > rebuilding WebCore.  Some of the build bots seem to be fine, but others
> have
> > hit this error.
> > Thanks,
> >  -John
> > >
> >
>
> >
>

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

[chromium-dev] buildbot failure in Chromium on Webkit Builder, revision 28022

2009-10-05 Thread buildbot 
Automatically closing tree for "compile" on "Webkit Builder"

http://build.chromium.org/buildbot/waterfall/builders/Webkit%20Builder/builds/17422

http://build.chromium.org/buildbot/waterfall/waterfall?builder=Webkit%20Builder

--=>  Automatically closing tree for "compile" on "Webkit Builder"  <=--

Revision: 28021, 28022
Blame list: jam...@chromium.org,jpar...@chromium.org

Buildbot waterfall: http://build.chromium.org/

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

[chromium-dev] buildbot failure in Chromium on Chromium Builder, revision 28022

2009-10-05 Thread buildbot 
Automatically closing tree for "compile" on "Chromium Builder"

http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder/builds/16661

http://build.chromium.org/buildbot/waterfall/waterfall?builder=Chromium%20Builder

--=>  Automatically closing tree for "compile" on "Chromium Builder"  <=--

Revision: 28021, 28022
Blame list: jam...@chromium.org,jpar...@chromium.org

Buildbot waterfall: http://build.chromium.org/

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

[chromium-dev] Re: build time speed improvement with solid state drive?

2009-10-05 Thread Marshall Greenblatt 
Thanks for the input everyone. I'll shop accordingly :-)

On Mon, Oct 5, 2009 at 2:27 PM, Marc-Antoine Ruel wrote:

> Marshall, don't waste money on SSD (especially not MLC SSD).
> Get 2 standard HD, put the checkout on the secondary drive, get a dual-cpu
> quad-core ht with 8+ gigs of RAM (or up to the limit you can afford but get
> at least 8 gigs of RAM and at least one quad core). Core i7 or xeon nehalem
> *highly* recommended.
>
> M-A
>
> On Mon, Oct 5, 2009 at 2:21 PM, Jeremy Orlow  wrote:
>
>> On Mon, Oct 5, 2009 at 11:14 AM, Amanda Walker wrote:
>>
>>> On Mon, Oct 5, 2009 at 2:08 PM, Marshall Greenblatt <
>>> magreenbl...@gmail.com> wrote:
>>>
 I'm putting together a new computer and I'd like to optimize my chromium
 build times :-) Is anyone currently building chromium using a solid state
 drive? Have you noticed any compile or link time speed improvements 
 relative
 to using a second traditional SATA drive?

>>>
>>> Other people can chime in about windows ssd performance, but I have an
>>> SSD in a Mac laptop that I sometimes do builds on.  Total build time is only
>>> marginally better than a traditional SATA drive (a few percent), but the
>>> machine is noticeably less sluggish doing other things during a build (when
>>> there's any disk contention happening, the faster seek time and i/o
>>> operations per second are a definite win).  But for overall build time, I've
>>> found that RAM and CPU cores make much more of a difference than the drive.
>>>
>>
>> From what I've heard, SVN and searching within a project are faster with a
>> SSD.  As for the system getting sluggish during compile: this can also be
>> solved by having a 2nd hard drive that contains all the source + build
>> files.
>>
>> >>
>>
>

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

[chromium-dev] Re: build time speed improvement with solid state drive?

2009-10-05 Thread Marc-Antoine Ruel 
Marshall, don't waste money on SSD (especially not MLC SSD).
Get 2 standard HD, put the checkout on the secondary drive, get a dual-cpu
quad-core ht with 8+ gigs of RAM (or up to the limit you can afford but get
at least 8 gigs of RAM and at least one quad core). Core i7 or xeon nehalem
*highly* recommended.

M-A

On Mon, Oct 5, 2009 at 2:21 PM, Jeremy Orlow  wrote:

> On Mon, Oct 5, 2009 at 11:14 AM, Amanda Walker wrote:
>
>> On Mon, Oct 5, 2009 at 2:08 PM, Marshall Greenblatt <
>> magreenbl...@gmail.com> wrote:
>>
>>> I'm putting together a new computer and I'd like to optimize my chromium
>>> build times :-) Is anyone currently building chromium using a solid state
>>> drive? Have you noticed any compile or link time speed improvements relative
>>> to using a second traditional SATA drive?
>>>
>>
>> Other people can chime in about windows ssd performance, but I have an SSD
>> in a Mac laptop that I sometimes do builds on.  Total build time is only
>> marginally better than a traditional SATA drive (a few percent), but the
>> machine is noticeably less sluggish doing other things during a build (when
>> there's any disk contention happening, the faster seek time and i/o
>> operations per second are a definite win).  But for overall build time, I've
>> found that RAM and CPU cores make much more of a difference than the drive.
>>
>
> From what I've heard, SVN and searching within a project are faster with a
> SSD.  As for the system getting sluggish during compile: this can also be
> solved by having a 2nd hard drive that contains all the source + build
> files.
>
> >
>

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

[chromium-dev] Re: build time speed improvement with solid state drive?

2009-10-05 Thread Jeremy Orlow 
On Mon, Oct 5, 2009 at 11:14 AM, Amanda Walker  wrote:

> On Mon, Oct 5, 2009 at 2:08 PM, Marshall Greenblatt <
> magreenbl...@gmail.com> wrote:
>
>> I'm putting together a new computer and I'd like to optimize my chromium
>> build times :-) Is anyone currently building chromium using a solid state
>> drive? Have you noticed any compile or link time speed improvements relative
>> to using a second traditional SATA drive?
>>
>
> Other people can chime in about windows ssd performance, but I have an SSD
> in a Mac laptop that I sometimes do builds on.  Total build time is only
> marginally better than a traditional SATA drive (a few percent), but the
> machine is noticeably less sluggish doing other things during a build (when
> there's any disk contention happening, the faster seek time and i/o
> operations per second are a definite win).  But for overall build time, I've
> found that RAM and CPU cores make much more of a difference than the drive.
>

>From what I've heard, SVN and searching within a project are faster with a
SSD.  As for the system getting sluggish during compile: this can also be
solved by having a 2nd hard drive that contains all the source + build
files.

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

[chromium-dev] Re: build time speed improvement with solid state drive?

2009-10-05 Thread Amanda Walker 
On Mon, Oct 5, 2009 at 2:08 PM, Marshall Greenblatt
wrote:

> I'm putting together a new computer and I'd like to optimize my chromium
> build times :-) Is anyone currently building chromium using a solid state
> drive? Have you noticed any compile or link time speed improvements relative
> to using a second traditional SATA drive?
>

Other people can chime in about windows ssd performance, but I have an SSD
in a Mac laptop that I sometimes do builds on.  Total build time is only
marginally better than a traditional SATA drive (a few percent), but the
machine is noticeably less sluggish doing other things during a build (when
there's any disk contention happening, the faster seek time and i/o
operations per second are a definite win).  But for overall build time, I've
found that RAM and CPU cores make much more of a difference than the drive.

--Amanda

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

[chromium-dev] build time speed improvement with solid state drive?

2009-10-05 Thread Marshall Greenblatt 
Hi All,

I'm putting together a new computer and I'd like to optimize my chromium
build times :-) Is anyone currently building chromium using a solid state
drive? Have you noticed any compile or link time speed improvements relative
to using a second traditional SATA drive?

Thanks,
Marshall

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

[chromium-dev] Re: Google Blogoscoped author tries out Chrome app shortcuts

2009-10-05 Thread Marc-Antoine Ruel 
[+chromium-dev]

On Mon, Oct 5, 2009 at 12:36 PM, Philipp Lenssen 
wrote:
> Hi Peter and Marc-Antoine!
>
> (forwarding my post via email as the Google Groups discussion is
moderated)

You need to subscribe first to not be moderated, e.g. ignored.


> I'm glad to see the issues being looked at!
>
> The Fixedsys font problem is this: In my CSS, I have the line
>font-family: fixedsys, consolas, monospace;
> but Chrome ignores the first font, and jumps to Consolas (Firefox
> finds Fixedsys fine). It being a system font might be part of the
> issue, I can also not locate Fixedsys in Chrome's monospace font
> options dialog.

No idea about this one in particular. Since this is on Windows, it may be
interesting to take a look at. Can you file a bug at http://new.crbug.com ?


>> He just needs to learn how to create an application shortcut. Copy a
>> chrome shortcut on the desktop, rename it, right click on it,
>> properties, edit the command line to add the arguments wanted.
>
> Could you please guide me through the steps, did you try associating
> files? Just a basic edited shortcut doesn't do the job for me, as
> Windows (Vista) will set up the file association -- which I need to
> open files system wide with double click -- with the source exe when
> picking the shortcut... i.e. with basic Chrome, not Chrome App
> (dragging the file over the shortcut behaves somewhat better, but I
> didn't further explore this route as it's not a solution).
>
> To clarify, my goal is:
> - set up Windows (Vista) so that all .foo files (like myfile.foo) will
> automatically be opened with Chrome App at the location
> http://example/#path-to-foo-file (e.g.
> http://example/#C:\somefolder\myfile.foo).
>
> My current suboptimal workaround as mentioned is associating my files
> with a CMD file which reads:
> C:\Users\...\Chrome\Application\chrome.exe --app="http://example/#%1";

Ok I didn't understand what you wanted to do correctly at first. The easiest
fix is by editing the registry entry. I made it do a websearch as an example
but this is obviously useless as-is. The important part is the
type\shell\open\command\@ (default) registry value, by default it uses «--
"%1"». I just changed this part to use --app and a prebacked url instead.
You need to replace %USERPROFILE% by your user profile path.

--- CUT HERE ---
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.foo]
@="foo_auto_file"

[HKEY_CLASSES_ROOT\foo_auto_file]
@="Web Search"

[HKEY_CLASSES_ROOT\foo_auto_file\shell]

[HKEY_CLASSES_ROOT\foo_auto_file\shell\open]

[HKEY_CLASSES_ROOT\foo_auto_file\shell\open\command]
@="\"%USERPROFILE%\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe\"
--app \"http://www.google.com/search?q=%1\"";


I don't think Google Chrome should be blamed by someone hooking up weird
file association like this. :)

M-A

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

[chromium-dev] Re: Scalability

2009-10-05 Thread Steven Knight 
The variable name is actually just 'library'.  The default is set in
build/common.gypi.  You can either change the default variable right in
build/common.gypi or set the environment variable
GYP_DEFINES=library=shared_library to get a shared library build.
(I have it modified locally in one of my checked-out Linux trees for
periodic sanity checks that Linux at least nominally builds with shared
libraries.  IIRC, a lot of the Linux folks use shared library builds
regularly, for the much faster link times.)
--SK

On Mon, Oct 5, 2009 at 9:00 AM, Mark Mentovai  wrote:

>
> If anyone want to work on this, we've left some breadcrumbs behind by
> declaring libraries that could be built as either static or shared as
> a GYP variable named library_type.  It expands to static_library by
> default, but the intention was to make it easy to switch to a shared
> library build by flipping it to shared_library.  I'm sure there's a
> bunch of work to be done even with that switch flipped, but it might
> be a good start if anyone's interested.
>
> Mark
>
> Evan Martin wrote:
> > On Fri, Oct 2, 2009 at 8:26 AM, Marc-Antoine Ruel 
> wrote:
> >> is linking. To give you an idea, here's a truncated dir list:
> >> (...)
> >> 10,223,616 dump_cache.exe
> >> 10,309,632 fetch_client.exe
> >> 10,600,448 net_perftests.exe
> >> 12,406,784 sync_unit_tests.exe
> >> 14,966,784 net_unittests.exe
> >> 22,118,400 mini_installer.exe
> >> 55,029,760 tab_switching_test.exe
> >
> > Does anyone (not necessarily you :P) have building a web of .dlls in
> > their plans?
> > I've seen a number of patches from mmoss to get that working on Linux
> > with the intent of using it on buildbots...
>
> >
>

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

[chromium-dev] Re: Changed WebKit build flags, may require clobber after sync

2009-10-05 Thread Tony Chang 

If you're getting linker errors about missing symbols for
WebNotifications, then you're probably running gyp_chromium manually
(which I think is most people using the make build or building 64
bit).

To fix, add -Isrc/build/features_override.gypi to gyp_chromium (see
src/DEPS where it's added to the gclient invocation of gyp_chromium).



On Mon, Oct 5, 2009 at 9:11 AM, John Gregg  wrote:
> Hi all,
> I checked in a change yesterday which sets ENABLE_NOTIFICATIONS=1 for the
> Chromium build of WebKit (in features_override.gypi).  If you sync up and
> are seeing linking errors regarding notifications, this should be fixed by
> rebuilding WebCore.  Some of the build bots seem to be fine, but others have
> hit this error.
> Thanks,
>  -John
> >
>

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

[chromium-dev] Changed WebKit build flags, may require clobber after sync

2009-10-05 Thread John Gregg 
Hi all,
I checked in a change yesterday which sets ENABLE_NOTIFICATIONS=1 for the
Chromium build of WebKit (in features_override.gypi).  If you sync up and
are seeing linking errors regarding notifications, this should be fixed by
rebuilding WebCore.  Some of the build bots seem to be fine, but others have
hit this error.

Thanks,
 -John

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

[chromium-dev] Re: Google Blogoscoped author tries out Chrome app shortcuts

2009-10-05 Thread Evan Martin 

On Sun, Oct 4, 2009 at 5:46 PM, Marc-Antoine Ruel  wrote:
>> Sort of crucial: Chrome won’t accept my system font definition, Fixedsys,
>> while Firefox has no problems with it and loads it fine. Apparently Chrome
>> doesn’t like system fonts, but the TrueType replacements I found for
>> Fixedsys don’t look like the real thing. Anyone knows a solution?
>>
>> I don't understand the problem description well enough to take action here.
>
> I'm pretty sure block bitmap fonts. IIRC, this is also an issue with
> some asian fonts. Maybe I'm wrong since I couldn't find a bug about
> it. (Maybe only related to printing after all)

On Linux at least we don't allow any bitmap fonts, because (as I
recall) of some disconnect between the time we request a font name and
a later point where we request the font size.

Like most font issues, half of our bug reports (particularly from CJK
users) are "your non-bitmap fonts look worse than Firefox" and the
other half are "your smooth antialiased fonts look better than
Firefox".

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

[chromium-dev] Re: Scalability

2009-10-05 Thread Mark Mentovai 

If anyone want to work on this, we've left some breadcrumbs behind by
declaring libraries that could be built as either static or shared as
a GYP variable named library_type.  It expands to static_library by
default, but the intention was to make it easy to switch to a shared
library build by flipping it to shared_library.  I'm sure there's a
bunch of work to be done even with that switch flipped, but it might
be a good start if anyone's interested.

Mark

Evan Martin wrote:
> On Fri, Oct 2, 2009 at 8:26 AM, Marc-Antoine Ruel  wrote:
>> is linking. To give you an idea, here's a truncated dir list:
>> (...)
>> 10,223,616 dump_cache.exe
>> 10,309,632 fetch_client.exe
>> 10,600,448 net_perftests.exe
>> 12,406,784 sync_unit_tests.exe
>> 14,966,784 net_unittests.exe
>> 22,118,400 mini_installer.exe
>> 55,029,760 tab_switching_test.exe
>
> Does anyone (not necessarily you :P) have building a web of .dlls in
> their plans?
> I've seen a number of patches from mmoss to get that working on Linux
> with the intent of using it on buildbots...

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

[chromium-dev] Re: Scalability

2009-10-05 Thread Marc-Antoine Ruel 

Yes, Nicolas is working on making webkit.dll. It's painful to do; I
know, I tried last year. :)

On Mon, Oct 5, 2009 at 11:42 AM, Evan Martin  wrote:
> On Fri, Oct 2, 2009 at 8:26 AM, Marc-Antoine Ruel  wrote:
>> is linking. To give you an idea, here's a truncated dir list:
>> (...)
>> 10,223,616 dump_cache.exe
>> 10,309,632 fetch_client.exe
>> 10,600,448 net_perftests.exe
>> 12,406,784 sync_unit_tests.exe
>> 14,966,784 net_unittests.exe
>> 22,118,400 mini_installer.exe
>> 55,029,760 tab_switching_test.exe
>
> Does anyone (not necessarily you :P) have building a web of .dlls in
> their plans?
> I've seen a number of patches from mmoss to get that working on Linux
> with the intent of using it on buildbots...
>

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

[chromium-dev] Re: Debugging glibc malloc "double free or corruption"

2009-10-05 Thread Evan Martin 

On Fri, Oct 2, 2009 at 7:32 AM, spotrh  wrote:
> A Fedora user recently reported that loading www.msnbc.com causes the
> "Oh snap!" and unhappy mac, which I was able to reproduce.
>
> The gory details are filed here:
> http://code.google.com/p/chromium/issues/detail?id=23635
>
> I hate to just open bugs and say "go fix it!", at least not without
> significantly narrowing down the problem.

Since this is a crash on a high-profile page, marking the bug with
priority P1 will help developers find it quickly.  In this particular
case it sounds like it's maybe a gcc 4.4 issue which we won't run into
with Google Chrome builds so mailing the list seems reasonable to me
too.

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

[chromium-dev] Re: Scalability

2009-10-05 Thread Evan Martin 

On Fri, Oct 2, 2009 at 8:26 AM, Marc-Antoine Ruel  wrote:
> is linking. To give you an idea, here's a truncated dir list:
> (...)
> 10,223,616 dump_cache.exe
> 10,309,632 fetch_client.exe
> 10,600,448 net_perftests.exe
> 12,406,784 sync_unit_tests.exe
> 14,966,784 net_unittests.exe
> 22,118,400 mini_installer.exe
> 55,029,760 tab_switching_test.exe

Does anyone (not necessarily you :P) have building a web of .dlls in
their plans?
I've seen a number of patches from mmoss to get that working on Linux
with the intent of using it on buildbots...

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