b95f7591bd
BR2_PACKAGE_LIBCURL_OPENSSL is part of a "choice" option so it cannot be selected. What seems to be really be needed is HTTPS support in curl, so use the blind LIBCURL_FORCE_TLS option instead (openssl is already selected). Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
32 lines
1.3 KiB
Plaintext
32 lines
1.3 KiB
Plaintext
config BR2_PACKAGE_GITLAB_RUNNER
|
|
bool "gitlab-runner"
|
|
depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
|
|
depends on BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
|
|
depends on BR2_TOOLCHAIN_HAS_THREADS
|
|
depends on BR2_USE_MMU # git
|
|
depends on BR2_USE_WCHAR # tar
|
|
select BR2_PACKAGE_BASH # runtime, shells/bash.go probably want to support bashism.
|
|
select BR2_PACKAGE_BUSYBOX_SHOW_OTHERS # bash
|
|
select BR2_PACKAGE_CA_CERTIFICATES # runtime
|
|
select BR2_PACKAGE_GIT # runtime
|
|
select BR2_PACKAGE_LIBCURL # runtime
|
|
select BR2_PACKAGE_LIBCURL_CURL # runtime
|
|
select BR2_PACKAGE_LIBCURL_FORCE_TLS # runtime
|
|
select BR2_PACKAGE_OPENSSL # runtime
|
|
select BR2_PACKAGE_OPENSSL_FORCE_LIBOPENSSL # runtime
|
|
select BR2_PACKAGE_LIBOPENSSL_BIN # runtime
|
|
select BR2_PACKAGE_TAR # runtime
|
|
help
|
|
GitLab Runner is the open source project that is used to run
|
|
your jobs and send the results back to GitLab. It is used in
|
|
conjunction with GitLab CI/CD, the open-source continuous
|
|
integration service included with GitLab that coordinates the
|
|
jobs.
|
|
|
|
https://docs.gitlab.com/runner/
|
|
|
|
comment "gitlab-runner needs a toolchain w/ threads"
|
|
depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
|
|
depends on BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
|
|
depends on !BR2_TOOLCHAIN_HAS_THREADS
|