diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2016-09-07 13:35:21 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2016-09-07 13:35:21 +0200 |
| commit | 0d3de45da7ae0a3a3ce33af274151e66e9ddf8a9 (patch) | |
| tree | c12cbd4e202557429dac1070cbaec18ca48ed02b | |
| parent | dc1ba69ecee15fb0cbcb7ebad39eb2d6abe76f06 (diff) | |
NEWS file correction0.4.0
| -rw-r--r-- | NEWS | 10 |
1 files changed, 5 insertions, 5 deletions
@@ -6,8 +6,8 @@ Version 0.4.0 MinGW GCC. With VC, the toolchain can be built with version 14 Update 2 or later and - used with any version from 13. /MD and, for C++, /EHsc are default but are - overridden if an explicit value is specified in the coptions variable. + used with any version from 7.1. /MD and, for C++, /EHsc are default but + are overridden if an explicit value is specified in the coptions variable. * Support for C compilation. @@ -43,9 +43,9 @@ Version 0.4.0 In build2 a library dependency on another library is either an "interface" or "implementation". If it is an interface, then everyone who links this - library should also link the interface dependency, explicitly. A good - example of an interface dependency is a library API that is called in an - inline function. + library should also be linking the interface dependency. A good example of + an interface dependency is a library API that is called in an inline + function. Interface dependencies of a library should be explicitly listed in the *.export.libs variable (where we can now list target names). The typical |