Re: Adding a new compiler and linker for use with BJAM.

From: Peter Foley (pjfoley_at_[hidden])
Date: 2005-07-02 01:04:46

Hi Volodya,

Thanks for the reply earlier. I have not been idle and have been working my
way through this.

I have been reading through the online doc's and reading through a number of
the other jam files in the v2\tools directory (mainly the msvc one).

I have attached what I have done so far.

As you advised I have managed to get it such that I can do the linker stage.
Ie I first manually compile the WIX files and then use bjam to link the
object files together. (note I have used "-out test", to hard code the
files name. Is there a better way to do this?).

What process would I need to go through to do the compiler stage. I could
be really dense but I have not found anything in the online doc's to suggest
the way forward.

Also where in the doc's would I learn about how bjam does its pattern
matching?

Thanks,

Peter.

> Message: 3 
> Date: Mon, 27 Jun 2005 11:29:37 +0400
> From: Vladimir Prus <ghost_at_[hidden]>
> Subject: Re: Adding a new compiler and linker for use with BJAM.
> 
> Hi Peter,
> 
> > Since it is starting to include a number of wxs files 
> (think CPP files) I
> > decided to look into writing a jamfile to contain the 
> various build rules
> > to generate the MSI file. Also as the standard build 
> system of choice for
> > boost it would hopefully allow other interested parties to 
> look at and
> > extend/contribute to the installer.
> >
> > I have read through the online "Boost Build System V2" 
> documentation and
> > the closest thing I can find to adding new file extensions 
> is "Chapter 22.
> > Extender Manual". Is this the right part of the manual to look at?
> 
> Exactly.
> 
> > The main tools that would be used are:
> >
> > * Candle.exe - Which is the compiler for WIX. It takes 
> .wxs files and
> > compiles them into .wixobj.
> > * Light.exe - Which is the linker for WIX. It takes 
> all the .wixobj
> > files and links them into an MSI file.
> >
> >
> > To give you an example of how these tools are used check 
> out these blog
> > links: 
> http://blogs.msdn.com/robmen/archive/2004/04/05/107709.aspx (example
> > using 1 wxs file) and
> > http://blogs.msdn.com/robmen/archive/2004/05/11/129613.aspx 
> (example using
> > 2 wxs files).
> >
> > Is it a trivial process to introduce the ability to support 
> WIX within
> > BJAM?
> 
> I believe so. You can start with "wxsobj" to MSI 
> transformation. Just follow 
> the instructions at 
> http://boost.org/boost-build2/doc/html/bbv2/extender.html#bbv2
.extender.intro
> Alternatively, you can take a look at example/customization project, 
> specifically the "verbatim.jam" file, and adjust it to your needs.
> 
> The only difference from the docs is replacing 
> 
> generators.register-standard
> 
> with
> 
> generators.register-composing 
> 
> for the wxsobj -> MSI transformation, so that Boost.Build 
> links all wxsobj 
> files together, and does not process them individually.
> 
> - Volodya
> 
> 
> -- 
> Vladimir Prus
> http://vladimir_prus.blogspot.com
> Boost.Build V2: http://boost.org/boost-build2
> 
> 
> ______________________________________________________________
 ------=_NextPart_000_0000_01C57F1F.C48213E0 Content-Type: application/octet-stream;
name="wix.jam"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="wix.jam"

[Attachment content not displayed.] ------=_NextPart_000_0000_01C57F1F.C48213E0--