Re: Where in the boost.build code are the files actually compiled? (Newbie)

From: Tyson Marchuk (tmarchuk_at_[hidden])
Date: 2005-10-14 16:10:35

Nevermind. A bit of experimentation makes it look like % just
represents the source name so changing this to CPP(%.moc) seems to
adjust the output the way I want it.

Now if I can just figure out how to create the moc file without
compiling it as well then I'll be a happy camper. :)

Thanks for the help,
-Tyson Marchuk

--- In jamboost_at_[hidden], "Tyson Marchuk" <tmarchuk_at_c...> wrote:
>
> Ok I think I understand that now. Thanks.
> 
> So basically I have to change where this target's action is setup so
> that when it calls the 'moc' action in tools/qt.jam it passes the
> right name to the action. Any idea where I should look to find this?
> I'm guessing it's somewhere in the qt module definition where it says:
> 
> generators.register-standard qt.moc : H : CPP(moc_%) : <allow>qt ;
> 
> But I'm not really sure what teh 'CPP(moc_%)' syntax means.
> 
> Thanks again for your help,
> -Tyson Marchuk
> 
> 
> --- In jamboost_at_[hidden], Rene Rivera <grafik.list_at_r...> wrote:
> >
> > crimshadow wrote:
> > > Hi all,
> > > 
> > > Ok I've been trying to figure out where the actual compilation
> takes place
> > > in boost.build. If I put an ECHO statement in kernel/bootstrap.jam
> at the
> > > end of the file it prints this out and then it goes on to say
> things like:
> > > ...found 151 targets...
> > > ...updating 6 targets...
> > > gcc.compile.c++ ../main/build/linux/gcc/debug/main.o
> > > qt.moc ../main/build/linux/gcc/debug/moc_MainDlg.cpp
> > > gcc.compile.c++ ../main/build/linux/gcc/debug/moc_MainDlg.o
> > > gcc.compile.c++ ../main/build/linux/gcc/debug/MainDlg.o
> > > gcc.link ../main/build.linux/gcc/debug/main
> > > gcc.link ../main/obj/linux/main
> > > ...updated 6 targets...
> > > 
> > > So where is this being executed in the .jam files. Or is this done
> in the
> > > bjam executable itself?? I thought the build process started at
> > > bootstrap.jam which just includes kernel/bootstrap.jam so I'm
kind of
> > > confused as to what happens before this.
> > 
> > Depends on you definition of "build process". All the code from 
> > bootstrap.jam through when you see the found# message happens in the
> jam 
> > files. All that the code does up to that point is set up all the
> targets 
> > and actions for those targets. After that bjam takes over and starts 
> > header scanning, dependency analysis, target stability, and
eventually 
> > running of the needed actions.
> > 
> > 
> > 
> > -- 
> > -- 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
> >
>