Re: Adding a parameter for use in toolchain 'using' line
Steven Watanabe via Boost-build <[email protected]>
| Newsgroups | gmane.comp.lib.boost.build |
|---|---|
| Organization | Providere Consulting, Inc. |
| Message-ID | <[email protected]> |
AMDG On 08/21/2018 08:31 AM, Kuhl, Brian via Boost-build wrote: > <snip> > With something like this: > > using clang-vxworks : : $(cxx) : > <cflags>$(cflags) > <cxxflags>$(cxxflags) > <compileflags>$(compileflags) > <archiver>$(ar) > <linker>$(linker) > <library-path>$(library-path) > <libraries>$(libraries) > <crt0-obj>$(crt0-obj) > <linkflags>$(linkflags) > <linkflags-static>$(linkflags-static) > <linkflags-dynamic>$(linkflags-dynamic) > <linkflags-dll>$(linkflags-dll) ; > > But some options on the "using" line appear to be regular "features" and some don't appear to be defined anywhere as a formal feature? Where are these "special features" declared, and how is there behavior different from a regular "feature"? > They are *not* features. Even the ones that have the same names as features are not actually features. They are all processed by the init rule: - https://github.com/boostorg/build/blob/develop/src/tools/clang-vxworks.jam#L65 handles standard cflags, cxxflags, linkflags. - https://github.com/boostorg/build/blob/develop/src/tools/clang-vxworks.jam#L70 looks up the toolset specific option <archiver> In Christ, Steven Watanabe _______________________________________________ Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build