Searched refs:relevant (Results 1 – 25 of 914) sorted by relevance
12345678910>>...37
10 [[bbv2.builtin.features.relevant]]`relevant`::13 Indicates which other features are relevant for a given target. It is usually15 cases. Features which are not relevant will not affect target paths, and will18 * A feature will be considered relevant if any of the following are true22 ** It is a sub-feature of a relevant feature23 ** It has a sub-feature which is relevant24 ** It is a composite feature, and any composed feature is relevant26 ** It is a propagated feature and is relevant for any dependency27 ** It is relevant for any dependency created by the same main target29 value is relevant[all …]
38 # return <threadapi>$(api) <relevant>threadapi:<relevant>target-os ;
90 # Returns relevant base properties. This is used for computing91 # target paths, so it must return the expanded set of relevant94 rule base-relevant ( )96 if ! $(self.relevant-initialized)98 init-relevant ;100 return $(self.base-relevant) ;103 # Returns all properties marked as relevant by features-ps107 rule relevant ( features-ps )109 if ! $(self.relevant.$(features-ps))112 local features = [ $(features-ps).get <relevant> ] ;[all …]
31 # relevant for doing configuration builds. One can add additional relevant40 # This is the initial set of relevant features. Note that subfeature of all41 # relevant features are also considered relevant.409 rule get-relevant-features ( )411 local relevant = [ feature.expand <configure> ] ;413 for local f in $(relevant)430 # different set of features as relevant.431 local relevant = [ property.select [ get-relevant-features ] : $(properties) ] ;432 local ps = [ property-set.create $(relevant) ] ;449 local relevant = [ property.select [ get-relevant-features ] : $(properties) ] ;[all …]
225 # Returns additional properties that are relevant for this target228 rule relevant ( )1024 local relevant = [ toolset.relevant [ $(a1).action-name ] ] ;1025 relevant = [ $(relevant).add [ $(target).relevant ] ] ;1026 local p1 = [ $(ps1).relevant $(relevant) ] ;1027 local p2 = [ $(ps2).relevant $(relevant) ] ;1125 # Only show features that are relevant for either target.1126 local relevant = [ $(p1).get <relevant> ] [ $(p2).get <relevant> ] ;1127 relevant = [ feature.expand-relevant $(relevant) ] ;1128 # The presence of relevant can potentially mess things up,[all …]
82 # are relevant.378 rule relevant-features ( rule-or-module )381 if ! $(.relevant-features.$(rule-or-module))417 result += [ relevant-features $(next[1]) ] ;424 .relevant-features.$(rule-or-module) = $(result) ;429 return $(.relevant-features.$(rule-or-module)) ;466 local relevant = [ relevant-features $(rule-or-module) ] ;470 if $(p:G) in $(relevant)516 # Returns a property-set indicating which features are relevant519 rule relevant ( rule-name )[all …]
59 # Registers a new generator class, specifying a set of properties relevant to63 rule register ( scanner-class : relevant-properties * )66 .relevant-properties.$(scanner-class) = $(relevant-properties) ;112 [ property.select $(.relevant-properties.$(scanner-class)) :
726 # Features are relevant here if they could affect alternative729 rule relevant-features ( )733 if $(self.relevant-features)735 return $(self.relevant-features) ;754 self.relevant-features = [ property-set.create <relevant>$(result) ] ;755 return $(self.relevant-features) ;779 local relevant = [ relevant-features ] ;784 local r = [ generate-really [ $(p).add $(relevant) ] ] ;1373 local relevant = [ propagated-relevant1374 [ $(gur).get <relevant> ][all …]
154 relevant = ps.get_properties('target-os') + \159 rps = property_set.create(relevant)
228 local relevant = [ property.select [ configure.get-relevant-features ] <link> :231 local key = ac-library-$(name)-$(relevant:J=-) ;323 : [ configure.get-relevant-features ] <link> ] ;
112 unsigned int relevant; in r300_swizzle_is_native() local133 relevant = 0; in r300_swizzle_is_native()137 relevant |= 1 << j; in r300_swizzle_is_native()139 if ((reg.Negate & relevant) && ((reg.Negate & relevant) != relevant)) in r300_swizzle_is_native()
186 unsigned int relevant; in r500_swizzle_is_native() local224 relevant = 0; in r500_swizzle_is_native()228 relevant |= 1 << i; in r500_swizzle_is_native()230 if ((reg.Negate & relevant) && ((reg.Negate & relevant) != relevant)) in r500_swizzle_is_native()
40 local relevant = [ toolset.relevant [ indirect.get-rule $(m[1]) ] ] ;41 local a = [ new action $(source-targets) : $(m[1]) : [ $(property-set).add $(relevant) ] ] ;44 return $(relevant) [ virtual-target.register $(t) ] ;
41 local a = [ new null-action [ $(property-set).add-raw <relevant>link ] ] ;50 return [ property-set.create <xdll-path>$(search) <relevant>link ]89 rule relevant ( )91 return [ property-set.create <relevant>link ] ;
29 property-set = [ $(property-set).add-raw <relevant>link ] ;50 local usage-requirements = <relevant>link ;
20 <!-- reproduce this bug. Include code to reproduce, if relevant -->40 <!-- Include as many relevant details about the environment you experienced the bug in. -->
8 - Open the relevant solution file in /msvc:43 default library paths for your project points to the relevant directories.
42 Sync methods are only relevant for `rimraf.sync()`, of course.58 Only relevant for async usage.69 Only relevant for async usage.
5 independently covers all of the relevant information currently included here.
8 echo Building relevant projects.
2 # only where it's not relevant to the parse.
131 local relevant = [ $(ps).get <relevant> ] ;132 relevant = [ feature.expand-relevant $(relevant) ] ;134 if python in $(relevant)460 local relevant = [ $(property-set).get <relevant> ] ;461 relevant = [ feature.expand-relevant $(relevant) ] ;463 if python in $(relevant)
6 particularly relevant to testing Mesa because we often need to change41 ``/etc/lava-dispatcher/device-types``). Now, go find a relevant79 relevant as we have many stable branches all using CI).
5 - add the code to the relevant directory