top bar

Difference between revisions of "Micro-Manager Source Code"

(Current release available through our subversion repository: Note about svn 1.8.0)
(Current release available through our subversion repository: How to check out, so we don't have to have duplicate instructions elsewhere)
Line 10: Line 10:
  
 
To access the subversion repository you will need a [http://subversion.tigris.org/ subversion client].
 
To access the subversion repository you will need a [http://subversion.tigris.org/ subversion client].
 
Note: There is currently an issue that prevents the Subversion 1.8.0 client from checking out our public repositories (unless you have a username). Until this is fixed, please use Subversion 1.7.x.
 
  
 
https://valelab.ucsf.edu/svn/micromanager2/trunk - Release 1.4<br />
 
https://valelab.ucsf.edu/svn/micromanager2/trunk - Release 1.4<br />
Line 18: Line 16:
 
https://valelab.ucsf.edu/svn/micromanager2/branches/micromanager1.3 - Release 1.3<br />
 
https://valelab.ucsf.edu/svn/micromanager2/branches/micromanager1.3 - Release 1.3<br />
 
https://valelab.ucsf.edu/svn/micromanager2/branches/micromanager1.2 - Release 1.2<br />
 
https://valelab.ucsf.edu/svn/micromanager2/branches/micromanager1.2 - Release 1.2<br />
 +
 +
{{MessageBox|Note|There is currently an issue that prevents the Subversion 1.8.0 client from checking out our public repositories (unless you have a username). Until this is fixed, please use Subversion 1.7.x.|color=#1C879D}}
 +
 +
To build Micro-Manager 1.4, you should place the micromanager2 (trunk) and 3rdpartypublic repositories in the same directory. For example, run the following from your projects directory:
 +
 +
<code><pre>svn checkout https://valelab.ucsf.edu/svn/micromanager2/trunk micromanager
 +
svn checkout https://valelab.ucsf.edu/svn/3rdpartypublic</pre></code>
 +
 +
More information on how to build Micro-Manager can be found here:
 +
* [[Building Micro-Manager Device Adapters]]
 +
* [[Building and debugging Micro-Manager source code]]
  
 
== Previous source code releases ==
 
== Previous source code releases ==
  
 
[http://valelab.ucsf.edu/%7Enenad/micro-manager/distribution/micro-manager-1.1.47.tar.gz <span>'''Micro-Manager source code 1.1.47, (January 28, 2008) tar.gz package, 1.4 MB'''</span>]<br />[http://valelab.ucsf.edu/%7Enenad/micro-manager/distribution/micro-manager-1.0.69.tar.gz <span>'''Micro-Manager source code 1.0.69, (May 1, 2007) tar.gz package, 1.2 MB '''</span>]<br />
 
[http://valelab.ucsf.edu/%7Enenad/micro-manager/distribution/micro-manager-1.1.47.tar.gz <span>'''Micro-Manager source code 1.1.47, (January 28, 2008) tar.gz package, 1.4 MB'''</span>]<br />[http://valelab.ucsf.edu/%7Enenad/micro-manager/distribution/micro-manager-1.0.69.tar.gz <span>'''Micro-Manager source code 1.0.69, (May 1, 2007) tar.gz package, 1.2 MB '''</span>]<br />

Revision as of 17:36, 20 June 2013

Updated on June 14, 2011

The source code includes all Micro-Manager files (Java and C++) and all supporting files (project files, build scripts, etc.). However, to build the entire project a number of Open Source libraries and device SDKs must be installed. Instructions for building Micro-Manager are available for Mac, Windows, and Linux.

Note about the source code licensing terms

Micro-Manager is structured in three distinct layers: Graphical User Interface (GUI), Device Adapters and MMCore. All source files, except ones carrying a different license notice in the header, are copyright of University of California. GUI and Device adapters are distributed under the "BSD" license, while MMCore is distributed under "Lesser GPL" license. License text files are included in the source package, and each file should have a header stating the exact type of license. A good starting point to learn more about the Open Source Code licensing is http://www.opensource.org/. If you have any questions or need some clarification regarding our licensing terms please let us know: info@micro-manager.org

Current release available through our subversion repository

To access the subversion repository you will need a subversion client.

https://valelab.ucsf.edu/svn/micromanager2/trunk - Release 1.4
https://valelab.ucsf.edu/svn/3rdpartypublic - 3rd party files needed for Release 1.4

https://valelab.ucsf.edu/svn/micromanager2/branches/micromanager1.3 - Release 1.3
https://valelab.ucsf.edu/svn/micromanager2/branches/micromanager1.2 - Release 1.2

Note
There is currently an issue that prevents the Subversion 1.8.0 client from checking out our public repositories (unless you have a username). Until this is fixed, please use Subversion 1.7.x.

To build Micro-Manager 1.4, you should place the micromanager2 (trunk) and 3rdpartypublic repositories in the same directory. For example, run the following from your projects directory:

svn checkout https://valelab.ucsf.edu/svn/micromanager2/trunk micromanager
svn checkout https://valelab.ucsf.edu/svn/3rdpartypublic

More information on how to build Micro-Manager can be found here:

Previous source code releases

Micro-Manager source code 1.1.47, (January 28, 2008) tar.gz package, 1.4 MB
Micro-Manager source code 1.0.69, (May 1, 2007) tar.gz package, 1.2 MB

© Micro-Manager : Vale Lab, UCSF 2006-2011 | All Rights Reserved | Contact