Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0


Contributing to WOLips

The first step of programming WOLips is Building WOLips. Once WOLips is properly built, then you're off to development. Development inside of Eclipse will give you the most power, but to take advantage of it will require a few additional steps when you want to do a full build again.

Building WOLips after PDE Development

The main problem is that the PDE build of WOLips gives you a top level "projects" project that allows you to do a full build (which CONTAINS the plugin folders), but also checks out top level projects for each plugin to take advantage of PDEyou all the plugins, but to deploy you need to build the "woproject" top-level project from Subversions, which CONTAINS the same plugins that you have checked-out as individual projects. What that means is that you will be mainly working in the top level plugin projects, but deploying from the your "projects" project which won't have your changeswoproject" project will become out of sync as a result. When it comes time to deploy again, you will need to either cvs commit your changes and update your "projectswoproject" project (if your changes were committed to CVS), or to get those changes; or, you will need to manually copy your plugin project changes on top of the corresponding folders in your projects/wolips/pluginschanges over to the woproject project.

Once your changes are updated in "woproject", you can follow the build instructions in the "Checking out and Building inside of Eclipse for Deployment" section of Building WOLips.

One problem you might run into is that your build number doesn't increment and you cannot update your plugins from the update site if that happens (because the versions are the same). The quick fix for this is to manually change the value in build.version inside of the woproject project prior to rebuilding.