I see.  My thinking was to be able to unblock our team more quickly by 
fixing compatibility issues right away rather than waiting for an official 
update, which can take several days.  Of course we aren't really blocked, 
there is just some thrash for the folks who take FF updates immediately.

This would be on Ubuntu Linux.  I would not be inclined to go to the 
trouble (the thrash isn't that bad) unless I could contribute.  If in order 
to submit a patch I would be required to build/test on Windows, ain't 
happening, but if Linux is sufficient, then yeah, if you could put out 
non-Google-specific build instructions, that would be great.

Thanks,
Lee


On Tuesday, November 26, 2013 2:30:36 PM UTC-8, Brian Slesinsky wrote:
>
> It's fairly complicated to build because we have to do a C++ compile 
> against the latest XulRunner SDK on three platforms and assemble the 
> results. Furthermore, converting a new XulRunner SDK into the format needed 
> to do the build is a partially manual process. But if you just want to 
> build on one platform (Linux or Mac, preferably) for a Firefox release we 
> already support, it should be easier and that should be enough to get 
> started. And yes, we'd like to accept patches.
>
> I have a document with the build procedure, but it contains 
> Google-specific steps. If you're seriously interested then I could publish 
> a cleaned-up version.
>
> - Brian
>
> On Tuesday, November 26, 2013 8:33:00 AM UTC-8, navels wrote:
>>
>> What are the general steps involved to build the firefox plugin?  How 
>> involved are the fixes to maintain compatibility with new FF releases? 
>>  (I'm sure it depends on the release, but is there a general level of 
>> complexity.)
>>
>> Would I be able to contribute patches?
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to