Try to strip your image.
> --
> Chromium OS Developers mailing list: chromiu...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
On Saturday, 14 July 2012 17:44:58 UTC+5:30, Simon Hong wrote:
> Try to strip your image.
>
> On Jul 14, 2012 9:04 PM, "Ashish S" <<a href="
>
> >
>
> > Hello,
>
> >
>
> > I built chromium browser targeting arm within the chromiumos chroot.
>
> > The generated exe is so large(1.2GB in release mode) it cant fit in my target.
>
> > The x86-target exe in release mode came out to be only 100Mb..
>
> > How can i built an exe thats small enough to land on my target board.
>
> > i remember exes for arm under 60mb.. and one cant ship a software with main exe this big..
>
> > whats wrong.. and what can be done.
>
> > Thanks.
>
> >
>
> > --
>
> > Chromium OS Developers mailing list: <a href="mailto:chromiu...@chromium.org" target="_blank">chromiu...@chromium.org</a>
>
> > View archives, change email options, or unsubscribe:
>
> > <a href="http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en" target="_blank">http://groups.google.com/a/<WBR>chromium.org/group/chromium-<WBR>os-dev?hl=en</a>
>
> </p>
View archives, change email options, or unsubscribe:
Ashish:
If you run strip, I think you'll lose debug symbols, and you won't be
able to step through it with gdb. This may or may not be what you
Or you could also sshfs-mount it on target...
On Mon, Jul 16, 2012 at 3:16 PM, asharif <> wrote:
On Mon, Jul 16, 2012 at 1:57 PM, Simon Que <> wrote:
Ashish:
If you run strip, I think you'll lose debug symbols, and you won't be
able to step through it with gdb. This may or may not be what youYou can still debug your binary using USE="splitdebug" and use gdbserver on the remote machine.
want to do -- it sounds like you're in a development workflow and you
might end up needing to debug it.
Here's an alternative solution: If you have a normal Chromebook, you
can move the /opt/google/chrome folder to /usr/local/chrome. Then
just create a symlink at /opt/google/chrome to /usr/local/chrome. On
a Chromebook, /usr/local will have enough space for that 1.2 GB
executable.
Of course, this is only for development purposes. On the system that
you ship, you will have to strip it (or build with build_packages) and
put it in the proper location.
Simon
>> > href="mailto:chromium-os-dev@chromium.org"
>> > target="_blank">chromium-os-d...@chromium.org</a>
>> >
>> > > View archives, change email options, or unsubscribe:
>> >
>> > > <a
>> > href="http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en"
>> > target="_blank">http://groups.google.com/a/<WBR>chromium.org/group/chromium-<WBR>os-dev?hl=en</a>
>> >
>> > </p>
>>
>> --
>> Chromium OS Developers mailing list: chromiu...@chromium.org
>> View archives, change email options, or unsubscribe:
>> http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
>
>
> --
> Chromium OS Developers mailing list: chromiu...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
I generally increase my rootfs size for every image that I build.
Hello again...The strip trick did make the exe small but it cant be debugged as pointed out by people here already..so for debugging purposes in am using sshfs . I am trying to debug on virtualbox..the size of the exe is around 1.4G and while running gdb /tmp/chrome chrome , the gdb process gets stuck at the "Reading symbols from /opt/google/chrome/chrome..." step..
I'm using Linux and cross compiling to Linux/ARM64 in release mode. My out/build comes out to 1.3GB in release mode with symbols = 0. is there a way to reduce the size further? I'm a noob so please tell me what I am missing.
--