I want to be able to see what exactly jam is doing when it is compiling each file.  In other words, I want to see something along the lines of:
"g++ -Wno-deprecated -m32 -g -I../lib  -I../shared -DOS_IS_LINUX -c -o filename.o filename.cc."

Since I'm new to jam I want to make sure that my variables and flags are properly being processed. 

Thanks,

Chance Meek

Thanks, I found that out almost as soon as I posted this.  I kept trying the numbers, forgot there were letter options too.

Chance Meek
Software Engineer



-----Original Message-----
From: Jeremy Cowgar [mailto:jeremy <at> cowgar.com]
Sent: Wed 6/10/2009 1:46 PM
To: Meek, Chance
Cc: jamming <at> perforce.com
Subject: Re: [jamming] Question on jam output

Meek, Chance wrote:
>
> I want to be able to see what exactly jam is doing when it is
> compiling each file.  In other words, I want to see something along
> the lines of:
> "g++ -Wno-deprecated -m32 -g -I../lib  -I../shared -DOS_IS_LINUX -c -o
> filename.o filename.cc."
>
> Since I'm new to jam I want to make sure that my variables and flags
> are properly being processed.
>

Chance,

Take a peek at jam --help and look at the -d parameter. I believe what
you want is:

jam -dx

Jeremy

Question on jam output

I want to be able to see what exactly jam is doing when it is compiling each file.  In other words, I want to see something along the lines of:
"g++ -Wno-deprecated -m32 -g -I../lib  -I../shared -DOS_IS_LINUX -c -o filename.o filename.cc."

Since I'm new to jam I want to make sure that my variables and flags are properly being processed. 

Thanks,

Chance Meek

_______________________________________________ jamming mailing list - jamming <at> maillist.perforce.com http://maillist.perforce.com/mailman/listinfo/jamming

Is there a way to prevent jam from deleting object files when building a library?  I see on the Jambase Reference that "The intermediate objects  are deleted" when building a library.

Thanks,
Chance Meek
Software Engineer

It looks like if you set KEEPOBJS = true, intermediate objects may stick around. We always have NOARSCAN set to true, which also keeps object files around.