| /openbsd-src/gnu/usr.bin/perl/cpan/CPAN-Meta/t/data-test/ |
| H A D | restrictive-1_4.yml | 2 abstract: 'Build and install Perl modules'
5 …ns, bug reports, and patches should be sent to the\nModule-Build mailing list at <module-build@per…
10 generated_by: 'Module::Build version 0.3608'
13 url: http://module-build.sourceforge.net/META-spec-v1.4.html
15 name: Module-Build
17 Module::Build:
18 file: lib/Module/Build.pm
20 Module::Build::Base:
21 file: lib/Module/Build/Base.pm
23 Module::Build::Compat:
[all …]
|
| H A D | META-1_4.yml | 2 abstract: 'Build and install Perl modules'
5 …ns, bug reports, and patches should be sent to the\nModule-Build mailing list at <module-build@per…
10 generated_by: 'Module::Build version 0.3608'
13 url: http://module-build.sourceforge.net/META-spec-v1.4.html
15 name: Module-Build
17 Module::Build:
18 file: lib/Module/Build.pm
20 Module::Build::Base:
21 file: lib/Module/Build/Base.pm
23 Module::Build::Compat:
[all …]
|
| H A D | unicode.yml | 2 abstract: 'Build and install Perl modules'
5 …ns, bug reports, and patches should be sent to the\nModule-Build mailing list at <module-build@per…
10 generated_by: 'Module::Build version 0.3608'
13 url: http://module-build.sourceforge.net/META-spec-v1.4.html
15 name: Module-Build
17 Module::Build:
18 file: lib/Module/Build.pm
20 Module::Build::Base:
21 file: lib/Module/Build/Base.pm
23 Module::Build::Compat:
[all …]
|
| /openbsd-src/gnu/usr.bin/perl/cpan/CPAN-Meta/t/data-fail/ |
| H A D | META-1_4.yml | 2 abstract: 'Build and install Perl modules'
5 …ns, bug reports, and patches should be sent to the\nModule-Build mailing list at <module-build@per…
10 generated_by: 'Module::Build version 0.3608'
13 url: http://module-build.sourceforge.net/META-spec-v1.4.html
15 name: Module-Build
17 Module::Build:
18 file: lib/Module/Build.pm
20 Module::Build::Base:
21 file: lib/Module/Build/Base.pm
23 Module::Build::Compat:
[all …]
|
| /openbsd-src/gnu/usr.bin/perl/cpan/CPAN-Meta/t/data-fixable/ |
| H A D | meta-spec-version-trailing-zeros.yml | 2 abstract: 'Build and install Perl modules'
5 …ns, bug reports, and patches should be sent to the\nModule-Build mailing list at <module-build@per…
10 generated_by: 'Module::Build version 0.3608'
13 url: http://module-build.sourceforge.net/META-spec-v1.4.html
15 name: Module-Build
17 Module::Build:
18 file: lib/Module/Build.pm
20 Module::Build::Base:
21 file: lib/Module/Build/Base.pm
23 Module::Build::Compat:
[all …]
|
| H A D | invalid-meta-spec-version.yml | 2 abstract: 'Build and install Perl modules'
5 …ns, bug reports, and patches should be sent to the\nModule-Build mailing list at <module-build@per…
10 generated_by: 'Module::Build version 0.3608'
13 url: http://module-build.sourceforge.net/META-spec-v1.4.html
15 name: Module-Build
17 Module::Build:
18 file: lib/Module/Build.pm
20 Module::Build::Base:
21 file: lib/Module/Build/Base.pm
23 Module::Build::Compat:
[all …]
|
| H A D | META-1_4.yml | 4 …ns, bug reports, and patches should be sent to the\nModule-Build mailing list at <module-build@per…
9 generated_by: 'Module::Build version 0.3608'
12 url: http://module-build.sourceforge.net/META-spec-v1.4.html
14 name: Module-Build
16 Module::Build:
17 file: lib/Module/Build.pm
19 Module::Build::Base:
20 file: lib/Module/Build/Base.pm
22 Module::Build::Compat:
23 file: lib/Module/Build/Compat.pm
[all …]
|
| /openbsd-src/gnu/llvm/clang/tools/scan-build-py/ |
| H A D | README.md | 1 scan-build
4 A package designed to wrap a build so that all calls to gcc/clang are
6 the clang static analyzer. Includes intercept-build tool, which logs
7 the build, as well as scan-build tool, which logs the build and runs
30 $ scan-build <your build command>
34 $ intercept-build <your build command>
39 $ analyze-build
49 $ intercept-build <your build command>
54 $ analyze-build --ctu
62 $ analyze-build --ctu-collect-only
[all …]
|
| H A D | CMakeLists.txt | 2 "analyze-build"
3 "intercept-build"
4 "scan-build")
35 if ("${BinFile}" STREQUAL "scan-build")
36 # Need to rename scan-build to scan-build-py to prevent overwriting
37 # scan-build Perl implementation.
38 add_custom_command(OUTPUT ${CMAKE_BINARY_DIR}/bin/scan-build-py
42 ${CMAKE_CURRENT_SOURCE_DIR}/bin/scan-build
43 ${CMAKE_BINARY_DIR}/bin/scan-build-py
44 DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/bin/scan-build)
[all …]
|
| /openbsd-src/gnu/llvm/clang/www/analyzer/ |
| H A D | scan-build.html | 5 <title>scan-build: running the analyzer from the command line</title>
16 <h1>scan-build: running the analyzer from the command line</h1>
22 <p><b>scan-build</b> is a command line utility that enables a user to run the
23 static analyzer over their codebase as part of performing a regular build (from
27 <p>During a project build, as source files are compiled they are also analyzed
30 <p>Upon completion of the build, results are then presented to the user within a
33 <h3>Will it work with any build system?</h3>
34 <p><b>scan-build</b> has little or no knowledge about how you build your code.
36 (hopefully) change your build to use a "fake" compiler instead of the
37 one that would normally build your project. This fake compiler executes either
[all …]
|
| H A D | installation.html | 20 href="/scan-build.html">instructions</a> on using <tt>scan-build</tt> to
28 <p>Builds are released frequently. Often the differences between build
31 builds, especially if the build you are using is more than a couple
34 <p>The latest build is:
47 <p>To use a package build, simply unpack it anywhere. If the build
60 <li><b>scan-build</b>: <tt>scan-build</tt> is the high-level command line utility for running the a…
62 utility to <tt>scan-build</tt>, <tt>scan-view</tt> is used to view
63 analysis results generated by <tt>scan-build</tt>. There is an option
64 that one can pass to <tt>scan-build</tt> to cause <tt>scan-view</tt> to
65 run as soon as it the analysis of a build completes</li>
[all …]
|
| /openbsd-src/gnu/llvm/llvm/docs/ |
| H A D | AdvancedBuilds.rst | 2 Advanced Build Configurations
11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake
12 does not build the project, it generates the files needed by your build tool
22 Many of the build configurations mentioned on this documentation page can be
24 file that sets the necessary flags for a specific build configuration. The caches
32 The Clang CMake build system supports bootstrap (aka multi-stage) builds. At a
33 high level a multi-stage build is a chain of builds that pass data from one
35 bootstrap build.
37 In a simple two-stage bootstrap build, we build clang using the system compiler,
38 then use that just-built clang to build clang again. In CMake this simplest form
[all …]
|
| H A D | HowToAddABuilder.rst | 2 How To Add Your Build Configuration To LLVM Buildbot Infrastructure
8 This document contains information about adding a build configuration and
18 the build.
20 attached to this machine will be completely silent by default when the build
44 maintains the build configuration. Generally, operational responsibility lies
54 Volunteers can provide their build machines to work as build workers to
59 #. Check the existing build configurations to make sure the one you are
66 actually build your configuration successfully. Please check what degree
67 of parallelism (-j param) would give the fastest build. You can build
79 it), buildbot-worker access name and password the build master will be using
[all …]
|
| H A D | HowToBuildWithPGO.rst | 2 How To Build Clang and LLVM with Profile-Guided Optimizations
12 This guide walks you through how to build Clang with PGO, though it also applies
15 If you want to build other software with PGO, see the `end-user documentation
53 - uses the instrumented Clang to build Clang, LLVM, and all of the other
74 how to build Clang/LLVM with PGO.
81 1. Build a standard Release Clang and the relevant libclang_rt.profile library
82 2. Build Clang using the Clang you built above, but with instrumentation
90 4. Build a final release Clang (along with whatever other binaries you need)
95 1. Configure a Clang build as you normally would. It's highly recommended that
96 you use the Release configuration for this, since it will be used to build
[all …]
|
| /openbsd-src/gnu/llvm/llvm/utils/gn/ |
| H A D | README.rst | 13 *Warning* The GN build is experimental and best-effort. It might not work,
15 necessary. LLVM's official build system is CMake, if in doubt use that.
16 If you add files, you're expected to update the CMake build but you don't need
17 to update GN build files. Reviewers should not ask authors to update GN build
18 files. Keeping the GN build files up-to-date is on the people who use the GN
19 build.
23 which then shell out to ninja for the actual build.
25 The main motivation behind the GN build is that some people find it more
27 just parts of LLVM, and embedding the LLVM GN build from other builds are
28 non-goals for the GN build.
[all …]
|
| /openbsd-src/gnu/gcc/gcc/doc/ |
| H A D | configterms.texi | 10 The configure and build process has a long and colorful history, and can
16 There are three system names that the build knows about: the machine you
17 are building on (@dfn{build}), the machine that you are building for
20 @option{--build=}, @option{--host=}, and @option{--target=}.
22 Specifying the host without specifying the build should be avoided, as
24 is also the build, which may not be true.
26 If build, host, and target are all the same, this is called a
27 @dfn{native}. If build and host are the same but target is different,
28 this is called a @dfn{cross}. If build, host, and target are all
31 on the build at that time). If host and target are the same, but build
[all …]
|
| /openbsd-src/gnu/usr.bin/gcc/gcc/doc/ |
| H A D | configterms.texi | 10 The configure and build process has a long and colorful history, and can
16 There are three system names that the build knows about: the machine you
17 are building on (@dfn{build}), the machine that you are building for
20 @option{--build=}, @option{--host=}, and @option{--target=}.
22 Specifying the host without specifying the build should be avoided, as
24 is also the build, which may not be true.
26 If build, host, and target are all the same, this is called a
27 @dfn{native}. If build and host are the same but target is different,
28 this is called a @dfn{cross}. If build, host, and target are all
31 on the build at that time). If host and target are the same, but build
[all …]
|
| /openbsd-src/gnu/llvm/clang/tools/scan-build/ |
| H A D | CMakeLists.txt | 1 option(CLANG_INSTALL_SCANBUILD "Install the scan-build tool" ON)
7 scan-build
8 scan-build.bat
18 scan-build
32 scan-build.1)
51 COMPONENT scan-build)
65 COMPONENT scan-build)
79 COMPONENT scan-build)
83 add_custom_command(OUTPUT ${CMAKE_BINARY_DIR}/share/scan-build/${ShareFile}
85 ${CMAKE_BINARY_DIR}/share/scan-build
[all …]
|
| /openbsd-src/share/man/man8/ |
| H A D | release.8 | 20 There are several steps necessary to build a release:
26 Build and install a new kernel.
28 Build a new base system.
32 Build and install Xenocara.
46 To build a
58 .Sy build
103 .Ss 2. Build and install a new kernel
104 Always build and install a new kernel and reboot before
115 Create the build directory and configuration file,
128 .Ss 3. Build a new base system
[all …]
|
| /openbsd-src/gnu/llvm/llvm/utils/gn/secondary/compiler-rt/lib/ubsan/ |
| H A D | BUILD.gn | 28 configs -= [ "//llvm/utils/gn/build:llvm_code" ]
29 configs += [ "//llvm/utils/gn/build:crt_code" ]
55 configs -= [ "//llvm/utils/gn/build:llvm_code" ]
56 configs += [ "//llvm/utils/gn/build:crt_code" ]
62 configs -= [ "//llvm/utils/gn/build:llvm_code" ]
63 configs += [ "//llvm/utils/gn/build:crt_code" ]
69 configs -= [ "//llvm/utils/gn/build:llvm_code" ]
70 configs += [ "//llvm/utils/gn/build:crt_code" ]
76 configs -= [ "//llvm/utils/gn/build:llvm_code" ]
77 configs -= [ "//llvm/utils/gn/build:no_rtti" ]
[all …]
|
| /openbsd-src/gnu/usr.bin/gcc/contrib/regression/ |
| H A D | objs-gcc.sh | 3 # Build tools for testing GCC.
21 # btest <target> <source> <prefix> <state> <build>
36 # BUILD is a temporary directory that this script will
37 # delete and recreate, containing the build tree.
38 BUILD=$5
47 # build the build failed
48 # regress-<n> the build succeeded, but there were <n>
50 # pass build succeeded and there were no regressions
52 # in BUILD_LOG, the output of the build
80 # Nuke $BUILD and recreate it.
[all …]
|
| /openbsd-src/share/man/man1/ |
| H A D | dpb.1 | 47 is used to build ports on a cluster of machines, or on a single machine
75 to build as parameters.
81 to build, or a filename that contains pkgpaths (one per line).
103 In order to build on a cluster, the ports tree itself should be identical
126 .Pa ${DISTDIR}/build-stats .
182 Build packages for given architecture, selecting relevant hosts from the
197 Explicitly prime the heuristics module with a previous build log,
198 so that packages that take a long time to build will happen earlier.
200 .Pa %f/build-stats/%a
203 Don't clean port working directories after build.
[all …]
|
| /openbsd-src/gnu/usr.bin/gcc/gcc/testsuite/gcc.c-torture/execute/ |
| H A D | 921029-1.c | 5 build(long h, long l) in build() function
17 if (build(0, 1) != 0x0000000000000001LL) in main()
19 if (build(0, 0) != 0x0000000000000000LL) in main()
21 if (build(0, 0xFFFFFFFF) != 0x00000000FFFFFFFFLL) in main()
23 if (build(0, 0xFFFFFFFE) != 0x00000000FFFFFFFELL) in main()
25 if (build(1, 1) != 0x0000000100000001LL) in main()
27 if (build(1, 0) != 0x0000000100000000LL) in main()
29 if (build(1, 0xFFFFFFFF) != 0x00000001FFFFFFFFLL) in main()
31 if (build(1, 0xFFFFFFFE) != 0x00000001FFFFFFFELL) in main()
33 if (build(0xFFFFFFFF, 1) != 0xFFFFFFFF00000001LL) in main()
[all …]
|
| /openbsd-src/gnu/llvm/libcxx/docs/ |
| H A D | BuildingLibcxx.rst | 25 The default build
30 umbrella, they are different in nature from other build tools, so it makes sense
31 to treat them as a separate set of entities. The default build can be achieved
38 $ mkdir build
39 …$ cmake -G Ninja -S runtimes -B build -DLLVM_ENABLE_RUNTIMES="libcxx;libcxxabi;libunwind" # Config…
40 $ ninja -C build cxx cxxabi unwind # Build
41 $ ninja -C build check-cxx check-cxxabi check-unwind # Test
42 …$ ninja -C build install-cxx install-cxxabi install-unwind # Install
54 variables. If you wish to build the runtimes from a just-built Clang, the bootstrapping build
58 Bootstrapping build
[all …]
|
| /openbsd-src/gnu/llvm/llvm/cmake/modules/ |
| H A D | ChooseMSVCCRT.cmake | 9 # override that for each build type:
29 # Find the selected-by-CMake CRT for each build type, if any.
64 string(TOUPPER "${build_type}" build)
65 if (NOT LLVM_USE_CRT_${build})
66 get_current_crt(LLVM_USE_CRT_${build}
68 CMAKE_CXX_FLAGS_${build})
69 set(LLVM_USE_CRT_${build}
70 "${LLVM_USE_CRT_${build}}"
73 set_property(CACHE LLVM_USE_CRT_${build}
75 endif(NOT LLVM_USE_CRT_${build})
[all …]
|