Bronek Kozicki wrote:

I think that big part of failures in como toolset are due to --a (strict mode) option. This unfortunatelly prevents windows headers from being included. Or more precisely, the exact reasult of including windows headers with --a option on is that compiler chokes on __declspec, which is exactly what I see in results. I'd rather not update como toolset to remove this option, maybe someone more familiar with bjam will do this.

Is this specific files? I ask because there's already a facility in the como-win32 toolset for removing the --a option by specifying that certain files with <no-warn>file.cpp Or is this a global problem? As in the flag should be removed entirely. And here I ask because I though part of the idea of testing with como, once upon a time, was to have that strict mode testing. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

I think that big part of failures in como toolset are due to --a (strict mode) option. This unfortunatelly prevents windows headers from being included. Or more precisely, the exact reasult of including windows headers with --a option on is that compiler chokes on __declspec, which is exactly what I see in results. I'd rather not update como toolset to remove this option, maybe someone more familiar with bjam will do this.

I would prefer to see -a applied more or less uniformly, with whatever config changes we may need to make to disable Win32 support in that case. John.