/openbmc/hiomapd/ |
H A D | .gitignore | 2 # https://github.com/github/gitignore/blob/master/Autotools.gitignore 57 # Autotools test infrastructure
|
/openbmc/phosphor-mboxd/ |
H A D | .gitignore | 2 # https://github.com/github/gitignore/blob/master/Autotools.gitignore 57 # Autotools test infrastructure
|
/openbmc/openbmc/poky/documentation/sdk-manual/ |
H A D | working-projects.rst | 7 You can use the SDK toolchain directly with Makefile and Autotools-based 10 Autotools-Based Projects 15 Autotools-based <GNU_Build_System>` workflow, which is outside of the 18 The following figure presents a simple Autotools workflow. 24 Follow these steps to create a simple Autotools-based "Hello World" 29 For more information on the GNU Autotools workflow, see the same 101 tool takes care of running the other Autotools such as ``aclocal``, 119 For an Autotools-based
|
H A D | using.rst | 17 You can use a standard SDK to work on Makefile and Autotools-based
|
H A D | extensible.rst | 23 Makefile and Autotools. See the 1164 - Autotools (``autoconf`` and ``automake``)
|
/openbmc/openbmc/poky/meta/classes-recipe/ |
H A D | autotools-brokensep.bbclass | 7 # Autotools class for recipes where separate build dir doesn't work
|
/openbmc/openpower-host-ipmi-flash/ |
H A D | .gitignore | 17 # Autotools
|
/openbmc/openpower-sbe-interface/ |
H A D | .gitignore | 17 # Autotools
|
/openbmc/openpower-debug-collector/ |
H A D | .gitignore | 2 # https://github.com/github/gitignore/blob/master/Autotools.gitignore
|
/openbmc/pam-ipmi/ |
H A D | .gitignore | 17 # Autotools
|
/openbmc/ibm-logging/ |
H A D | .gitignore | 2 # https://github.com/github/gitignore/blob/master/Autotools.gitignore
|
/openbmc/openpower-host-ipmi-oem/ |
H A D | .gitignore | 2 # https://github.com/github/gitignore/blob/master/Autotools.gitignore
|
/openbmc/openpower-dbus-interfaces/ |
H A D | .gitignore | 2 # https://github.com/github/gitignore/blob/master/Autotools.gitignore
|
/openbmc/ibm-dbus-interfaces/ |
H A D | .gitignore | 2 # https://github.com/github/gitignore/blob/master/Autotools.gitignore
|
/openbmc/obmc-console/ |
H A D | .gitignore | 2 # https://github.com/github/gitignore/blob/master/Autotools.gitignore
|
/openbmc/phosphor-user-manager/ |
H A D | .gitignore | 12 # https://github.com/github/gitignore/blob/master/Autotools.gitignore
|
/openbmc/openbmc-build-scripts/scripts/ |
H A D | unit-test.py | 533 which Autotools, Meson, CMake and possibly other build system drivers can 634 class Autotools(BuildSystem): class 636 super(Autotools, self).__init__(package, path) 1186 self.supported = [Meson, Autotools, CMake]
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/chrony/ |
H A D | chrony_4.6.1.bb | 47 # chrony does not use GNU Autotools.
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | new-recipe.rst | 70 application that builds using Autotools. Creating the base recipe using 521 - *Autotools:* If your source files have a ``configure.ac`` file, then 522 your software is built using Autotools. If this is the case, you just 525 When using Autotools, your recipe needs to inherit the 550 method other than Autotools or CMake. If this is the case, you 555 Even if your software is not being built by Autotools or CMake, you 719 - *Autotools and CMake:* If the software your recipe is building uses 720 Autotools or CMake, the OpenEmbedded build system understands how to 749 For the scenarios that do not use Autotools or CMake, you need to track 1229 Applications built with the Autotools such as ``autoconf`` and ``automake``
|
/openbmc/openbmc/poky/documentation/migration-guides/ |
H A D | migration-1.7.rst | 41 Autotools Class Changes
|
H A D | migration-1.6.rst | 238 building Autotools-based software that fails to build with a separate
|
/openbmc/openbmc/poky/meta/recipes-core/glib-2.0/ |
H A D | glib.inc | 118 # Autotools does this, meson does not
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | faq.rst | 371 Autotools configuration scripts, and other build systems are expected to
|
H A D | classes.rst | 88 :wikipedia:`GNU Autotools <GNU_Autotools>`. 95 that emulates Autotools. For more information, see the 2999 As an example, consider Autotools, which can require tests that must 3007 Autotools automatically picks up.
|
/openbmc/phosphor-mboxd/Documentation/ |
H A D | mbox_protocol.md | 118 The Autotools of this requires the autoconf-archive package for your
|