Version 1.0.2 beta 2

Highlights of v1.0.2 beta 2

• OSX dynamic libraries and plugins now default to using an install name of @rpath/[lib filename]. This requires an executable loading such files to define RPATHs - by default, a application built with Bam defines @executable_path/ as an initial RPATH. This restores previous behaviour, but this change allows applications to define additional RPATHs to just the application, rather than each dynamic library, to locate those dependencies.
• VisualStudio project files, project filter, and solution files are now only rewritten to disk if they don't exist, or differ from the existing file. For larger projects, this reduces the time in which the VisualStudio IDE becomes responsive after incremental changes to the build scripts, if the project is not unloaded first. Note that Xcode project generation does not support this feature yet.
• Multiple Xcode projects referencing the same source file now honour per-module compiler options of those files. (Not per configuration - Xcode does not support this.)
• Added an assembly level attribute, Bam.Core.PackageDirectoryRedirect, which redirects where the $(packagedir) macro refers to, so that source for a package can reside elsewhere. For example, if package build scripts and package source reside in different source control repositories, or don't support nested checkouts.
• Added Bam.Core.Module.ClosingPatch, which is similar to a private patch, but is guaranteed to be the last patch to be executed on a module. This allows logic to be applied once all settings on a module have been calculated.

All changes since v1.0.2b1

Known issues

Bug list