| /freebsd-13.1/contrib/googletest/googletest/docs/ |
| H A D | XcodeGuide.md | 10 …the `gtest.xcodeproj` in the `googletest-read-only/xcode/` directory and build the gtest.framework.
12 …1. Add the gtest.framework to your project and add it to the "Link Binary with Libraries" build ph…
14 …_FRAMEWORK\_PATH" with a value equal to the path to the framework containing the gtest.framework r…
42 The next step is to build and add the gtest.framework to your own project. This guide describes two…
44 …framework manually. Then, add the built framework into your project using the "Add->Existing Frame…
45 …framework every time the source updates. to do this, you'll need to add the gtest.xcodeproj file, …
51 Next, you'll want to add gtest.framework in two different ways, depending upon which option you cho…
53 …e will need to know that you are linking against the gtest.framework. Add the gtest.framework to t…
54 …framework to your "Link Binary with Libraries" build phase of your test target. In addition, you'l…
58 …framework. Instead, the dynamic linker must be told at runtime to search for the framework in anot…
[all …]
|
| /freebsd-13.1/sys/contrib/openzfs/config/ |
| H A D | intlmacosx.m4 | 24 LIBS="$LIBS -Wl,-framework -Wl,CoreFoundation"
34 …to 1 if you have the Mac OS X function CFPreferencesCopyAppValue in the CoreFoundation framework.])
39 LIBS="$LIBS -Wl,-framework -Wl,CoreFoundation"
49 …efine to 1 if you have the Mac OS X function CFLocaleCopyCurrent in the CoreFoundation framework.])
53 LIBS="$LIBS -Wl,-framework -Wl,CoreFoundation"
63 …if you have the Mac OS X function CFLocaleCopyPreferredLanguages in the CoreFoundation framework.])
69 INTL_MACOSX_LIBS="-Wl,-framework -Wl,CoreFoundation"
|
| /freebsd-13.1/contrib/googletest/googletest/xcode/gtest.xcodeproj/ |
| H A D | project.pbxproj | 160 remoteInfo = "gtest-framework";
167 remoteInfo = "gtest-framework";
261 …A70F4C /* gtest.framework */ = {isa = PBXFileReference; explicitFileType = wrapper.framework; incl…
316 4539C8FF0EC27F6400A70F4C /* gtest.framework */,
508 name = "gtest_unittest-framework";
525 name = "sample1_unittest-framework";
613 name = "gtest-framework";
865 PRODUCT_NAME = "gtest_unittest-framework";
875 PRODUCT_NAME = "gtest_unittest-framework";
884 PRODUCT_NAME = "sample1_unittest-framework";
[all …]
|
| /freebsd-13.1/sys/contrib/openzfs/contrib/intel_qat/patch/ |
| H A D | 0001-timespec.diff | 11 …/performance/framework/linux/kernel_space/cpa_sample_code_utils.c b/quickassist/lookaside/access_l…
13 --- a/quickassist/lookaside/access_layer/src/sample_code/performance/framework/linux/kernel_space/c…
14 +++ b/quickassist/lookaside/access_layer/src/sample_code/performance/framework/linux/kernel_space/c…
|
| /freebsd-13.1/sys/opencrypto/ |
| H A D | cryptodev_if.m | 45 * The crypto framework invokes this method on each crypto driver when
80 * Invoked by the crypto framework to initialize driver-specific data
81 * for a crypto session. The framework allocates and zeroes the
102 * The crypto framework invokes this method when tearing down a crypto
103 * session. After this callback returns, the framework will explicitly
121 * The crypto framework invokes this method for each symmetric crypto
128 * framework and retried in the future.
152 * The crypto framework invokes this method for each asymmetric crypto
160 * framework and retried in the future.
|
| /freebsd-13.1/contrib/googletest/googletest/xcode/Samples/FrameworkSample/WidgetFramework.xcodeproj/ |
| H A D | project.pbxproj | 40 …AF3B400C7F239 /* Widget.framework in Frameworks */ = {isa = PBXBuildFile; fileRef = 8D07F2C80486CC…
85 …CD1D0 /* Widget.framework */ = {isa = PBXFileReference; explicitFileType = wrapper.framework; incl…
95 3B7EB1480E5AF3B400C7F239 /* Widget.framework in Frameworks */,
112 8D07F2C80486CC7A007CD1D0 /* Widget.framework */,
221 productReference = 8D07F2C80486CC7A007CD1D0 /* Widget.framework */;
222 productType = "com.apple.product-type.framework";
|
| /freebsd-13.1/contrib/bearssl/mk/ |
| H A D | mkT0.cmd | 5 rem provided with the .NET framework. We need framework 3.5 or later
7 rem implemented in the compiler provided with framework 2.0.50727).
|
| /freebsd-13.1/sys/mips/conf/ |
| H A D | std.AR724X | 6 # the majority of the kernel framework will be built as modules.
33 options TCP_HHOOK # hhook(9) framework for TCP
35 options PSEUDOFS #Pseudo-filesystem framework
|
| H A D | AR71XX_BASE | 31 options TCP_HHOOK # hhook(9) framework for TCP
35 options PSEUDOFS #Pseudo-filesystem framework
|
| H A D | std.AR5315 | 36 options TCP_HHOOK # hhook(9) framework for TCP
40 options PSEUDOFS #Pseudo-filesystem framework
|
| H A D | std.AR5312 | 37 options TCP_HHOOK # hhook(9) framework for TCP
41 options PSEUDOFS #Pseudo-filesystem framework
|
| H A D | std.AR91XX | 31 options TCP_HHOOK # hhook(9) framework for TCP
33 options PSEUDOFS #Pseudo-filesystem framework
|
| H A D | std.MALTA | 21 options TCP_HHOOK # hhook(9) framework for TCP
24 options PSEUDOFS #Pseudo-filesystem framework
|
| H A D | std.AR934X | 31 options TCP_HHOOK # hhook(9) framework for TCP
33 options PSEUDOFS #Pseudo-filesystem framework
|
| H A D | std.AR933X | 31 options TCP_HHOOK # hhook(9) framework for TCP
33 options PSEUDOFS #Pseudo-filesystem framework
|
| H A D | std.QCA955X | 30 options TCP_HHOOK # hhook(9) framework for TCP
32 options PSEUDOFS #Pseudo-filesystem framework
|
| H A D | QCA953X_BASE | 33 options TCP_HHOOK # hhook(9) framework for TCP
35 options PSEUDOFS #Pseudo-filesystem framework
|
| /freebsd-13.1/tools/tools/vhba/ |
| H A D | README | 8 *just enough* framework to be useful, plus some nominally common
13 are pretty much used to stress and test the FreeBSD CAM framework
|
| /freebsd-13.1/sys/contrib/device-tree/Bindings/cpufreq/ |
| H A D | cpufreq-st.txt | 5 from the SoC, then supplies the OPP framework with 'prop' and 'supported
6 hardware' information respectively. The framework is then able to read
|
| /freebsd-13.1/sys/mips/mediatek/ |
| H A D | std.rt2880 | 54 options PSEUDOFS # Pseude-filesystem framework
69 # FDT clock and pinctrl framework
|
| H A D | std.mediatek | 55 options PSEUDOFS # Pseude-filesystem framework
70 # FDT clock and pinctrl framework
|
| /freebsd-13.1/sys/contrib/device-tree/Bindings/thermal/ |
| H A D | thermal-zones.yaml | 44 A /thermal-zones node is required in order to use the thermal framework to
66 timers setup by the thermal framework and assumes that the thermal
75 framework and assumes that the thermal sensors in this zone
111 which the thermal framework needs to take action. The actions to
131 millicelsius. Any cooling action initiated by the framework is
196 cooling-device phandle limit specifier lets the framework
|
| /freebsd-13.1/sys/modules/tests/ |
| H A D | Makefile | 3 SUBDIR+= framework
|
| /freebsd-13.1/sys/arm/conf/ |
| H A D | NOTES | 14 options INTRNG # Include INTRNG framework
35 device xdma # xDMA framework for SoC on-chip dma controllers
|
| /freebsd-13.1/contrib/googletest/googlemock/ |
| H A D | README.md | 3 The Google C++ mocking framework.
7 Google's framework for writing and using C++ mock classes.
79 Google Mock is not a testing framework itself. Instead, it needs a
80 testing framework for writing tests. Google Mock works seamlessly
82 …e it with [any C++ testing framework](../../master/googlemock/docs/ForDummies.md#using-google-mock…
91 framework, although it will still need Google Test. Please read
93 ../../master/googlemock/docs/ForDummies.md#using-google-mock-with-any-testing-framework)
|