[sugar] google gears rpm update

David Van Assche dvanassche
Thu Jul 10 23:58:35 EDT 2008


Ok... finally fixed the compile problem found above. Turns out the
libgtk-x11-2.0 had been compiled with a Ubuntu 6.06, and when I replaced it
with one compiled on 8.04, the build went through smoothly leaving me with
the desired gears 4.3.0 .xpi... The google gears guys don't really check the
Linux version too much... but for anyone desiring to build this from scratch
the commands for Ubuntu 8.04 are:

sudo svn checkout *http*://gears.googlecode.com/svn/trunk/ gears-read-only
cd gears-read-only/gears
sudo chmod o+x ../third_party/gecko_1.9/linux/gecko_sdk/bin/xpidl
sudo chmod o+x ../third_party/gecko_1.9/linux/gecko_sdk/bin/xpt_link
[should work with other versions and distros too I guess]
sudo cp /usr/lib/libgtk-x11-2.0.so ../third_party/gtk/linux/lib/
libgtk-x11-2.0.so
sudo make BROWSER= CC=gcc-3.4 CXX=g++-3.4 MKSHLIB=g++-3.4 MODE=opt

The compiled .xpi file is then found in gears/bin-opt/installer/
as
gears-linux-opt-0.4.3.0.xpi (or whatever version is presently out)

For Fedora 9, instructions are the same except the make string is:
sudo make BROWSER= CC=gcc34 CXX=g++34 MKSHLIB=g++34 MODE=opt

That means I can now finish the rpm...!


Kind Regards,
David Van Assche

On Wed, Jul 9, 2008 at 3:08 PM, David Van Assche <dvanassche at gmail.com>
wrote:

>
>> Good. So you have a build that gets you the right GG for FF3 on F9 -
>> almost there :-) If you are testing with Browse, bear in mind that we
>> may need different tweaks - as I suspect Browse is closer to FF2 than
>> to FF3, but Tomeu will probably know better. Of course, we first need
>> the FF3 targetted RPM - easier to test, and to get into Fedora.
>>
>
> yep, as soon as there is a working svn branch, I'll be able to inject the
> gg code into FF3 quite easily (xulrunner-1.9 --install-app
> /path/to/.xpi_file) does this...
>
>
>>
>> > 2. This leads me to the conclusion that there must be some files being
>> > generated elsewhere that somehow activate the gears libraries...
>>
>> Or that you have an API mismatch (if you are testing with Browse
>> rather than with other FF3 install) or perhaps missing libs?
>>
>
> I've been testing on both FF3 and browse, with tomeu's help...
>
>
>>
>> > 3. Taking out the BROWSER=FF3 and leaving it BROWSER= makes the build
>> crash
>> > with:
>>
>> Ugh! Maybe that is a broken revision?
>>
>
> According to the comments on the svn trunk, they say they fixed this error
> for linux... so I guess it is broken, and the google gears guys know it
> exists, but aren't testing their fixes entirely... because I downloaded the
> latest trunk and the exact one that contains the linux fix comment, and the
> break is in the same place as before...
>
>
>>
>> > 4. Seeing as Gears is currently a beta product for developers only, this
>>
>> Let's try for the right answer :-) The XPI is probably a zipfile, grab
>> it, unzip it and see what's there...
>>
>
> This I have done, and was using in order to create the spec file... but
> there are many files missing in the svn trunk build... so wait for the
> google gears devs we must...
>
>
>>
>> > 1. wait till the gears devs give me an answer/fix the compile so all
>> items
>> > get created
>>
>> Let's try for that :-) we'll hopefullyuse that rpm for many years to
>> come...
>>
>
> wow... this has been quite a journey... I'll make sure I document the
> procedure so hopefully it will help others wanting to create plugins for
> browse and FF3 as rpms...
>
>
>>
>> m
>> --
>>  martin.langhoff at gmail.com
>>  martin at laptop.org -- School Server Architect
>>  - ask interesting questions
>>  - don't get distracted with shiny stuff - working code first
>>  - http://wiki.laptop.org/go/User:Martinlanghoff
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/sugar/attachments/20080711/12d947c2/attachment-0001.htm 



More information about the Sugar-devel mailing list