MCR libraries - Revision history

Daniel Castaño at 09:33, 4 October 2016

2016-10-04T09:33:33Z

Daniel Castaño at 16:37, 1 June 2016

2016-06-01T16:37:10Z

Daniel Castaño at 09:22, 2 May 2016

2016-05-02T09:22:22Z

Daniel Castaño: /* General use of the MCR */

2016-05-02T09:20:41Z

General use of the MCR

Daniel Castaño: /* General use of the MCR */

2016-05-02T09:20:02Z

General use of the MCR

Daniel Castaño: /* In Dynamo */

2016-05-02T09:18:12Z

In Dynamo

Daniel Castaño: /* In Dynamo */

2016-05-02T09:17:54Z

In Dynamo

Daniel Castaño: Created page with "The MCR (''Matlab Compiled Runtime'') libraries are a set libraries freely distributed by Mathworks. They allow running code written in Matlab without having a Matlab licens..."

2016-05-02T09:14:10Z

Created page with "The MCR (''Matlab Compiled Runtime'') libraries are a set libraries freely distributed by Mathworks. They allow running code written in Matlab without having a Matlab licens..."

New page

The MCR (''Matlab Compiled Runtime'') libraries are a set libraries freely distributed by Mathworks.

They allow running code written in Matlab without having a Matlab license in your system.

== In Dynamo ==
The MCR libraries are used when running the [[standalone]] version, both for running projects or for the interactive [[Dynamo console|console]. The libraries are already included in the version available for [[download]] and in general you shouldn't need to reinstall them.

==General use of the MCR==
The code needs to have been ''compiled'' by the authors, who should have delivered a ''precompiled executable''to the end users. End users need to have a version of the MCR libraries that matches the version used by the author to compile the original Matlab code.

← Older revision		Revision as of 09:33, 4 October 2016
Line 14:		Line 14:

	Do not mix this environment variable with [[MCR_CACHE_ROOT\|<tt>MCR_CACHE_ROOT</tt>]], which is used to select a location on the filesystem where the MCR libraries will store temporary information.		Do not mix this environment variable with [[MCR_CACHE_ROOT\|<tt>MCR_CACHE_ROOT</tt>]], which is used to select a location on the filesystem where the MCR libraries will store temporary information.
		+
		+	== MCR versions ==
		+
		+	The version of the MCR library reflects the strengths and flaws of the Matlab version. Thus, if a ''Dynamo'' [[standalone]] has been compiled against, say, Matlab release R2015a, the performance of the resulting distributed ''Dynamo''package (for instance, in graphics rendering) will correspond to the performance of that Matlab version.
		+
		+	In principle, we would like to distribute ''Dynamo'' packages that are compiled against the highest available version of Matlab, to ensure that users of the ''Dynamo'' standalone have access to the best performing version of software.
		+
		+	However, Mathworks has recently introduced some changes in their MCR packaging system. For MCRs R2015b onwards, we have received user reports of ''Dynamo'' standalone versions not correctly linking with the MCR libraries distributed in the very same package. In those cases, the users have two options:
		+	* install manually the corresponding MCR version in their own system
		+	* use a ''Dynamo'' package compiled against R2015a.

@@ Line 4: / Line 4: @@
 == In Dynamo ==
-The MCR libraries are used when running the [[standalone]] version, both for running projects or for the interactive [[Dynamo console|console]. The libraries are already included in the version available  for [[Download Dynamo|download]] and in general you shouldn't need to reinstall them.
+The MCR libraries are used when running the [[standalone]] version, both for running projects or for the interactive [[Dynamo console|console]]. The libraries are already included in the version available  for [[Download Dynamo|download]] and in general you shouldn't need to reinstall them.
 Also, when you  [[Installation#Activating ''Dynamo'' as standalone program|''activate'']] ''Dynamo'' on a linux shell, the library paths will be set to point to the MCR libraries shipped within your ''Dynamo'' installation.

← Older revision		Revision as of 09:22, 2 May 2016
Line 12:		Line 12:

	In runtime, the shell must be informed through <tt>LD_LIBRARY_PATH</tt> of the location of the libraries.		In runtime, the shell must be informed through <tt>LD_LIBRARY_PATH</tt> of the location of the libraries.
		+
		+	Do not mix this environment variable with [[MCR_CACHE_ROOT\|<tt>MCR_CACHE_ROOT</tt>]], which is used to select a location on the filesystem where the MCR libraries will store temporary information.

@@ Line 9: / Line 9: @@
 ==General use of the MCR==
-In general applications of the MCR libraries, the code needs to have been ''compiled'' by the authors, who should have delivered a ''precompiled executable''to the end users. End users need to have a version of the MCR libraries that matches the version used by the author to compile the original Matlab code.
+In general applications of the MCR libraries, the code needs to have been ''compiled'' by the authors, who should have delivered a ''precompiled executable'' to the end users. End users need to have a version of the MCR libraries that matches the version used by the author to compile the original Matlab code.
 In runtime, the shell must be informed through <tt>LD_LIBRARY_PATH</tt> of the location of the libraries.

← Older revision		Revision as of 09:20, 2 May 2016
Line 9:		Line 9:

	==General use of the MCR==		==General use of the MCR==
−	~~The~~ code needs to have been ''compiled'' by the authors, who should have delivered a ''precompiled executable''to the end users. End users need to have a version of the MCR libraries that matches the version used by the author to compile the original Matlab code.	+	In general applications of the MCR libraries, the code needs to have been ''compiled'' by the authors, who should have delivered a ''precompiled executable''to the end users. End users need to have a version of the MCR libraries that matches the version used by the author to compile the original Matlab code.
		+
		+	In runtime, the shell must be informed through <tt>LD_LIBRARY_PATH</tt> of the location of the libraries.