summaryrefslogtreecommitdiffstats
path: root/build.ninja
Commit message (Collapse)AuthorAgeFilesLines
* Generate the entire graph not only for the 'all' target.Nicolas Despres2011-04-261-1/+1
| | | | | This way we can see the 'doxygen' target and also some object file we forgot to add as input of the link rule.
* Add the 'clean' tool.Nicolas Despres2011-04-261-1/+2
| | | | It removes built files either by rule or target or everything.
* Merge branch 'doxygen'Evan Martin2011-04-221-2/+2
|\
| * doxygen_mainpage is not an implicit dependency.Nicolas Despres2011-04-211-1/+1
| | | | | | | | This way it does not appear in the $in variables.
| * Adjust DOXYGEN_MAINPAGE rule description.Nicolas Despres2011-04-181-1/+1
| | | | | | | | Now it prints its output file.
| * Touching README and co triggers rebuild of doxygen.Nicolas Despres2011-04-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before the main page was an order-only dependency of the doxygen target. Thus, modification in the README did not triggers rebuild of the doxygen target as it ought to be. We have several ways to fix this issue: 1) Make the '$builddir/doxygen_mainpage' target an explicit dependency: build $builddir/doxygen_mainpage: doxygen_mainpage \ README HACKING COPYING | $doxygen_mainpage_generator build doxygen: doxygen doxygen.config $builddir/doxygen_mainpage 2) Duplicate the explicit dependencies of the '$builddir/doxygen_mainpage' target as implicit dependencies of the 'doxygen' target and keep the '$builddir/doxygen_mainpage' target as an order-only dependency: build $builddir/doxygen_mainpage: doxygen_mainpage \ README HACKING COPYING | $doxygen_mainpage_generator build doxygen: doxygen doxygen.config \ | README HACKING COPYING \ || $builddir/doxygen_mainpage I chose the first option since the doxygen executable only cares about its first argument. But it would not be the case for all commands. So I think introducing "slice" support for the $in and $out variables would be great. This way I could rewrite the 'doxygen' rule this way: rule doxygen command = doxygen $in[0] description = DOXYGEN $in[0] Note that using variables to avoid duplication does not work since the three files are seen as a single one: doxygen_deps = README HACKING COPYING build $builddir/doxygen_mainpage: doxygen_mainpage \ $doxygen_deps | $doxygen_mainpage_generator build doxygen: doxygen doxygen.config \ | $doxygen_deps \ || $builddir/doxygen_mainpage Maybe Ninja's philosophy expects the generators to generate the second option.
* | actually link in util_testEvan Martin2011-04-221-1/+2
|/
* Add doxygen support.Nicolas Despres2011-04-161-0/+15
|
* Move CanonicalizePath into util.h so it can be shared by the other modules.Thiago Farina2011-04-151-0/+1
| | | | | | Also add util_test.cc and move the CanonicalizePathTest into there. Signed-off-by: Thiago Farina <tfarina@chromium.org>
* move the implementation of GraphViz to source fileThiago Farina2011-03-071-2/+3
|
* inline.sh: rewrite for better portabilityEvan Martin2011-03-071-1/+1
|
* use a shell script to inline browse.pyEvan Martin2011-03-071-1/+8
| | | | | | | | | Relying on the inline-assembly trick was cute but it didn't work on other platforms; relying on xxd will make us depend on xxd being available. Instead, inline browse.py into a header using a shell script. (Making this work required fixing multiple bugs in ninja...)
* canonicalize paths loaded from depfilesEvan Martin2011-03-071-1/+2
| | | | | | | | | If a C file #includes "../foo.cc", then gcc will emit paths like "bar/../foo.cc" into the dependency file; canonicalize these when we load the file. Add a test module for testing the graph dirty recomputation directly, without all the build classes around it.
* move test support into test.*Evan Martin2011-03-061-1/+2
|
* factor browse out into its own fileEvan Martin2011-03-051-4/+6
|
* drop use of ar's T flagEvan Martin2011-03-051-1/+1
| | | | | | This produces smaller archives, which is important for large projects to not clobber your disk cache. But we are small (the resulting .a is ~3.5mb for debug) and it's not supported on older operating systems.
* move tools into a flagEvan Martin2011-01-281-1/+1
|
* remove introductory comments from build fileEvan Martin2011-01-261-21/+11
| | | | It's not intended to be human-friendly, so don't pretend.
* mark browse.py as an implicit depEvan Martin2011-01-241-1/+1
|
* allow implicit depsEvan Martin2011-01-231-2/+2
|
* split some of jumble outEvan Martin2011-01-191-2/+3
|
* use config file for build-time options; default to optEvan Martin2011-01-151-2/+6
|
* doc updatesEvan Martin2011-01-141-1/+6
|
* build file cleanupsEvan Martin2011-01-081-3/+6
|
* tweak build flagsEvan Martin2011-01-081-1/+1
|
* split out graph into its own headerEvan Martin2011-01-081-2/+3
|
* add a class for logging builds (commands + timing)Evan Martin2010-12-231-4/+8
|
* disable c++ deprecation warningsEvan Martin2010-12-191-1/+1
|
* remove @ from build.ninjaEvan Martin2010-12-191-19/+17
|
* rename docsEvan Martin2010-12-051-2/+2
|
* use "all" rule in graphEvan Martin2010-12-051-2/+1
|
* move src into subdirEvan Martin2010-12-051-10/+10
|
* add backtracerEvan Martin2010-11-301-2/+5
|
* switch to asciidocEvan Martin2010-11-291-1/+7
|
* subprocess code into new fileEvan Martin2010-11-291-2/+5
|
* add simple subproc manager and testEvan Martin2010-11-231-1/+2
|
* scope test ldflags to test binaryEvan Martin2010-11-231-1/+1
|
* split out builder into own fileEvan Martin2010-11-231-1/+2
|
* add "all" targetEvan Martin2010-11-141-0/+4
|
* clang safeEvan Martin2010-11-141-2/+4
|
* add simple graphingEvan Martin2010-11-091-0/+11
|
* check in build.ninja, since we're using itEvan Martin2010-11-071-0/+41
generated by cgit v0.12 at 2025-08-31 13:29:40 (GMT)