[Boost-build] Passing link-flags to boost-build

Subject: [Boost-build] Passing link-flags to boost-build
From: Ts, Raghu (raghu.ts_at_[hidden])
Date: 2017-03-30 18:19:11

Hello,

I'm new to the Boost-world and have been entrusted with a task to build these libraries for UWP-Apps. I'm particularly interested in following libraries - 'filesystem', 'log', 'thread'. I tried building the entire gamut of libraries in Store-mode, but encountered many failures, including these libraries of interest.

Alternatively, I set out to build the Boost-libraries in Desktop-mode, but linking only against 'OneCoreUap.lib', instead of the plethora of libraries such as 'kernel32.lib', 'advapi32.lib', 'user32.lib', etc. However, I'm not able to pass on the link-flags to build-tool.

I'm using the following JAM-declaration:
using msvc : 14.0 : :
<linkflags>"\"C:/WDK/Lib/winv10.0/um/x64/OneCoreUAP.Lib"\"
<linkflags>/NODEFAULTLIB:"kernel32.lib"
<linkflags>/NODEFAULTLIB:"advapi32.lib"
;

Whether I use the command-line option or via JAM-file declaration, the link-options don't get passed on to the build-tool. If I modify the <linkflags> to <compileflags>, all the options get propagated properly; of course, it'll lead to errors as these are not compile-time flags.

Could someone please help me with what am I missing?

Thanks,
Raghu