You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ripple.apache.org by gt...@apache.org on 2013/03/11 16:11:04 UTC
[35/50] [abbrv] git commit: The section for what a build target is
could use a better description.
The section for what a build target is could use a better description.
Before, it seemed to not give full context to what a build target is,
Project: http://git-wip-us.apache.org/repos/asf/incubator-ripple/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-ripple/commit/c52be480
Tree: http://git-wip-us.apache.org/repos/asf/incubator-ripple/tree/c52be480
Diff: http://git-wip-us.apache.org/repos/asf/incubator-ripple/diff/c52be480
Branch: refs/heads/master
Commit: c52be480cda76f73d92ba35c67b80071a932c97a
Parents: 73494e6
Author: Brent Lintner <br...@gmail.com>
Authored: Thu Feb 14 10:52:23 2013 -0500
Committer: Brent Lintner <br...@gmail.com>
Committed: Thu Feb 14 10:52:23 2013 -0500
----------------------------------------------------------------------
HACKING.md | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-ripple/blob/c52be480/HACKING.md
----------------------------------------------------------------------
diff --git a/HACKING.md b/HACKING.md
index 29f88bf..1df477c 100644
--- a/HACKING.md
+++ b/HACKING.md
@@ -148,12 +148,12 @@ You can build via `jake build`.
Any files used are located in `build/*`. To start, check out `build/build.js`.
+During build, there is the concept of a build target. A build target is for packaging project components (usually `lib/client`) into usable solutions. For example, there is a target for creating Ripple as a Chrome Extension, while there is also a "hosted" target that is used by the CLI & NPM package.
+
For any target specific builds (that have any assets placed in `targets/target_name`), there are corresponding modules that build said targets, which are located in `build/targets/*`.
For every target that is built, they should (and will) be placed in the `pkg/` folder.
-Note: A target can be anything, really. There is a Chrome Extension target that does not include any of the server/cli components (i.e. some can be used in conjunction with each other).
-
## Using Built Targets
There are various ways in which to use aspects of Ripple.