Re: [jamboost] como-win32 toolset help needed

From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-05-26 09:58:13

[2003-05-26] Beman Dawes wrote:

>At 12:33 AM 5/26/2003, Rene Rivera wrote:
>
> >But if you need control on a per file basis then the naswer is 
>complicated,
> >because it's not really supported by BBv1. But a hack that will work is 
>to
> >declare a free-feature to specify files which should have warnings
> >disabled,
> >and check as each file is compiled to add, or not, the --a flag. And to
> >make
> >it easy for you.. attached is a patch to the current como-win32-tools.jam
> >which does that ;-) With it you can specify <no-warn>some_file.cpp in the
> >requirements section which will not get the --a flag.
>
>Yes, that's exactly what is needed!
>
>I made the change to como-win32-tools.jam in CVS. It didn't work for me, 
>however.
>
>Perhaps I didn't use <no-warn> correctly. See my Jamfile below. I also 
>tried prefixing the two .cpp filenames with "../src/", but that didn't work 
>either.
>
>Ideas?

Yes, since it's a hack, I didn't consider sources with paths in them :-) You
just need to remove the path part, in adition to the grist part, when
testing the files. So the current test:

if $(>:G=) in $(NO_WARN) { WARN on $(<) = "" ; }

Becomes:

if $(>:G=:D=) in $(NO_WARN) { WARN on $(<) = "" ; }

-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq