- Sort Score
- Result 10 results
- Languages All
Results 71 - 80 of 1,533 for varints (0.15 sec)
-
platforms/native/language-native/src/main/java/org/gradle/language/cpp/internal/MainLibraryVariant.java
@Override public Set<? extends SoftwareComponent> getVariants() { return variants; } public void addArtifact(PublishArtifact artifact) { artifacts.add(artifact); } /** * Adds a child variant */ public void addVariant(SoftwareComponent variant) { variants.add(variant); }
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Nov 16 20:20:03 UTC 2023 - 2.6K bytes - Viewed (0) -
subprojects/core-api/src/main/java/org/gradle/api/artifacts/result/ResolvedComponentResult.java
* times with different variants (for example, the main component and its test fixtures). The dependencies * of each variant are different, but the {@link #getDependencies() method} doesn't give access to each * variant individual dependencies. * * <p> * The variant must be a {@linkplain #getVariants() selected variant} of this component.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Jun 05 19:24:33 UTC 2023 - 3.8K bytes - Viewed (0) -
testing/internal-integ-testing/src/main/groovy/org/gradle/test/fixtures/maven/MavenModule.groovy
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Apr 04 07:21:38 UTC 2024 - 4.8K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/design/gradle-module-metadata-latest-specification.md
The following statements must hold for the variants: - Variant name must be unique per module - Each variant must have at least one attribute - Two variants cannot have the same attributes and capabilities - If there is at least one dependency in any variant, at least one must carry version information ### `attributes` value
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Mar 18 16:14:11 UTC 2024 - 14.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/native/cpp_application_plugin.adoc
[[sec:cpp_application_task_variants]] === Variant-dependent Tasks The {cpp} Application Plugin creates tasks based on the variants of the application component. Read the <<building_cpp_projects.adoc#sec:introducing_build_variants-cpp,introduction to build variants>> for more information. The following diagram shows the relationship between variant-dependent tasks. .{cpp} Application Plugin variant-dependent task graph
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 13.6K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/native/swift_application_plugin.adoc
[[sec:swift_application_task_variants]] === Variant-dependent Tasks The Swift Application Plugin creates tasks based on the variants of the application component. Read the <<building_swift_projects.adoc#sec:introducing_build_variants-swift,introduction to build variants>> for more information. The following diagram shows the relationship between variant-dependent tasks. .Swift Application Plugin variant-dependent task graph
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 13.2K bytes - Viewed (0) -
platforms/software/publish/src/main/java/org/gradle/api/publish/internal/metadata/ModuleMetadataJsonWriter.java
); } private void writeVariants() throws IOException { List<ModuleMetadataSpec.Variant> variants = metadata.variants; if (variants.isEmpty()) { return; } writeArray("variants", () -> { for (ModuleMetadataSpec.Variant variant : variants) { if (variant instanceof ModuleMetadataSpec.LocalVariant) {
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Oct 12 14:02:46 UTC 2023 - 11.4K bytes - Viewed (0) -
platforms/native/language-native/src/main/java/org/gradle/language/cpp/internal/MainExecutableVariant.java
private final DomainObjectSet<SoftwareComponent> variants; public MainExecutableVariant(ObjectFactory objectFactory) { variants = objectFactory.domainObjectSet(SoftwareComponent.class); } @Override public String getName() { return "main"; } @Override public Set<SoftwareComponent> getVariants() { return variants; }
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Nov 16 20:20:03 UTC 2023 - 1.7K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/native/cpp_unit_test_plugin.adoc
[[sec:cpp_unit_test_task_variants]] === Variant-dependent Tasks The {cpp} Unit Test Plugin creates tasks based on the variants of the unit test component. Read the <<building_cpp_projects.adoc#sec:introducing_build_variants-cpp,introduction to build variants>> for more information. The following diagrams show the relationship between variant-dependent tasks. .{cpp} Unit Test Plugin variant-dependent task graph
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 13.9K bytes - Viewed (0) -
platforms/software/dependency-management/src/main/java/org/gradle/api/internal/artifacts/ivyservice/resolveengine/result/ThisBuildOnlySelectedVariantSerializer.java
long instanceId = decoder.readSmallLong(); VariantGraphResolveState variant = variants.get(instanceId); if (variant == null) { throw new IllegalStateException("No variant with id " + instanceId + " found."); } return variant; }
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Nov 22 04:22:29 UTC 2023 - 6.5K bytes - Viewed (0)