|
|
(2 intermediate revisions by one other user not shown) |
Line 1: |
Line 1: |
− | == Binary Platfoms ==
| + | <big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [https://www.slicer.org/wiki/Slicer:SlicerBinaries here]</font></big> |
− | | |
− | Slicer3 binaries are currently being generated for the following platforms:
| |
− | | |
− | * linux-x86_64
| |
− | * linux-x86
| |
− | * win32
| |
− | * darwin-ppc
| |
− | * darwin-x86
| |
− | | |
− | == Nightly and Snapshot Builds ==
| |
− | | |
− | Builds for these platforms are auto-generated nightly from the Slicer3 svn trunk, and uploaded to the [http://www.na-mic.org/Slicer/Download/Nightly Nightly directory]. Builds older than seven days are deleted from the directory by a nightly cron job.
| |
− | | |
− | Around the first of the month, one binary for each platform is copied from the Nightly directory into the [http://www.na-mic.org/Slicer/Download/Snapshots Snapshots directory] to provide a historical archive of builds.
| |
− | | |
− | Builds in the Nightly and Snapshots directory are provided with no guarantee that they will run correctly, or run at all. If the Slicer3 trunk is compiling when the builds are made, the resulting binary will be uploaded. These builds are intended more for internal developer use and debugging, rather than end user use.
| |
− | | |
− | Our nightly builds are being generated on these machines with the following hardware and operating system configurations:
| |
− | | |
− | === linux-x86_64 ===
| |
− | slicerl.bwh.harvard.edu
| |
− | | |
− | Linux slicerl.bwh.harvard.edu 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:29:47 EST 2005 x86_64 x86_64 x86_64 GNU/Linux
| |
− | | |
− | Red Hat Enterprise Linux WS release 4 (Nahant)
| |
− | | |
− | === linux-x86 ===
| |
− | b2_d4_4.bwh.harvard.edu
| |
− | | |
− | Linux b2_d4_4.bwh.harvard.edu 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:30:39 EST 2005 i686 i686 i386 GNU/Linux
| |
− | | |
− | Red Hat Enterprise Linux WS release 4 (Nahant)
| |
− | | |
− | Dell Precision Workstation 470
| |
− | | |
− | === win32 ===
| |
− | lonely.bwh.harvard.edu
| |
− | | |
− | Microsoft Windows XP Professional - 32 bit
| |
− | | |
− | Version 5.1.2600 Service Pack 2 Build 2600
| |
− | | |
− | Dell Precision Workstation 470
| |
− | | |
− | === darwin-ppc ===
| |
− | slicerm.bwh.harvard.edu
| |
− | | |
− | OSX 10.4 (Tiger)
| |
− | | |
− | Darwin slicerm.local 8.7.0 Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC Power Macintosh powerpc
| |
− | | |
− | Mac Mini
| |
− | | |
− | Machine Model: PowerMac10,1
| |
− | | |
− | CPU Type: PowerPC G4 (1.2)
| |
− | | |
− | Number Of CPUs: 1
| |
− | | |
− | CPU Speed: 1.42 GHz
| |
− | | |
− | Memory: 1 GB
| |
− | | |
− | System Version: Mac OS X 10.4.7 (8J135)
| |
− | | |
− | Kernel Version: Darwin 8.7.0
| |
− |
| |
− | === darwin-x86 ===
| |
− | lefty.bwh.harvard.edu
| |
− | | |
− | OSX 10.4 (Tiger)
| |
− | | |
− | Darwin lefty.bwh.harvard.edu 8.10.1 Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386 i386 i386
| |
− | | |
− | Model Name: iMac
| |
− | | |
− | Model Identifier: iMac4,1
| |
− | | |
− | Processor Name: Intel Core Duo
| |
− | | |
− | Processor Speed: 1.83 GHz
| |
− | | |
− | Number Of Processors: 1
| |
− | | |
− | Total Number Of Cores: 2
| |
− | | |
− | Memory: 1 GB
| |
− | | |
− | System Version: Mac OS X 10.4.10 (8R2232)
| |
− | | |
− | Kernel Version: Darwin 8.10.1
| |
− | | |
− | == Release Builds ==
| |
− | | |
− | Release builds are located in the [http://www.na-mic.org/Slicer/Download/Release Release directory], and are intended for end users and tutorial participants. They have been tested, so they should work on the platform specified. If you encounter a bug in a release build, please go to our [http://www.na-mic.org/Bug Bug Tracker] and create an account. Once you create an account, you can view all of the known issues for that release. If the bug that you found is not in the bug tracker, please submit a new bug report with as much information as possible about how to recreate the problem.
| |