Lines Matching refs:gn

21 `GN <https://gn.googlesource.com/gn/>`_ is a metabuild system. It always
40 #. ``llvm/utils/gn/get.py`` to download a prebuilt gn binary if you're on a
41    64-bit X86 system running Linux, macOS, or Windows. `Build gn yourself
42    <https://gn.googlesource.com/gn/#getting-started>`_ if you're on a different
45 #. ``llvm/utils/gn/gn.py gen out/gn`` to run GN and create build files.
46    ``out/gn`` is the build directory, it can have any name, and you can have as
47    many as you want, each with different build settings.  (The ``gn.py`` script
48    adds ``--dotfile=llvm/utils/gn/.gn --root=.`` and just runs regular ``gn``;
54 #. ``ninja -C out/gn check-lld`` to build all prerequisites for and run the LLD
58 the host arch. You can set build options by editing ``out/gn/args.gn``, for
60 ``llvm/utils/gn/gn.py args --list out/gn`` to see a list of all possible
61 options. After touching ``out/gn/args.gn`` just run ninja: it will re-invoke gn
64 GN has extensive built-in help; try e.g. ``llvm/utils/gn/gn.py help gen`` to see
66 online <https://gn.googlesource.com/gn/+/master/docs/reference.md>`_.
69 ``git ls-files '*.gn' '*.gni' | xargs llvm/utils/gn/gn.py format``
72 To not put ``BUILD.gn`` files into the main tree, they are all below
73 ``utils/gn/secondary``.  For example, the build file for ``llvm/lib/Support``
74 is in ``utils/gn/secondary/llvm/lib/Support``.
83 Run ``llvm/utils/gn/build/sync_source_lists_from_cmake.py`` to print a report
84 of which files need to be added to or removed from ``BUILD.gn`` files to
89 a new corresponding ``BUILD.gn`` file below ``llvm/utils/gn/secondary/``.
107   features. (Maybe there could be a script that writes args.gn based on the
138 variable, it wants the build to be controlled by .gn files.