Make alpha: Difference between revisions
From genomewiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
After a new browser feature is developed the <B>'make alpha'</B> is used to deliver this feature to the genome-test browser to allow QA and other users of genome-test to begin testing the new feature. | After a new browser feature is developed the <B>'make alpha'</B> is used to deliver this feature to the genome-test browser to allow QA and other users of genome-test to begin testing the new feature. | ||
To use the <B>'make alpha'</B> procedure, keep in mind the following: | |||
<UL> | |||
<LI>use a local filesystem to the development machine to save compile time</LI> | |||
<LI>use a completely clean checkout of the source tree to use only top-of-tree source</LI> | |||
<LI>email notify browser staff when install is done so everyone is aware that genome-test has changed</LI> | |||
</UL> | |||
[[Category:Browser Development]] | [[Category:Browser Development]] | ||
Revision as of 21:36, 26 October 2006
The 'make alpha' makefile target in the kent source tree is used to build the CGI binaries and related data files into the /usr/local/apache/cgi-bin/ hierarchy.
After a new browser feature is developed the 'make alpha' is used to deliver this feature to the genome-test browser to allow QA and other users of genome-test to begin testing the new feature.
To use the 'make alpha' procedure, keep in mind the following:
- use a local filesystem to the development machine to save compile time
- use a completely clean checkout of the source tree to use only top-of-tree source
- email notify browser staff when install is done so everyone is aware that genome-test has changed
