Re: [Boost-build] 1.53.00 - masm ml options not honored??

Subject: Re: [Boost-build] 1.53.00 - masm ml options not honored??
From: Vladimir Prus (ghost_at_[hidden])
Date: 2013-10-03 02:37:15

On 02.10.2013 00:36, Jeff Flinn wrote:
> Any idea what could be the cause of the following issue:
>
>  > Ok I'm able to build my app linking with static context libs.
>  >
>  > I had to manually assemble the following into obj's by:
>  >
>  > ml /safeseh /c make_i386_ms_pe_masm.asm
>  > ml /safeseh /c jump_i386_ms_pe_masm.asm
>  >
>  > and then replace
>  >
>  > make_i386_ms_pe_masm.obj
>  > jump_i386_ms_pe_masm.obj
>  >
>  > in the boost build generated libs with the above.
>  >
>  > Any idea why modifying ...\boost_1_53_0\libs\context\**build\Jamfile.v2:
>  >
>  >
>  > actions masm
>  > {
>  >     ml /safeseh /c /Fo"$(<)" "$(>)"
>  > }
>  >
>  > is not being honored?
>  >
>
> I remember that boost.build has a bug which causes this behaviour - I don't
> know when it will be fixed (if ever) or we have to wait for cmake.

I am missing context here. If you have 'safeseh' in 'masm' action in context's Jamfile,
then that action will use safeseh option. There's nothing that will magically strip
'safeseh' from any command lines. So, could you check that:

- You are using Boost.Build you have modified (use --debug-configuration option)
- Build process actually invokes this action (i.e. it prints NNN.nasm as the action
being executed, where NNN includes context's Jamfile path.

HTH,
Volodya