Downloads

Download either a release appropriate for your platform or check out the bleeding edge CVS repository. Note that the CVS repository tends to be broken (i.e. not to compile).

All releases contain an example configuration file and the video.x driver from MOL.

What to download

If you have no idea what to download you almost certainly want the win32-jitc release.

Releases

These are links to the sourceforge mirror system. Don't "save link target as.." since that will only give you an HTML file.

release data	version	what	where
20.12.2005	0.4.0	sources-bzip2 sources-gzip win32	pearpc-0.4.tar.bz2 pearpc-0.4.tar.gz pearpc-0.4-win32-jitc.zip
5.9.2004	0.3.1	sources-bzip2 sources-gzip win32 sdl win32 generic	pearpc-0.3.1.tar.bz2 pearpc-0.3.1.tar.gz pearpc-0.3.1-win32-sdl-jitc.zip pearpc-0.3.1-win32-jitc.zip
13.8.2004	0.3.0	sources-bzip2 sources-gzip win32 jitc win32 generic	pearpc-0.3.0.tar.bz2 pearpc-0.3.0.tar.gz pearpc-0.3.0-win32-sdl-jitc.zip pearpc-0.3.0-win32-jitc.zip
15.6.2004	0.2.0	sources-bzip2 sources-gzip win32 jitc win32 generic	pearpc-0.2.0.tar.bz2 pearpc-0.2.0.tar.gz pearpc-0.2.0-win32-jitc.zip pearpc-0.2.0-win32.zip
20.5.2004	0.1.2	sources-bzip2 sources-gzip win32 jitc win32 generic	pearpc-0.1.2.tar.bz2 pearpc-0.1.2.tar.gz pearpc-0.1.2-win32-jitc.zip pearpc-0.1.2-win32.zip
14.5.2004	0.1.1	sources-bzip2 sources-gzip win32 jitc win32 generic	pearpc-0.1.1.tar.bz2 pearpc-0.1.1.tar.gz pearpc-0.1.1-win32-jitc.zip pearpc-0.1.1-win32.zip
10.5.2004	0.1	sources-bzip2 sources-gzip win32 jitc win32 generic	pearpc-0.1.tar.bz2 pearpc-0.1.tar.gz pearpc-0.1-win32-jitc.zip pearpc-0.1-win32.zip

Extras

For those who have no idea how to create a big file, here's a bzip2 compressed 3 GiB and 6 GiB file filled with zeros. The compressed files are < 5 KiB in size.

3 GiB disk image
6 GiB disk image
createdisk.py a Python script to efficiently create empty disk images

3c90x (network card) driver for Darwin PPC/Mac OS X

CVS access

You can browse our CVS repository online: View CVS online.

You can also fetch a copy of our CVS repository to your machine with these commands:

	
	$ cvs -z 4 -d:pserver:anonymous@pearpc.cvs.sf.net:/cvsroot/pearpc login
	

When asked for a password, hit Enter.

• Checking out "the trunk":

  
  	$ cvs -z 4 -d:pserver:anonymous@pearpc.cvs.sf.net:/cvsroot/pearpc co pearpc
  	

  This will create your repository in directory pearpc.

• Checking out a "branch":

  
  	$ cvs -z 4 -d:pserver:anonymous@pearpc.cvs.sf.net:/cvsroot/pearpc \
  	co -r $BRANCHNAME -d $BRANCHNAME pearpc
  	

  Replace $BRANCHNAME with the branch you want to checkout. This will create your repository in directory $BRANCHNAME. The current branch is: ppc_0_4_branch

To build from CVS, issue in the repository (cd there before)

	$ ./autogen.sh
	

Then use configure and make as usual.

To get the latest changes, do:

	$ cvs update -dP
	

Currently only a few people have write-access to CVS. If you want your changes to be applied, send us a patch.

In order to create patches, check out CVS, duplicate the directory, change only one of the copies, then do:

	
	$ diff -urN old-dir new-dir > my.patch
	

to obtain a patch. Alternatively (and untested), check out CVS, modify the checked-out files (you may also add files), then do:

	$ cvs diff -uN > my.patch
	

Note that in the first example you use "diff", in the second you use "cvs"