[SERVER-9572] Make target build directory controllable via an option to SCons. Created: 03/May/13  Updated: 11/Jul/16  Resolved: 06/Aug/14

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: 2.7.4

Type: Improvement Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: Unassigned
Resolution: Done Votes: 0
Labels: build-system-cleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Comments   
Comment by Jonathan Reams [ 06/Aug/14 ]

This was fixed during 2.7.4, but wasn't updated.

Comment by Githook User [ 14/Jul/14 ]

Author:

{u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}

Message: SERVER-9570 SERVER-9572 Default install prefix to subdirectory of selectable build dir

In addition, move the .scons directory to a subdirectory of the build
directory. This makes all build artifacts not installed to '#' live under the
build directory.
Branch: master
https://github.com/mongodb/mongo/commit/a6a55dfeb3ce0edebc7d58a119b41fe590b61e07

Comment by Andrew Morrow (Inactive) [ 25/Feb/14 ]

It is somewhat different in that --variant-dir only specifies a path under #build. We could probably change that easily enough so that if the argument to --variant-dir started with a '/' it was considered absolute, or something like that.

Comment by Eric Milkie [ 25/Feb/14 ]

Cool, so is this --variant-dir or something different? I guess you can only specify a relative path with variant-dir, or does it support absolute paths?

Comment by Andrew Morrow (Inactive) [ 25/Feb/14 ]

I intended this as the variant directory, so you could say:

cd /my/mongodb/src/directory
scons --build-dir=/path/to/my/ssd/build

And all of the object files would end up in /path/to/my/ssd/build.

Ideally, if we had hygenic builds, you could do this even when /my/mongodb/src/directory was mounted read-only.

Comment by Eric Milkie [ 25/Feb/14 ]

Is this the variant directory or the install directory?

Generated at Thu Feb 08 03:20:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.