Mslice - Revision history

Dean Whittaker at 09:23, 5 September 2008

2008-09-05T09:23:22Z

Dean Whittaker at 10:49, 2 September 2008

2008-09-02T10:49:54Z

Dean Whittaker at 10:37, 2 September 2008

2008-09-02T10:37:58Z

Dean Whittaker at 13:46, 26 August 2008

2008-08-26T13:46:53Z

New page

Mslice uses some of the same functions as Libisis. These are all in a subdirectory called libisis_funcs. Mslice therefore contains copies of the functions so that it can be run without Libisis.

==Compiling Standalone Mslice==

← Older revision		Revision as of 09:23, 5 September 2008
Line 1:		Line 1:
−	~~Mslice is designed to be compiled into a standalone application. Therefore, some matlab functions etc. can not be used~~

−
−	~~== Dos and Don'ts ==~~
−
−	~~There are a few rules when altering code that ''''MUST'''' be obeyed, these are:~~
−
−	* NO feval or eval statements - these do not compile
−	* Use the command filesep to get the folder separator for the current platform instead of using '\'
−	* Do not use script mfiles
−	* Use text files for any optional settings etc. so that a user may change them once the suite has been compiled
−	* Always include the mcrinstaller with any distribution
−
−
−
−	~~== How To Compile for Windows==~~
−
−	~~===Mex Fortran Files===~~
−
−	~~The mex files should already exist, but if required the function mslice_mex exists. Run this script to produce mex files in the correct format for your version of Matlab.~~
−
−	~~===Compile Standalone Mslice===~~
−	* open matlab. Version 2006b or later is required to use the mslice compile script.
−	* Make sure that your '''startup.m''' file either contains conditional isdeployed statements (so that no code executes if isdeployed is true) OR all text is commented out. The presence of code in startup.m stops any compiled applications from working, but compiling will complete. NOTE however, that the paths still have to set up (i.e. startup.m must have run when you opened Matlab, but not be available at compile-time)
−	* Type >> mslice_compile_win32. This will then take up to 5 minutes to compile,
−	* Two files now exist in the mslice_standalone folder (newly created on the same level as the mslice_compile file). The zip file and the MCRinstaller.exe file. Distribute both to users, they must run the MCRinstaller.exe file once to setup matlab components on their computer.
−	* A further text file complete.txt is created, this file indicates that compilation is successfull and contains a date and time stamp of the last successful build. This is for reference only.
−
−
−	~~see [[File Locations]] for where to upload these for access from the wiki~~

@@ Line 16: / Line 16: @@
 == How To Compile for Windows==
 * open matlab. Version 2006b or later is required to use the mslice compile script.
 * Make sure that your '''startup.m''' file either contains conditional isdeployed statements (so that no code executes if isdeployed is true) OR all text is commented out. The presence of code in startup.m stops any compiled applications from working, but compiling will complete. NOTE however, that the paths still have to set up (i.e. startup.m must have run when you opened Matlab, but not be available at compile-time)
 * Type >> mslice_compile_win32. This will then take up to 5 minutes to compile,

← Older revision		Revision as of 10:37, 2 September 2008
Line 1:		Line 1:
−	Mslice ~~uses~~ some ~~of the same~~ functions ~~as Libisis~~. ~~These are all in a subdirectory called libisis_funcs. Mslice therefore contains copies of the functions so that it~~ can be ~~run without Libisis.~~	+	Mslice is designed to be compiled into a standalone application. Therefore, some matlab functions etc. can not be used


		+	== Dos and Don'ts ==

−	==~~Compiling Standalone Mslice~~==	+	There are a few rules when altering code that ''''MUST'''' be obeyed, these are:
		+
		+	* NO feval or eval statements - these do not compile
		+	* Use the command filesep to get the folder separator for the current platform instead of using '\'
		+	* Do not use script mfiles
		+	* Use text files for any optional settings etc. so that a user may change them once the suite has been compiled
		+	* Always include the mcrinstaller with any distribution
		+
		+
		+
		+	== How To Compile for Windows==
		+
		+
		+	* open matlab. Version 2006b or later is required to use the mslice compile script.
		+	* The '''First''' time you compile:
		+	* Make sure that your '''startup.m''' file either contains conditional isdeployed statements (so that no code executes if isdeployed is true) OR all text is commented out. The presence of code in startup.m stops any compiled applications from working, but compiling will complete. NOTE however, that the paths still have to set up (i.e. startup.m must have run when you opened Matlab, but not be available at compile-time)
		+	* Type >> mslice_compile_win32. This will then take up to 5 minutes to compile,
		+	* Two files now exist in the mslice_standalone folder (newly created on the same level as the mslice_compile file). The zip file and the MCRinstaller.exe file. Distribute both to users, they must run the MCRinstaller.exe file once to setup matlab components on their computer.
		+	* A further text file complete.txt is created, this file indicates that compilation is successfull and contains a date and time stamp of the last successful build. This is for reference only.
		+
		+
		+	see [[File Locations]] for where to upload these for access from the wiki