Re: [chromium-dev] Faster linking for chromium on ubuntu
On Thu, Dec 31, 2009 at 7:24 PM, n179911 n179...@gmail.com wrote:
On Thu, Dec 31, 2009 at 3:17 PM, Dan Kegel d...@kegel.com wrote:
On Thu, Dec 31, 2009 at 3:14 PM, n179911 n179...@gmail.com wrote:
And I have put 'shared' library in my include gypi file
$ more ~/.gyp/include.gpyi
{'variables': {
'library': 'shared_library',
}}
How can I make sure that it is building in shared library and using
the gold linker?
I find linking chromium is still take a long time (~ 10 minutes) on my
machine.
Is it definitely the chrome link command that is taking 10 minutes, or
linking in general? Some of the shared libs, especially in debug
build, are very large, so will still take a while to link. The main
benefit is that the actual executables, like chrome, test_shell, etc.,
will no longer duplicate that shared lib code, so collectively they
should be much smaller and link much faster.
Did you rerun gyp, e.g. with the command
glient runhooks --force
after changing ~/.gyp/include.gypi ?
Yes, I did run 'glient runhooks --force' before I run 'make
out/Debug/chrome' again.
When I build chromium as a shared library, will the result binary(ies)
be different, is there something I can check to make sure the chromium
I built is 'shared library'?
Do you have a lib.target directory full of .so files in your build
output? Does 'ldd chrome | grep libv8' match anything? If so, you have
a proper shared library build.
Michael
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
[chromium-dev] Faster linking for chromium on ubuntu
Hi,
I have installed gold linker mentioned here:
http://code.google.com/p/chromium/wiki/LinuxFasterBuilds
And I have put 'shared' library in my include gypi file
$ more ~/.gyp/include.gpyi
{'variables': {
'library': 'shared_library',
}}
How can I make sure that it is building in shared library and using
the gold linker?
I find linking chromium is still take a long time (~ 10 minutes) on my machine.
Thank you for any ideas.
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
Re: [chromium-dev] Faster linking for chromium on ubuntu
On Thu, Dec 31, 2009 at 3:14 PM, n179911 n179...@gmail.com wrote:
And I have put 'shared' library in my include gypi file
$ more ~/.gyp/include.gpyi
{'variables': {
'library': 'shared_library',
}}
How can I make sure that it is building in shared library and using
the gold linker?
I find linking chromium is still take a long time (~ 10 minutes) on my
machine.
Did you rerun gyp, e.g. with the command
glient runhooks --force
after changing ~/.gyp/include.gypi ?
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
Re: [chromium-dev] Faster linking for chromium on ubuntu
On Thu, Dec 31, 2009 at 3:17 PM, Dan Kegel d...@kegel.com wrote:
On Thu, Dec 31, 2009 at 3:14 PM, n179911 n179...@gmail.com wrote:
And I have put 'shared' library in my include gypi file
$ more ~/.gyp/include.gpyi
{'variables': {
'library': 'shared_library',
}}
How can I make sure that it is building in shared library and using
the gold linker?
I find linking chromium is still take a long time (~ 10 minutes) on my
machine.
Did you rerun gyp, e.g. with the command
glient runhooks --force
after changing ~/.gyp/include.gypi ?
Yes, I did run 'glient runhooks --force' before I run 'make
out/Debug/chrome' again.
When I build chromium as a shared library, will the result binary(ies)
be different, is there something I can check to make sure the chromium
I built is 'shared library'?
Thank you.
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
