| /openbmc/openbmc/meta-openembedded/meta-webserver/recipes-php/phpmyadmin/phpmyadmin/ |
| H A D | apache.conf | 5 <Directory /usr/share/phpmyadmin>
21 </Directory>
24 <Directory /usr/share/phpmyadmin/setup>
31 </Directory>
34 <Directory /usr/share/phpmyadmin/libraries>
37 </Directory>
38 <Directory /usr/share/phpmyadmin/setup/lib>
41 </Directory>
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | temporary-source-code.rst | 11 :term:`Build Directory`, and then you can force a re-compile and quickly
16 build packages is available in the :term:`Build Directory` as defined by the
19 :term:`Source Directory`::
59 As an example, assume a Source Directory top-level folder named
60 ``poky``, a default :term:`Build Directory` at ``poky/build``, and a
|
| H A D | custom-template-configuration-directory.rst | 3 Creating a Custom Template Configuration Directory
9 ``bblayers.conf`` that are created in a new :term:`Build Directory`) and a custom
23 The above command takes the config files from the currently active :term:`Build Directory` under ``…
35 :term:`Build Directory` ``conf`` directory.
|
| H A D | error-reporting-tool.rst | 11 :term:`Source Directory` (e.g. ``poky``).
32 :term:`Build Directory`::
74 :term:`Build Directory`::
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | terms.rst | 62 :term:`Build Directory`
65 script that is found in the Source Directory
67 :term:`TOPDIR` variable points to the :term:`Build Directory`.
69 You have a lot of flexibility when creating the :term:`Build Directory`.
71 examples assume your :term:`Source Directory` is named ``poky``:
73 - Create the :term:`Build Directory` inside your Source Directory and let
74 the name of the :term:`Build Directory` default to ``build``:
81 - Create the :term:`Build Directory` inside your home directory and
89 :term:`Build Directory`. Any intermediate folders in the pathname
90 must exist. This next example creates a :term:`Build Directory`
[all …]
|
| H A D | structure.rst | 4 Source Directory Structure
7 The :term:`Source Directory` consists of numerous files,
10 describes the Source Directory and gives information about those files
13 For information on how to establish a local Source Directory on your
21 names that contain spaces. Be sure that the Source Directory you use
29 This section describes the top-level components of the :term:`Source Directory`.
59 where the source tree is combined with the output. The :term:`Build Directory`
64 directory separate from the :term:`Source Directory` by
66 information on separating output from your local Source Directory files
70 See the ":ref:`The Build Directory --- build/ <structure-build>`" section for details
[all …]
|
| /openbmc/openbmc-test-automation/openpower/ |
| H A D | test_nmi_interface.robot | 35 Verify Crash Dump Directory After NMI Inject
40 Verify Crash Dump Directory After NMI Inject
45 Wait Until Keyword Succeeds 1 min 10 sec Verify Crash Dump Directory
83 Verify Crash Dump Directory
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/adcli/ |
| H A D | adcli_0.9.2.bb | 1 SUMMARY = "Active Directory enrollment"
2 DESCRIPTION = "A helper library and tools for Active Directory client operations."
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/msktutil/ |
| H A D | msktutil_1.2.1.bb | 1 SUMMARY = "Program for interoperability with Active Directory"
2 DESCRIPTION = "Msktutil creates user or computer accounts in Active Directory, \
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-obtain.rst | 31 #. *Go to the Installers Directory:* Go to
94 Yocto Project :term:`Source Directory`
104 the Source Directory (i.e. ``poky``), run the
111 Among other things, the script creates the :term:`Build Directory`, which
112 is ``build`` in this case and is located in the Source Directory. After
118 file in your :term:`Build Directory` matches the architecture
125 :term:`Build Directory` is correctly set.
156 ``tmp/deploy/sdk`` in the :term:`Build Directory`.
173 ``tmp/deploy/sdk`` in the :term:`Build Directory`. Here is an example::
256 Installed Standard SDK Directory Structure
[all …]
|
| /openbmc/openbmc/poky/documentation/toaster-manual/ |
| H A D | setup-and-use.rst | 18 :term:`Source Directory` (e.g. ``poky``)::
26 Next, from the :term:`Build Directory` (e.g. ``poky/build``), start Toaster
112 The Directory for Cloning Layers
116 Directory (i.e. ``poky``) to clone any layers needed for your builds.
124 The Build Directory
127 Toaster creates a :term:`Build Directory` within your Source Directory (e.g.
134 Toaster to use ``$TOASTER_DIR/build`` as the :term:`Build Directory`.
155 is the :term:`Build Directory`, invoke the ``createsuperuser`` command from
182 parameters such as the :term:`Build Directory`, layer sources, default variable
320 the location of the Toaster :term:`Build Directory`. The Toaster
[all …]
|
| /openbmc/linux/Documentation/PCI/endpoint/ |
| H A D | pci-endpoint-cfs.rst | 22 Directory Structure
120 | <Directory: EPC name>/
124 | <Directory: EPF driver>/
125 | <Directory: EPF device>/
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | dmtf_tools_utils.robot | 19 # rsv_dir_path Directory path for rsv tool (e.g. "Redfish-Service-Validator").
32 # rsv_dir_path Directory path for rsv tool (e.g. "Redfish-Service-Validator").
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/hdf5/files/ |
| H A D | 0001-cmake-remove-build-flags.patch | 55 - Module Directory: @CMAKE_Fortran_MODULE_DIRECTORY@
56 + Module Directory:
|
| /openbmc/webui-vue/docs/customization/ |
| H A D | readme.md | 8 ## SCSS Directory Structure
10 ### `bmc` Directory
27 ### `custom` Directory
29 The `custom` Directory imports all the styles needed to customize the UI. These
63 ### `helpers` Directory
262 ### `bootstrap` Directory
|
| /openbmc/openbmc/poky/meta/recipes-devtools/gcc/gcc/ |
| H A D | 0013-Ensure-target-gcc-headers-can-be-included.patch | 33 # Directory in which the compiler finds libraries etc.
36 # Directory in which the compiler finds executables
38 # Directory in which all plugin resources are installed
|
| /openbmc/phosphor-debug-collector/ |
| H A D | meson.options | 36 description: 'Directory where core dumps are placed',
50 description: 'Directory where bmc dumps are placed',
129 description: 'Directory where fault logs are placed',
|
| /openbmc/openbmc/poky/meta/recipes-sato/matchbox-desktop/files/vfolders/ |
| H A D | All.directory | 4 Type=Directory
|
| H A D | Applications.directory | 5 Type=Directory
|
| H A D | Games.directory | 7 Type=Directory
|
| H A D | Settings.directory | 7 Type=Directory
|
| /openbmc/linux/tools/memory-model/scripts/ |
| H A D | runlitmushist.sh | 28 echo Directory \"litmus\" missing, aborting run.
|
| /openbmc/u-boot/doc/ |
| H A D | README.socfpga | 120 input_qts_dir - Directory with compiled Quartus project
122 input_bsp_dir - Directory with generated bsp containing
124 output_dir - Directory to store the U-Boot compatible
|
| /openbmc/linux/Documentation/mm/ |
| H A D | page_tables.rst | 102 - **pmd**, `pmd_t`, `pmdval_t` = **Page Middle Directory**, the hierarchy right
105 - **pud**, `pud_t`, `pudval_t` = **Page Upper Directory** was introduced after
109 - **p4d**, `p4d_t`, `p4dval_t` = **Page Level 4 Directory** was introduced to
116 - **pgd**, `pgd_t`, `pgdval_t` = **Page Global Directory** - the Linux kernel
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/freediameter/files/ |
| H A D | install_test.patch | 18 +SET(INSTALL_TEST_SUFFIX /opt/${FD_PROJECT_NAME}-tests CACHE PATH "Directory where the test…
|