Project.meta
Dependency canDriver # no config attribute
Command line
User@Host:~$ bake -m bla/myProj
Note
To show the possible configs of a project, use the –show_configs command line option.
Changed: more than one config of a project can be used in one build.
Example:
Dependency canDriver, config: C1 Dependency canDriver, config: C2To reference a config of the current project, omit the project name, e.g.:
Dependency config: C3To build a single project, you can still use -p command line argument:
User@Host:~$ bake Debug -p canDriverHowever, if canDriver has more than one config in the workspace, all configs will be built. To build only a single config, use a comma separator like this:
User@Host:~$ bake Debug -p canDriver,C1
| Old | New | |
|---|---|---|
| Main project | $(MainConfigName) | $(MainConfigName) |
| Sub Project | $(MainConfigName)_$(MainProjectName) | $(SubConfigName)_$(MainProjectName)_$(MainConfigName) |
Warning
Be careful if you have something like this in Project.meta:
ExternalLibrary "bspCoreZ6/$(MainConfigName)_$(MainProjectName)/src/coreZ6/startup/startupCode.o", search:false
This refers to the old output directory. Change it or if you want to support old and new bake versions, write a PreStep which copies the file from the new location to the old one.
Changed: with -f a pattern can be specified, not only a single file. All files matching this string will be compiled.
Changed: variables in Dependency definitions are not allowed anymore to avoid inconsistencies.
Changed: no error will be reported anymore if makefile has no clean target.
Changed: source files will now be compiled and archived ordered by the Files definition in Project.meta, not by a Eclipse-backward-compatibility-ordering.
Changed: reworked some error messages, more error annotations are shown in IDEs
Added: “–include_filter” and “–exclude_filter” also work for main step of CustomConfig
Added: possibility to add comments in roots.bake
Added: new variables CPPPath, CPath, ASMPath, ArchiverPath and LinkerPath. These variables can also be used in InternalDefines and InternalInclude files.
Added: lint is not restricted to GCC toolchain anymore.
Added: –docu option. Specify the docu command line in Docu tag of the (Default)Toolchain.
Removed: support for Ruby 1.8. Use Ruby 1.9 or higher.
Removed: dependencies to cxxproject and rake gems
Removed: “-j” as default flag when calling makefiles. This must be explicitly specified.
Removed: option to check for unnecessary includes
| Old | New | |
|---|---|---|
| Compiler command | $(ti_home)/ccsv5/tools/compiler/tms470/bin/cl470 | ti_cl |
| Compiler flags | -mv7A8 -g –include_path=”#{ti_home}/ccsv5/tools/compiler/tms470/include” –diag_warning=225 -me –abi=eabi –code_state=32 –preproc_with_compile | |
| Archiver command | $(ti_home)/ccsv5/tools/compiler/tms470/bin/ar470 | ti_ar |
| Linker command | $(ti_home)/ccsv5/tools/compiler/tms470/bin/cl470 | ti_cl |
| Linker flags | -mv7A8 -g –diag_warning=225 -me –abi=eabi –code_state=32 -z –warn_sections -i”$(ti_home)/ccsv5/tools/compiler/tms470/lib” -i”$(ti_home)/ccsv5/tools/compiler/tms470/include” | |
| Linker lib prefix flags | -lDebug/configPkg/linker.cmd |
Bugfix: variables in add and remove attributes of Flags now work as intended
Bugfix: output folder was not created if no sources are specified for LibraryConfig and ExecutableConfig.
Bugfix: “-p” was not forwarded in bakery.
Cosmetic: bakery now calls bake with relative pathnames, which results in nicer outputs.