dynare/debian
sebastien 5e053d59f2 trunk: updated debian packaging
git-svn-id: https://www.dynare.org/svn/dynare/trunk@2334 ac1d8469-bf42-47a9-8791-bf33cf982152
2008-12-19 16:36:38 +00:00
..
README.Debian trunk: updated wiki URL in documentation 2008-10-20 16:31:20 +00:00
README.source v4: packaging updates 2008-07-11 14:57:54 +00:00
changelog trunk: merged r2221 from 4.0 branch (debian changelog entry for 4.0.2) 2008-10-28 14:12:14 +00:00
compat v4: merged Octave branch into trunk 2008-06-24 18:20:48 +00:00
control v4: packaging updates 2008-07-11 14:57:54 +00:00
copyright trunk: upgraded to GFDL 1.3 for all documentation 2008-12-18 13:39:46 +00:00
dynare-matlab7.4.install v4: merged Octave branch into trunk 2008-06-24 18:20:48 +00:00
dynare-matlab7.5.install v4: merged Octave branch into trunk 2008-06-24 18:20:48 +00:00
dynare.dirs v4: merged Octave branch into trunk 2008-06-24 18:20:48 +00:00
dynare.doc-base.manual v4: packaging updates 2008-07-11 14:57:54 +00:00
dynare.doc-base.userguide trunk: 2008-12-18 21:39:49 +00:00
dynare.docs trunk: 2008-12-18 21:39:49 +00:00
dynare.install trunk: updated debian packaging 2008-12-19 16:36:38 +00:00
dynare.lintian-overrides v4 packaging: 2008-07-09 17:20:45 +00:00
rules trunk: changes to MEX build system 2008-09-19 10:45:07 +00:00

README.source

The 'rules' file can build packages dynare-matlab7.4 and dynare-matlab7.5,
which contain DLLs for Matlab 7.4 and 7.5.

By default, the 'rules' file assumes that you have installed these Matlab (R)
versions in /usr/local/matlab74 and /usr/local/matlab75 respectively. If you
installed them somewhere else, please correct the environment variables at the
beginning of the 'rules' file.

Note that if any of these two directories doesn't exist, the corresponding
package will not be built.

Also note that the 'rules' file plays with Matlab (R) license manager,
launching it before building the MEX files, and killing it after. You must kill
any license manager before building the package, otherwise it fill fail. Also
note that if you have a single-user license, you must obviously build the
package with the user account which has the right to use the license.