> On Tue, May 31, 2011 at 5:02 AM, Chris Molozian <chris <at> cmoz.me> wrote:
>
> As suggested I've tried:
>
> MkDir build ;
> ALL_LOCATE_TARGET = build ;
>
> to relocate all build output to a dedicated build folder but it appears to do nothing. The object files are still built alongside source files and the libraries and executable build in the same directory as the Jamfile. I'm not sure what I'm doing wrong.

I forgot to mention: you can always set LOCATE on targets yourself, of course.
In fact, if you look in Jambase at how ALL_LOCATE_TARGET is used (it's
just 2 lines), it just sets the default LOCATE path.

LOCATE itself is a jam 'special' variable, which is used to bind a
target to a physical path on the file system.
c.f. http://public.perforce.com/public/jam/src/Jam.html#search

(apologies if you already knew this)

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

You shouldn't need to explicitly make the build directories, there.

We use ALL_LOCATE_TARGET and it works great for us. Just make sure you have it set up in your Jamrules, then at the top of each Jamfile ensure that you use SubDir. e.g. for a top level directory that has a src1 and src2 subdirectory, you should have this:

[top-level Jamfile]

SubDir TOP ;

# Stuff here

SubInclude $(TOP) src1 ;

SubInclude $(TOP) src2 ;

[src1 Jamfile]

SubDir TOP src1 ;

# stuff here

[src2 Jamfile]

SubDir TOP src2 ;

# stuff

In fact, we go a step further. Because we build for many different platforms, we actually want our build products to go into subdirectories, e.g. "temp/windows-debug" and "temp/macos-release", etc. So our Jamrules looks like this:

ALL_LOCATE_TARGET = temp ;

# Make LocateObjects be called at the end of the SubDir rule.

SUBDIRRULES += LocateObjects ;

rule LocateObjects

{

    # Build flavor is windows-debug, etc.

    LOCATE_TOKENS = $(ALL_LOCATE_TARGET) $(BUILD_FLAVOR) $(SUBDIR_TOKENS) ;

    # See the setup of these in Jambase's SubDir rule for reference.

    LOCATE_TARGET = [ FSubDirPath TOP $(LOCATE_TOKENS) ] ;

    LOCATE_SOURCE = [ FSubDirPath TOP $(LOCATE_TOKENS) ] ;

}

Note that this assumes a TOP, but that's fine for us.

Cheers,

--matt

On Fri, Jun 3, 2011 at 2:03 PM, John Waugh <john.waugh <at> gmail.com> wrote:

On Fri, Jun 3, 2011 at 9:57 AM, Chris Molozian <chris <at> cmoz.me> wrote:
>
> The only remaining addition I'd like to make is to force all build output to
> a dedicated build folder as you've been helping me with. I don't understand
> where to apply the SubDir rule and the ALL_LOCATE_TARGET variable. My
> project directory structure is as follows:
>    code/
>       |-- src/
>       |-- imports/
>       |-- build/        <-- folder for all build output
>       |-- Jamfile
>

Here's a Jamfile I created as a demo - the source files referenced are
just for a 'hello world' program.

# --- BEGIN Jamfile ---
ALL_LOCATE_TARGET = build ;
SubDir TOP ;

# Compile will fail if the destionations for ALL_LOCATE_TARGET
# don't exist, so be sure to create them
MkDir build/src ;
Depends proggie : build/src ;

Main myprogram : src/main.c src/foo.c ;
# --- END Jamfile ---


As I mentioned, I haven't used ALL_LOCATE_TARGET much myself, so
perhaps the MkDir/Depends stuff could be handled more automatically,
but that worked for me.

Does it make sense?

-John

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

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

On Fri, Jun 3, 2011 at 3:21 PM, matthew conte <matt <at> baisoku.org> wrote:

> You shouldn't need to explicitly make the build directories, there.

I found that I had to create the destination directory at least once.
Creating the dirs manually upfront works - any subsequent 'jam clean'
will only kill the files and not the dirs.
But if you ever removed the 'build' directory, AFAIK you'd get errors
the next time you built.

At least that's how it's playing out in my test case I'm toying with -
see below for output from a terminal session.

> We use ALL_LOCATE_TARGET and it works great for us. Just make sure you have

> it set up in your Jamrules...

Good point about putting it in Jamrules, rather than at the top of the
Jamfile. Putting it ahead of SubDir in Jamfile *seemed* unnecessarily
ugly.

Here's the output of a session where I don't have 'build/src' created
beforehand:

$ ls -R
Jamfile  Jamrules build    src

./build:

./src:
foo.c  foo.h  main.c

$ cat Jamrules
# --- BEGIN Jamrules ---
ALL_LOCATE_TARGET = build ;
# --- END Jamrules ---

$ cat Jamfile
# --- BEGIN Jamfile ---
SubDir TOP ;

Main myprog : src/main.c src/foo.c ;
# --- END Jamfile ---

$ ftjam
...found 19 target(s)...
...updating 3 target(s)...
Cc build/src/main.o
Assembler messages:
FATAL: can't create build/src/main.o: No such file or directory

cc -c -o build/src/main.o  -O  -I. src/main.c

...failed Cc build/src/main.o ...
Cc build/src/foo.o
Assembler messages:
FATAL: can't create build/src/foo.o: No such file or directory

cc -c -o build/src/foo.o  -O  -I. src/foo.c

...failed Cc build/src/foo.o ...
...skipped myprog for lack of src/main.o...
...failed updating 2 target(s)...
...skipped 1 target(s)...

$ mkdir build/src

$ ftjam
...found 19 target(s)...
...updating 3 target(s)...
Cc build/src/main.o
Cc build/src/foo.o
Link build/myprog
Chmod1 build/myprog
...updated 3 target(s)...

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