That's more or less it to build against existing source and plugin sdks. Upgrading to a new version is certainly more involved due to the repackaging of the original SDK, updating the makefile, manifest, and rdf install template in the easy case. In the hard case it involves dealing with breaking API changes from the new version :P
Though, if you just care about building a single platform locally, that takes away most of the repackaging headaches. It sounds like there may be sufficient demand for instructions for this use case (e.g. when we are lagging a release), so I'll mark that as a TODO for me to write up a wiki entry on this subject. On Fri, Aug 26, 2011 at 4:26 AM, Thomas Broyer <[email protected]> wrote: > Is anything more than > http://code.google.com/p/google-web-toolkit/source/browse/trunk/plugins/README.txt > and > http://code.google.com/p/google-web-toolkit/source/browse/trunk/plugins/xpcom/README.txt > needed? > > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/iavfWWhp1xoJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
