Building main on RedHat Enterprise Linux 4: Difference between revisions
| Line 4: | Line 4: | ||
./buildThirdParty.sh | ./buildThirdParty.sh | ||
The build process can take quite a while. If a specific component fails, the script will continue to build the third party components. You should monitor the build process for errors. If a component fails, you should stop the build, and fix the error, then rebuild. See troubleshooting for more | The build process can take quite a while. If a specific component fails, the script will continue to build the third party components. | ||
You should monitor the build process for errors. You can do this by tailing the build log: | |||
tail -f /tmp/ThirdParty.make.log | |||
If a component fails, you should stop the build, and fix the error, then rebuild. See [http://wiki.zimbra.com/index.php?title=Building_Zimbra_using_Perforce#Troubleshooting troubleshooting] for more help. | |||
Revision as of 18:01, 29 January 2008
Building Third Party
Once you have followed the ReadMe located here: http://wiki.zimbra.com/index.php?title=Main_README we must now build the third party components. Third party components must be built before ZCS is built.
cd /home/public/p4/zcs/FRANKLIN/ThirdParty ./buildThirdParty.sh
The build process can take quite a while. If a specific component fails, the script will continue to build the third party components. You should monitor the build process for errors. You can do this by tailing the build log:
tail -f /tmp/ThirdParty.make.log
If a component fails, you should stop the build, and fix the error, then rebuild. See troubleshooting for more help.
