How to download files for seti@home
Ok, to make seti compile, you also need the BOINC client...odd isn't it?
So you will need a folder layout like this (folder names must be identical)
where /boinc contains all the boinc sources and /seti_boinc has...well you know.
The project files under /setiboinc/client/win_build.
The project file and makefile(s) refer to source files in ../../boinc/blah_blah_blah . This is why you need ./boinc also.
There are two paths for boinc and setiboinc in the development. There is the latest_public_release, and the work_in_progress paths.
The one you download from the tarballs is the work_in_progress. (unless you find the specific day of tarball that they used for public)
The other method for getting the source is CVS (Controlled Versioning System).
There are utilities for CVS for windows, 3 that I know of. WinCvs, TortoiseCVS, and cygwin. No I will not describe how to install them here, but short web search should find those docs.
Linux/Unix - Now you will need to prepare the makefiles
Boinc source includes files for the following programs:
For your use, you won't need these other parts, but they come anyway.
On linux/unix variants you will need to configure both projects to work with your compiler & system features.
A configure file is inlcuded for each. Go to setiboinc and run its configure commands.
For boinc project you need to check if you system has 'mysql' installed. Then use these commands
First get boinc to compile...try typing make (in boinc root of course). There may be errors depending on your compiler configuration or other situations. When in doubt, you can search for problems others have had with compiling. Problems Compiling Boinc
Second, try compiling setiboinc. Goto it's directory and make.
Windows CompilingThe windows client was compiled with Microsoft Visual C++ 7.0 (.Net works also). The solution file for loading with the IDE is:
Make sure you check which target you are compiling..."debug" or "release". Usually you will want "release".
Testing the executable
Once you are sucessfull at compiling/linking both, try running setiboinc client with the included work unit