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

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2005-10-14 13:36:12

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