The .i suffix is now reserved for a preprocessor output file per this thread and Steve’s recent addition to support it:
http://thread.gmane.org/gmane.comp.lib.boost.build/23817/focus=23840
So it may be good for you to use some other extension.
Chris
From: boost-build-bounces@lists.boost.org [mailto:boost-build-bounces@lists.boost.org]
On Behalf Of Ling Li
Sent: Friday, January 20, 2012 2:32 PM
To: Boost.Build developer's and user's list
Subject: Re: [Boost-build] .i file suffix problem
I asked a similar question a while ago. Please see
http://boost.2283326.n4.nabble.com/Is-there-a-way-to-de-register-a-suffix-td3920186.html. There Vladimir suggested to 'cast' the types explicitly. I haven't got a chance to try that though. (I simply change the PREPROCESSED_C suffix from .i to .ii, as
a hack.)
On Tue, Jan 17, 2012 at 10:13 AM, lepere <renaud.lepere@alma.fr> wrote:
I'm using Swig and bbv2 and i use .i as suffix for swig input file. This was working well in the past but with latest bbv2 i got an error : preprocessed.jam already define this suffix.
type.register SWIG : i ;
generators.register-standard alma.swig : SWIG : CPP ;
feature.feature swig-options : : free ;
toolset.flags alma.swig OPTIONS <swig-options> ;
rule swig { }
actions swig {
swig $(OPTIONS) -o $(<) $(>)
}
C:/Renaud/alma/BuildTools/bbv2/build\type.jam:123: in register-suffixes from module type
error: Attempting to specify multiple types for suffix "i"
error: Old type PREPROCESSED_C, New type SWIG
C:/Renaud/alma/BuildTools/bbv2/build\type.jam:58: in type.register from module type
What should i do ?
- Change my swig suffix to something more explicit (.swig_i)
- or can i disable PREPROCESSED_C.
Thanks
Renaud
_______________________________________________
Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost-build