Version 1.0.3

The changes included in this stable release are aimed at improving feedback to the user during bam builds, and consistent support for module versioning across platforms.

Highlights of v1.0.3

• Cyclic dependencies between modules are now reported as errors.
• Bam command line tool displays progress updates during dependency graph construction.
• As of Mono 4.4, Bam on OSX now uses 64-bit Mono, on supporting hardware.
• C application modules can now define a working directory to use in VisualStudio and Xcode project debugging.
• All types of C binaries (applications, DLLs, plugins) now generate a resource file on Windows, containing versioning information from the module (using the same information as for dylibs and shared object symlinks; major, minor and patch versions). Exceptions are those marked with the C.Prebuilt or C.Thirdparty attributes. An optional path to an existing resource file can be passed to C.Thirdparty, for those modules representing external software that already has versioning resource files.
• Added Bam.Core.IProductDefinition, which can be implemented in a package build, providing a way of specifying additional product-wide data, such as a product version, company name, copyright etc. This information is currently only used to generate the Windows version resource files.
• And many more changes and fixes.

Full changes since v1.0.2

Known issues

Bug list