otp.git/lib/reltool/test/reltool_server_SUITE_data/Makefile.src, branch OTP-17.2 Mirror of Erlang/OTP repository. [reltool] Add option {excl_lib,otp_root} 2012-08-20T13:56:06+00:00 Siri Hansen siri@erlang.org 2012-08-17T13:38:35+00:00 ee8e60f1c160e576a040a92d28f3a3eed1cb572a With this option reltool will create a target structure with only the applications found in specified 'lib_dirs' (on system level) or 'lib_dir' (on app level). Erts will not be included, and no applications found under $OTP_ROOT/lib. 
With this option reltool will create a target structure with only the
applications found in specified 'lib_dirs' (on system level) or
'lib_dir' (on app level). Erts will not be included, and no
applications found under $OTP_ROOT/lib.
[reltool] Add configuration parameter lib_dir on application level 2012-03-22T07:46:30+00:00 Siri Hansen siri@erlang.org 2012-03-21T18:35:17+00:00 602d96340b97315c156b597a5ccbfcc135a9a682 As a way of specifying one specific version of an application, the following configuration parameter is added on application level: {lib_dir,Dir}, Dir = string() This can be useful if the parent directory of the application directory is not suitable to use as a lib dir on system level. 
As a way of specifying one specific version of an application, the
following configuration parameter is added on application level:

{lib_dir,Dir}, Dir = string()

This can be useful if the parent directory of the application
directory is not suitable to use as a lib dir on system level.
[reltool] Add test cases for handling of escripts 2012-03-19T08:48:53+00:00 Siri Hansen siri@erlang.org 2012-02-13T15:57:51+00:00 e3bb31270b1cc43a72a2c3942f496e5c8f93155b OTP-9794 OTP-9968 The following test cases are added: * create_standalone_beam * create_standalone_app * create_multiple_standalone * load_config_escript_path * load_config_same_escript_source * load_config_same_escript_beam * load_config_add_escript Most of them are temporarily skipped since they re-produce known problems that will be corrected in a later commit. 
OTP-9794
OTP-9968

The following test cases are added:
* create_standalone_beam
* create_standalone_app
* create_multiple_standalone
* load_config_escript_path
* load_config_same_escript_source
* load_config_same_escript_beam
* load_config_add_escript

Most of them are temporarily skipped since they re-produce known
problems that will be corrected in a later commit.
[reltool] Add test of dependencies derived through calls to external apps 2012-03-19T08:48:53+00:00 Siri Hansen siri@erlang.org 2012-01-09T14:42:29+00:00 e610c1e38219b7038f2e42b233ef226508535a90 OTP-9794 This is a test of the mechanism with which reltool_server decides which applications to include and not, based on function calls between applications. This is also the mechanism which forms the base for the application- and module dependency graphs. 
OTP-9794

This is a test of the mechanism with which reltool_server decides
which applications to include and not, based on function calls between
applications. This is also the mechanism which forms the base for the
application- and module dependency graphs.
Allow same module name in multiple applications if explicitely excluded 2011-05-17T09:04:38+00:00 Siri Hansen siri@erlang.org 2011-05-11T13:57:51+00:00 06f99b287fbb79e89831bedf1b2e64e7185f66c8 Earlier, reltool expected all module names detected under the lib directories to have unique names. If this was not the case, the result was undefined - i.e. the beam file of the duplicated module might be included in multiple applications in the target area, or it might even be excluded from all applications. This commit adds awareness in reltool that a module might occur in multiple applications, and it is allowed as long as the module or it's application is explicitely excluded in all but one of the containing applications. 
Earlier, reltool expected all module names detected under the lib
directories to have unique names. If this was not the case, the result
was undefined - i.e. the beam file of the duplicated module might be
included in multiple applications in the target area, or it might even
be excluded from all applications.

This commit adds awareness in reltool that a module might occur in
multiple applications, and it is allowed as long as the module or it's
application is explicitely excluded in all but one of the containing
applications.