Changing Homer GUI Code - Revision history

Dean Whittaker at 13:14, 2 September 2008

2008-09-02T13:14:03Z

2008-09-01T12:45:53Z

2008-09-01T12:42:08Z

2008-09-01T12:39:45Z

2008-08-29T10:42:20Z

2008-08-26T15:52:59Z

2008-08-26T15:29:50Z

2008-08-26T13:53:57Z

2008-08-26T10:28:47Z

2008-08-26T10:27:38Z

@@ Line 24: / Line 24: @@
 ** Next, select the same compiler from the same group used to build libisis (usually C++ .NET 2003).
 ** Comfirm by pressing return
-* 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.
+* 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 >> homer_compile_win32. This will then take up to 5 minutes to compile,
 * Two files now exist in the standalone_homer folder (newly created on the same level and the homer_gui folder). 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.

@@ Line 25: / Line 25: @@
 ** Comfirm by pressing return
 * 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.
 * Type >> homer_compile_win32. This will then take up to 5 minutes to compile,
 * Two files now exist in the standalone_homer folder (newly created on the same level and the homer_gui folder). 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.

@@ Line 25: / Line 25: @@
 ** Comfirm by pressing return
 * 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.
-* Type >> Homer_compile. This will then take up to 5 minutes to compile,
+* Type >> homer_compile_win32. This will then take up to 5 minutes to compile,
 * Two files now exist in the standalone_homer folder (newly created on the same level and the homer_gui folder). 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.

@@ Line 18: / Line 18: @@
-* open matlab. Version 2006b or later is required to use the homer compile script. If NOT using 2007b, you may need to locate some Matlab .dll files within the matlab installation folders and replace those in the win32_distref folder (in the libisis root folder), particularly libmx.dll and libmex.dll. Use a dependency analysis on the .exe file that is compiled to discover which .dll files are no longer working.
+* open matlab. Version 2006b or later is required to use the homer compile script. If NOT using 2007b, you may need to locate some Matlab .dll files within the matlab installation folders and replace those in the win32_distref folder (in the libisis root folder), particularly libmx.dll and libmex.dll. Use a dependency analysis on the .exe file that is compiled to discover which .dll files are no longer working. (Dependency analysis: go to start menu -> run and type 'depends'. In the window that pops up, browse for your .exe and .dll dependency is displayed).
 * The '''First''' time you compile:
 ** type >> mbuild -setup

@@ Line 18: / Line 18: @@
-* open matlab. Version 2006b or later is required to use the homer compile script.
+* open matlab. Version 2006b or later is required to use the homer compile script. If NOT using 2007b, you may need to locate some Matlab .dll files within the matlab installation folders and replace those in the win32_distref folder (in the libisis root folder), particularly libmx.dll and libmex.dll. Use a dependency analysis on the .exe file that is compiled to discover which .dll files are no longer working.
 * The '''First''' time you compile:
 ** type >> mbuild -setup

← Older revision		Revision as of 13:53, 26 August 2008
Line 28:		Line 28:
	* Two files now exist in the standalone_homer folder (newly created on the same level and the homer_gui folder). 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.		* Two files now exist in the standalone_homer folder (newly created on the same level and the homer_gui folder). 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.		* 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

← Older revision		Revision as of 10:28, 26 August 2008
Line 2:		Line 2:


−	== ~~dos~~ and ~~don~~'ts ==	+	== Dos and Don'ts ==

	There are a few rules when altering code that ''''MUST'''' be obeyed, these are:		There are a few rules when altering code that ''''MUST'''' be obeyed, these are: