commit | b85982b3cb9b3971173f77c7575b53b3ac00e774 | [log] [tgz] |
---|---|---|
author | Sergey Semushin <predelnik@gmail.com> | Sat Mar 23 00:12:01 2019 +0300 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Mar 26 16:03:38 2019 +0000 |
tree | c66dd4d83691247376ad69903b18cb8e6bfd8f15 | |
parent | 9434c3d281eefb5c3764b5a0575feec9c59bd095 [diff] |
visual_studio_writer: Make OutDir equal to $(SolutionDir). Currently gn writes relative path as 'OutDir' in Visual Studio project, this is problematic because changing working directory for debug purposes leads to inability to launch an executable. Instead gn should either write absoulte directory or similarly to default Visual Studio configuration for the project use project/solution specific variables. By default VS generates the following 'OutDir' for its project $(SolutionDir)$(Platform)\$(Configuration)\ but for gn position of executable seems to always be equal to $(SolutionDir) currently. So writing just $(SolutionDir) should work as well as current way and would not be disrupted by changing working directory. Change-Id: I4ad0394287c8e6ccde1f4fd74762cc9650994463 Reviewed-on: https://gn-review.googlesource.com/c/gn/+/4420 Reviewed-by: Brett Wilson <brettw@chromium.org> Commit-Queue: Brett Wilson <brettw@chromium.org>
GN is a meta-build system that generates build files for Ninja. There is documentation in docs/ and a presentation on it.
You can download the latest version of GN binary for Linux, macOS and Windows.
Alternatively, you can build GN from source:
git clone https://gn.googlesource.com/gn cd gn python build/gen.py ninja -C out # To run tests: out/gn_unittests
On Windows, it is expected that cl.exe
, link.exe
, and lib.exe
can be found in PATH
, so you'll want to run from a Visual Studio command prompt, or similar.
On Linux and Mac, the default compiler is clang++
, a recent version is expected to be found in PATH
. This can be overridden by setting CC
, CXX
, and AR
.
If you find a bug, you can see if it is known or report it in the bug database.
GN uses Gerrit for code review. The short version of how to patch is:
Register at https://gn-review.googlesource.com. ... edit code ... ninja -C out && out/gn_unittests
Then, to upload a change for review:
git commit git cl upload --gerrit
When revising a change, use:
git commit --amend git cl upload --gerrit
which will add the new changes to the existing code review, rather than creating a new one.
We ask that all contributors sign Google's Contributor License Agreement (either individual or corporate as appropriate, select ‘any other Google project’).
You may ask questions and follow along w/ GN‘s development on Chromium’s gn-dev@ Google Group.