From: Klaus Nowikow (e8827661_at_[hidden])
Date: 2006-06-14 08:59:30
Ilya Sokolov wrote:
> Klaus Nowikow wrote:
>> I created a little tool file for running xpidl (the interface
>> generator from the mozilla project) following
>> http://boost.org/boost-build2/doc/html/bbv2/extender.html :
>> import type ;
>> type.register XPIDL : idl ;
>> import generators ;
>> generators.register-standard xpidl.xpidl : XPIDL : H ;
>> actions xpidl
>> xpidl -m header -Ic:/cygwin/opt/mingw/idl -w $(>)
>> and tried to test it with this jamfile:
>> lib vtk-wrapper
>> : vtkIVisualizationFrame.idl plugin.cpp
>> : <link>shared ;
>> where plugin.cpp contains only
>> '#include "vtkIVisualizationFrame.h"'. Running
hm. But I have only one main target (a lib). The cited page says
By default, Boost.Build handles such dependencies within one main
target. For example, assume that main target "app" has two sources,
"app.cpp" and "parser.y". The latter source is converted into "parser.c"
and "parser.h". Then, if "app.cpp" includes "parser.h", Boost.Build will
detect this dependency. Moreover, since "parser.h" will be generated
into a build directory, the path to that directory will automatically
added to include path.
That is 'exe app : app.cpp parser.y ;'.
From parser.y the tool creates parser.h and then app is built using
app.cpp and parser.h.
Doesn't this mean that my jamfile should work? The only difference I can
see is that I only create a *.h file from *.idl instead of a *.h and a
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk