sapling/install

#!/bin/bash

set -e

cd `git rev-parse --show-toplevel`

OUTPUT_DIR=buck-out/eden
mkdir -p $OUTPUT_DIR
EDEN_CLI="$OUTPUT_DIR/eden"
EDEN_DAEMON="$OUTPUT_DIR/daemon"

buck build --out $EDEN_CLI eden-cli
buck build --out $EDEN_DAEMON eden-daemon
sudo chmod 4755 $EDEN_DAEMON

echo "Eden executable available in: $EDEN_CLI"
Exclude the cpp_binary for the daemon from the python_binary for the CLI. Summary: This changes the way that Eden is built and deployed. * To build the binary that must be run as `root` (but quickly drops privileges), run `buck build eden-daemon`. * To build the CLI that communicates with the daemon (and does not require privileges), run `buck build eden-cli`. * To build both, run `buck build eden`. There is an example of how to build the various parts of Eden using Buck and how to package them up in the `install` script introduced by this revision. While here, I also cleaned up some of our build files and changed them to be parameterized between internal and external use. In both cases, the user gets the "unadorned" version of their primary build targets. This ensures that shortcuts such as: ``` buck test eden/fs/integration ``` do the right thing by default. Finally, I also made `find_default_config_dir()` and `find_default_daemon_binary()` lazy whereas `find_default_config_dir()` was previously eager. Reviewed By: simpkins Differential Revision: D3436245 fbshipit-source-id: 4dfbd59ed0d198620324f0705c462334bb5a7daf 2016-06-16 03:07:34 +03:00			`#!/bin/bash`

			`set -e`

			cd `git rev-parse --show-toplevel`

			`OUTPUT_DIR=buck-out/eden`
			`mkdir -p $OUTPUT_DIR`
Make oss install script less hacky using --out argument to `buck build`. Summary: The `--out` option was not available when this script was originally written, but this is exactly the sort of hacky shell-scripting it is desgined to replace. Reviewed By: mzlee Differential Revision: D4625460 fbshipit-source-id: 9c884d0274bb5ebda8c59a7c9c6b2be22efd6265 2017-02-28 23:09:56 +03:00			`EDEN_CLI="$OUTPUT_DIR/eden"`
			`EDEN_DAEMON="$OUTPUT_DIR/daemon"`
Exclude the cpp_binary for the daemon from the python_binary for the CLI. Summary: This changes the way that Eden is built and deployed. * To build the binary that must be run as `root` (but quickly drops privileges), run `buck build eden-daemon`. * To build the CLI that communicates with the daemon (and does not require privileges), run `buck build eden-cli`. * To build both, run `buck build eden`. There is an example of how to build the various parts of Eden using Buck and how to package them up in the `install` script introduced by this revision. While here, I also cleaned up some of our build files and changed them to be parameterized between internal and external use. In both cases, the user gets the "unadorned" version of their primary build targets. This ensures that shortcuts such as: ``` buck test eden/fs/integration ``` do the right thing by default. Finally, I also made `find_default_config_dir()` and `find_default_daemon_binary()` lazy whereas `find_default_config_dir()` was previously eager. Reviewed By: simpkins Differential Revision: D3436245 fbshipit-source-id: 4dfbd59ed0d198620324f0705c462334bb5a7daf 2016-06-16 03:07:34 +03:00
Make oss install script less hacky using --out argument to `buck build`. Summary: The `--out` option was not available when this script was originally written, but this is exactly the sort of hacky shell-scripting it is desgined to replace. Reviewed By: mzlee Differential Revision: D4625460 fbshipit-source-id: 9c884d0274bb5ebda8c59a7c9c6b2be22efd6265 2017-02-28 23:09:56 +03:00			`buck build --out $EDEN_CLI eden-cli`
			`buck build --out $EDEN_DAEMON eden-daemon`
			`sudo chmod 4755 $EDEN_DAEMON`
Exclude the cpp_binary for the daemon from the python_binary for the CLI. Summary: This changes the way that Eden is built and deployed. * To build the binary that must be run as `root` (but quickly drops privileges), run `buck build eden-daemon`. * To build the CLI that communicates with the daemon (and does not require privileges), run `buck build eden-cli`. * To build both, run `buck build eden`. There is an example of how to build the various parts of Eden using Buck and how to package them up in the `install` script introduced by this revision. While here, I also cleaned up some of our build files and changed them to be parameterized between internal and external use. In both cases, the user gets the "unadorned" version of their primary build targets. This ensures that shortcuts such as: ``` buck test eden/fs/integration ``` do the right thing by default. Finally, I also made `find_default_config_dir()` and `find_default_daemon_binary()` lazy whereas `find_default_config_dir()` was previously eager. Reviewed By: simpkins Differential Revision: D3436245 fbshipit-source-id: 4dfbd59ed0d198620324f0705c462334bb5a7daf 2016-06-16 03:07:34 +03:00
Make oss install script less hacky using --out argument to `buck build`. Summary: The `--out` option was not available when this script was originally written, but this is exactly the sort of hacky shell-scripting it is desgined to replace. Reviewed By: mzlee Differential Revision: D4625460 fbshipit-source-id: 9c884d0274bb5ebda8c59a7c9c6b2be22efd6265 2017-02-28 23:09:56 +03:00			`echo "Eden executable available in: $EDEN_CLI"`