- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 35 for make (0.04 sec)
-
build/root/Makefile
# WHAT: List of checks to run # # Example: # make verify # make verify BRANCH=branch_x # make verify WHAT="gofmt typecheck" endef .PHONY: verify ifeq ($(PRINT_HELP),y) verify: echo "$$VERIFY_HELP_INFO" else ifeq ($(origin KUBE_VERIFY_GIT_BRANCH), undefined) verify: KUBE_VERIFY_GIT_BRANCH=$(BRANCH) hack/make-rules/verify.sh else verify: hack/make-rules/verify.sh endif
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Sat Jun 01 16:43:08 UTC 2024 - 15.8K bytes - Viewed (0) -
common/config/.golangci.yml
# # The original version of this file is located in the https://github.com/istio/common-files repo. # If you're looking at this file in a different repo and want to make a change, please go to the # common-files repo, make the change there and check it in. Then come back to this repo and run # "make update-common". run: # Timeout for analysis, e.g. 30s, 5m. # Default: 1m timeout: 20m build-tags: - integ - integfuzz linters:
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Jun 04 20:03:06 UTC 2024 - 11.3K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/best-practices/organizing_gradle_projects.adoc
Gradle recommends that you place sources in directories according to their language, because builds are more performant and both the user and build can make stronger assumptions. The following source tree contains Java and Kotlin source files. Java source files live in `src/main/java`, whereas Kotlin source files live in `src/main/kotlin`. ==== [.multi-language-sample] =====
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Apr 23 08:16:36 UTC 2024 - 13.1K bytes - Viewed (0) -
manifests/charts/istiod-remote/values.yaml
remotePilotAddress: "" ############################################################################################## # The following values are found in other charts. To effectively modify these values, make # # make sure they are consistent across your Istio helm charts # ##############################################################################################
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon Jun 03 01:55:05 UTC 2024 - 21K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/migrating/migrating_from_groovy_to_kotlin_dsl.adoc
A complex and highly dynamic build may require some restructuring anyway, so in such cases reimplementing build logic to follow Gradle best practice makes sense. Since applying Gradle best practices will make your builds easier to use and faster, we recommend that you migrate all projects in that way eventually, but it makes sense to focus on the projects that have to be restructured first and those that would benefit most from the improvements.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Apr 01 15:00:23 UTC 2024 - 26.9K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/jvm/building_java_projects.adoc
* Separate API and implementation JARs — it may make sense to have these as separate projects, particularly if you already have a multi-project build * Generated sources — if the resulting sources should be compiled with the production code, add their path(s) to the `main` source set and make sure that the `compileJava` task depends on the task that generates the sources
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Apr 01 15:00:23 UTC 2024 - 44.1K bytes - Viewed (0) -
cluster/images/etcd/Makefile
push: build # split words on hyphen, access by 1-index word-hyphen = $(word $2,$(subst -, ,$1)) sub-build-%: $(MAKE) OUTPUT_TYPE=docker OS=$(call word-hyphen,$*,1) ARCH=$(call word-hyphen,$*,2) build all-build: $(addprefix sub-build-,$(ALL_OS_ARCH)) sub-push-image-%: $(MAKE) OUTPUT_TYPE=registry OS=$(call word-hyphen,$*,1) ARCH=$(call word-hyphen,$*,2) OSVERSION=$(call word-hyphen,$*,3) REGISTRY=$(PUSH_REGISTRY) push
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Thu Jun 06 16:13:15 UTC 2024 - 11.1K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/values.yaml
remotePilotAddress: "" ############################################################################################## # The following values are found in other charts. To effectively modify these values, make # # make sure they are consistent across your Istio helm charts # ##############################################################################################
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon Jun 03 01:55:05 UTC 2024 - 21.1K bytes - Viewed (0) -
src/runtime/race_arm64.s
MOVD runtime·tls_g(SB), R11 \ MOVD (R0)(R11), g // func runtime·raceread(addr uintptr) // Called from instrumented code. // Defined as ABIInternal so as to avoid introducing a wrapper, // which would make caller's PC ineffective. TEXT runtime·raceread<ABIInternal>(SB), NOSPLIT, $0-8 MOVD R0, R1 // addr MOVD LR, R2 // void __tsan_read(ThreadState *thr, void *addr, void *pc); MOVD $__tsan_read(SB), R9
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Fri May 17 18:37:29 UTC 2024 - 15.5K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/optimizing-performance/build-cache/build_cache.adoc
Some tasks, like link:{groovyDslPath}/org.gradle.api.tasks.Copy.html[Copy] or link:{groovyDslPath}/org.gradle.api.tasks.bundling.Jar.html[Jar], usually do not make sense to make cacheable because Gradle is only copying files from one location to another. It also doesn't make sense to make tasks cacheable that do not produce outputs or have no task actions. [[sec:task_output_caching_cacheable_3rd_party]] === Third party plugins
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed May 15 11:30:10 UTC 2024 - 26.1K bytes - Viewed (0)