Building a minimal content module.

192 views
Skip to first unread message

Venkata Ramanan

unread,
Mar 24, 2014, 2:29:40 PM3/24/14
to chromium...@chromium.org
Hi,

Is there a target/way to build a minimal content module? I basically need a small footprint (interms of binary size and memory) chromium browser. One another constraint that I have is that I cannot have shared libraries in my environment. The steps that I have taken are..

1) Using the content_shell instead of the whole chromium
2) Building the content_shell statically by removing all the shared library that it uses and link with the corresponding static version.

The issue I face is that the contet_shell binary that I get is huge (~1.5 gig, debug build) and doesnt suite my environment. I just need a content_shell (or any other alternative) which is as light weight as possible. 

Does checking out an old version of chromium help (pre multiprocess arch or something)? If so any suggestions on the version ??

Any other suggestions?

Thanks,
Venkat.

Torne (Richard Coles)

unread,
Mar 25, 2014, 9:14:37 AM3/25/14
to s.ramana...@gmail.com, Chromium-discuss
On 24 March 2014 18:29, Venkata Ramanan <s.ramana...@gmail.com> wrote:
Hi,

Is there a target/way to build a minimal content module? I basically need a small footprint (interms of binary size and memory) chromium browser. One another constraint that I have is that I cannot have shared libraries in my environment. The steps that I have taken are..

1) Using the content_shell instead of the whole chromium
2) Building the content_shell statically by removing all the shared library that it uses and link with the corresponding static version.

The issue I face is that the contet_shell binary that I get is huge (~1.5 gig, debug build) and doesnt suite my environment. I just need a content_shell (or any other alternative) which is as light weight as possible. 

The binary you're looking at is unstripped; if you strip the debug information from it it will remove 95%+ of the size. Debug information for large C++ projects is extremely big. You should also build Release if you want to actually examine the real size, since even with the debug symbols stripped, the debug version still has extra code included.
 
Does checking out an old version of chromium help (pre multiprocess arch or something)? If so any suggestions on the version ??

There is no version of chrome pre-multiprocess architecture; chrome has always worked that way. The content layer has only existed relatively recently, so old versions of chromium will not work for your purposes at all. Also, you should never use any old version for production code, since browser code is subject to very frequent security issues and outdated code is a risk to your users.
 

Any other suggestions?

Thanks,
Venkat.

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


Reply all
Reply to author
Forward
0 new messages