Re: xforms build help

I don't know what step did it, as all the config settings were pretty much 
there (maybe the pull_all got something that I didn't have before I tried 
building seamonkey), but it worked! I really appreciate the hand holding :)

I'll let you know what tests I get created shortly. Thanks again.
-Andrew

"Aaron Reed" <[email protected]> wrote in message 
news:[email protected]...
> Ok, I just did a Firefox build.
>
> I did it just like a mozilla build, other than I had to change these 
> things:
>
> 1) Added ". $topsrcdir/browser/config/mozconfig" as my top, non-commented 
> line in .mozconfig
> 2) in my .mozconfig I changed MOZ_CO_PROJECT and --enable-application to 
> be browser instead of suite
> For example:
> mk_add_options MOZ_CO_PROJECT=browser
> ac_add_options --enable-application=browser
> 3)in addition to checking out mozilla/client.mk I checked out 
> mozilla/browser/config/mozconfig.  THEN I did "cd mozilla" and then 
> "make -f client.mk pull_all" followed by "make -f client.mk build".
>
> and remember that you need: 
> ac_add_options --enable-extensions="default,xforms,schema-validation" in 
> your .mozconfig to build xforms.
>
> After building, XForms worked for me just fine.
>
> Please let me know if you still have problems.
>
> --Aaron
>
> Andrew Douglas wrote:
>> I've got my build environment setup on win32 working great. Now I want 
>> more. Any help would be greatly appreciated.
>>
>> 1. Building seamonkey locally with xforms support works great, but for 
>> some reason building firefox with xforms support built in doesn't seem to 
>> work. Is it possible to do this or is there anything special I need to 
>> do?
>> If this is a dumb newbie question I apologize... it's also possible that 
>> I did something stupid.. who knows..
>> If I'm stuck on seamonkey that's okay, but I'm more of a firefox kinda 
>> guy.
>> 2. Are there pending patches that you have included in the xpi build or 
>> any that you would recommend applying (gecko or xforms related).. there 
>> appears to me to be quite a few in the works.. so i feel a bit over my 
>> head.. :)
>> For example the svg status blog update that says not only what's checked 
>> in but what's "lurking". I wouldn't mind helping with maintaining 
>> something like that if it would be helpful and folks are interested.
>> 3. I'm very interested in working with compound documents - namely svg 
>> and xforms. Before I jump in with both feet, are there any really big 
>> holes in this that I should avoid? I'll post any bugs I run into 
>> obviously, just trying to avoid too much wasted effort.
>>
>> Any help would be greatly appreciated.
>> -Andrew