Obtaining and Compiling Source Code

Obtaining and Compiling Source Code

Participants

To ask questions, or to report bugs in the SETI application software, please go to the Help Desk Message board area.

Mailing lists

The follow mailing list is available. Click to subscribe or post to this list.

boinc_opt: This list is for people porting and optimizing BOINC applications, including SETI@Home.

Getting source code

You can get the Seti@home for BOINC source code in several ways:

Download a tarball or .zip file (generated nightly).
Browse the CVS repository via a web-based interface.

Access the CVS repository directly, e.g. with a command like

cvs -d :pserver:anonymous@alien.ssl.berkeley.edu:/home/cvs/cvsroot checkout seti_boinc

Join the Seti@home for BOINC SourceForge project.

Building the SETI Application

The top level directory of the build tree is seti_boinc. You will need to build the boinc library/api such that the seti_boinc build can find it. See seti_boinc/m4/sah_check_boinc.m4 for the complete list of possible locations. An easy way to arrange things is to put boinc and seti_boinc at the same level:

	my_build_dir/
		boinc/
		seti_boinc/

Once this is set up and you have built boinc, cd into seti_boinc and:

	./configure
	make

Testing Your Build

Copy your application executable into seti_boinc/client/test_workunits.
In that directory rename reference_work_unit.sah to work_unit.sah.

Run the seti app in standalone mode. For example:

        ./setiathome_4.02_sparc-sun-solaris2.7 -standalone

Compare your result with the reference result (reference_result_unit.sah).

©2024 University of California

SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.