Version 1.0.1 beta 4

Highlights of v1.0.1 beta 4

• Added VisualC 2012 and 2010 support, including project generation. The latter has only been tested using the Express edition, which is has limited functionality compared to the Professional edition. Specify --VisualC.version=11.0 or 10.0, respectively on the command line (assuming the relevant packages are in your definition file).
• Headers exposed in C.Prebuilt modules (e.g. Qt modules) now appear in generated projects.
• Source files that are #included into others can now be explicitly marked as don't compile (see the PerformCompilation property on C.ObjectFile), and will appear as excluded in project files.
• Windows dynamic links can now specify an existing .def file for export definitions. See the C.ICommonLinkerSettingsWin.ExportDefinitionFile property.
• If a module is a child of a collection, it now has access to string macros referring to its parent. Useful to generate unique paths. See parentmodulename and encapsulatedparentmodulename macros.
• Scanning for #include statements in source files is more flexible on use of whitespace, and searching in the same directory as the source file (since the header search path does not need to be explicitly set on the compiler).
• Shell scripts in Xcode projects will now fail the build if any command within it fails.
• Fixed circular reference issue with symbolic links created by the Publisher package on a non-clean build.
• Procedurally generated files can now be checked for updates before writing them in non-clean project generation builds. For example, modules derived from C.ProceduralHeaderFile only write to disk when their content has changed now. See Bam.Core.EvaluationRequiredAttribute. This reduces redundant compilation steps when the IDE build step is next made.
• Many bug fixes to improve experience.

Full changes since v1.0.1 beta 3

Known issues

Bug list