Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
C5.2-32bPAE-Sg-buildZCSmain.tgz-README.txt | 2009-09-03 | 2.3 kB | |
Totals: 1 Item | 2.3 kB | 0 |
This VMware image exists to help skip the hassle of setting up a dedicated build box. Virtual Hardware compatilability level is set to 7 so VMware Server 2, VMware Workstation 6.5 or VMware Player 2.5 should work. CentOS 5.2 (+updates to .3) Kernel 2.6.18 with Physical Address Extensions so more than 4GB of ram is supported - set to 1GB RAM w/ 10-15GB HD on VMWare Server 2 Users/Passwords are root/zimbra or zcs/zimbra. There's 6.0.1_GA_1770 completed in /home/public/p4/main/ZimbraBuilds & the i386 directory. Might have to remove that or run 'make clean' in /home/public/p4/main/ZimbraBuild before running another since space is tight, we'll make HD size bigger next time. For help see http://wiki.zimbra.com/index.php?title=Building_Zimbra_using_Perforce & http://www.zimbra.com/forums/developers As well as /home/public/p4/main/README.buildZCS You can use P4 to put new code in /home/public/p4/main or manually edit your desired content. (If making frequent changes/want quick testing, a dev-install would be more prudent.) ./p4 -u public -P public1234 -c public-view sync -f //depot/zcs/BRANCH/... Java 1.6 is pre-copied to /home/public/p4/main/ZimbraBuilds/ThirdPartyBuilds/i386/java Ant is configured. /etc/profile defines paths should you need to change PERLLIB & RELEASE (like GNR or FRANKLIN instead of main) or modify P4 settings for automatic grab. To kickoff a build: root /home/public/p4/main/ZimbraBuilds ./buildZCS.sh -t if you want to build ThirdParty as well To build Desktop it's -d, however you must have your own install4j. CPAN for Perl will default to yahoo, you can enter another as desired at the prompt or specify -p. Curl is already built, but if you start completely fresh contents you may need to open another terminal and do a /home/public/p4/main/ThirdParty/curl 'make' after Perl completes (towards the end of ThirdParty but before Zimbra server/web-client starts). Amavisd won't appear in /opt/zimbra, but it'll be in the binary once you install. To append any info to the VERSION_TAG modify /home/public/p4/main/ZimbraBuilds/defs/global.def (CentOS5.def is a copy of RHEL5.def) Output binary is located at /home/public/p4/main/ZimbraBuilds/i386 preresequite.txt contains a list of common dependencies should you want to replicate a build enviroment on your own system.