Subversion Repositories DevTools

Last modification

• Rev 6133 2017-05-25 01:12:47
• Author: dpurdie

• Log message:

  ------------------------------------------------------------------------
  Version: 3.13.6000.cr Released: 04-May-17
  ------------------------------------------------------------------------
  
  Minor changes:
  * Makefile directive: PackageFiles
  Added option: --PreserveSymlinks.
  Used internally for preserving symlinks when building SDKs
  
  * Utility: jats_generate_deployable
  Ongoing improvements.
  
  Internal:
  Class: JatsCopy::CopyDir
  Added options
  NoRecurse
  NoSubDirList
  
  
  ------------------------------------------------------------------------
  Version: 3.13.5000.cr Released: 13-Apr-17
  ------------------------------------------------------------------------
  
  Minor changes:
  * Makefiles: Enhanced platform specifier
  Allows mixed use of included and excluded platform names.
  ie: Src ('DEVLINUX,!UBUNUT12', .... )
  
  * New Utilities: jats_generate_deployable, jats_generate_bom
  Experimental utilities for generation of BOMS
  
  ------------------------------------------------------------------------
  Version: 3.13.4000.cr Released: 31-Mar-17
  ------------------------------------------------------------------------
  
  Minor changes:
  * Build Files. BuildSrcArchive
  Exclude .svn sub directories.
  
  * Utility: jats_sandbox
  Improved behaviour of packages that do not build with the current
  build filters. They will be silently skipped and not create
  build errors.
  
  * Build Files - New alias : INSTRUMENT
  This is an alias for active instrumented build targets
  
  * Build Files - New directive : BuildAliasDef
  Shorthand for
  BuildAlias ('xxx,--Define', ... );
  This is the preferred method for defining aliases
  
  * Build Files - BuildAlias directive
  The build alias has been extended to support the use of a '!' operator
  This allows one, or more platforms to be removed from a definition.
  Examples:
  BuildAlias( 'A1,--Define', 'DEVLINUX,!ARM9TDMI');
  BuildAliasDef ('A1', 'DEVLINUX,!ARM9TDMI');
  All platforms covered by the DEVLINUX alias, except ARM9TDMI
  
  BuildAlias( 'A2,--Define', '!ARM9TDMI');
  BuildAliasDef( 'A2', '!ARM9TDMI');
  All active platforms, except the ARM9TDMI.
  
  * Platforms: GENERIC_XXX
  Improved operation of machType based generic platforms when used within the
  build system.
  
  Experimental:
  * Support for Red Hat Enterprise Linux 7
  Compiler is supported via the new platform RHEL7
  Jats support is provided via a machine type of linux_x64.
  This will change
  
  ------------------------------------------------------------------------
  Version: 3.13.3000.cr Released: 13-Mar-17
  ------------------------------------------------------------------------
  
  Minor changes:
  * Build Files. BuildSrcArchive
  Added a 'platform' argument. It is only used on build machines to
  prevent the archive being build on multiple machines.
  
  ------------------------------------------------------------------------
  Version: 3.13.1000.cr Released: 01-Mar-17
  ------------------------------------------------------------------------
  
  Minor changes:
  * Directive: MakePerlModule
  Fixed build issues associated with building Perl Modules under VS2012.
  Minor differences in the operation of nmake.
  
  * Build Files
  Handle build.pl files with out a BuildInterface directive
  Will force an interface directory called 'interface'
  
  Modified parsing of the BuildName to handle some instances of
  incorrect use of the '--RelaxedVersion' option.
  
  Note: This option is to be deprecated. Do not use it.
  Jats will handle '.cots' packages correctly by itself.
  
  * New Platforms: GENERIC_XXX
  A collection of platforms (Alias of GENERICS) that provide an architecture
  specific build target. The name of the target is created by joining the
  keyword GENERIC_ with the Jats Machine Type.
  ie: GENERIC_WIN32, GENERIC_LINUX_I386, GENERIC_LINUX_X64
  
  These targets cannot be mixed with non-generic targets (on the same machine), nor the GENERIC
  build target. It is possible to mix GENERIC_WIN32 with UBUNTU16 as they appear on
  different architectures.
  
  The targets function is in a similar manner to the GENERIC build target, but
  are directed to one or more machines.
  
  Intended uses:
  Windows: Creating installers.
  The NSIS builder does not require a compiler toolchain.
  
  All: Specialized packaging.
  
  * Makefiles
  New option in the platform specifier. --Alias=alias1[:alias2]*
  Allows the directive to be true if the current build has the specified alias.
  Eg:
  PackageFile ('--Alias=TOOLSET',DEVLINUX', ...)
  Will package the file(s) if the current build is for a platform that is
  a part of the TOOLSET alias AND is also member of the DEVLINUX alias.
  It could also have been written as:
  PackageFile ('--Alias=TOOLSET',--Alias=DEVLINUX', ...)
  but NOT as:
  PackageFile ('--Alias=TOOLSET:DEVLINUX', ...)
  PackageFile ('TOOLSET,DEVLINUX', ...)
  as these will be true if current platform is a TOOLSET or DEVLINUX
  
  * Utility: sandbox
  Subcommand info
  - Added option to test fingerprints
  - Display status in a column for easy reading
  
  ------------------------------------------------------------------------
  Version: 3.13.0000.cr Released: 20-Feb-17
  ------------------------------------------------------------------------
  
  Minor changes:
  * New build.pl directive BuilToolset.
  This directive will enable the generation of the TOOLSET alias.
  Provides a sanity test to ensure that tools can be built.
  Includes options to limit use to specific architectures
  
  * Support for building many of the platforms on a linux_x64 based machine
  Previously many of the compiler were limited to the Ubuntu12 machines.
  These can now be built on an Ubuntu16 based machine.
  
  * GenerateFiles directive
  Added --Var(Toolset) and --Var(Native).
  
  * Utility: sandbox
  Added a 'fingerprint' command to manipulate packages fingerprints.
  
  Sped up the location of build files. The results are cached and
  recalulated if the user adds or removes packages from the sandbox.
  
  Internal changes:
  * Centralizing build platform information.