The day you've been waiting for is here. We are in the process of landing the changes to upgrade the mac build system to CodeWarrior Pro7. The advantages are numerous, and include:
- XML project files - one set of tools for carbon/classic - debugging on OSX - building natively on OSX What does this mean for you? If you build on Mac, you need to get the new tools. The old Pro5 tools ARE NO LONGER SUPPORTED on the trunk. For those inside of NSCP, a separate email will be sent telling you how and where to get the tools (the regular place is no longer the regular place, IS screwed us royally when reworking bldg20). If you're outside the building, the mac build page will be updated within the next day or so. http://www.mozilla.org/build/mac.html http://www.mozilla.org/ports/fizzilla/cfm.html Even if you don't build on mac, you need to understand the changes to the build system. Pro7 continues to use binary projects, but they are imported from XML-based project files (the imported project will have an underscore prexifing the project name, ie "_Widget.mcp"). A project is re-imported every time its corresponding XML file changes on disk by the build scripts. The easiest way to add/remove files from the build is still to edit the project files with the IDE as before, but now you must EXPORT the project to XML and check it in. DO NOT check in the modified binary project file, as it will be ignored and overwritten. Camelot will, in the short term, be taken down until it can be retooled to edit the XML files. In the meantime, you have two options for adding/removing files to the mac build: 1) Find someone with a mac, get them to make changes and export the XML project for you to include in your patch 2) Edit the XML file yourself. Note that (2), while being technically possible, isn't childs-play. The XML files can be very large and confusing and you may mess up the first few times you try it. Remember: DO NOT check in the binary project file. You will break the build. We'll be watching the npm.mac newsgroup if people have problems. We know this is a big change, but we feel that it's worth it to both mac and non-mac developers in the Mozilla community. -- Mike Pinkerton Mac Browser Weenie [EMAIL PROTECTED] http://people.netscape.com/pinkerton
