kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/sysutils/cloudabi-utils/Makefile

49 lines
1.1 KiB
Makefile
Raw Normal View History

Add sysutils/cloudabi-utils. Summary: Though CloudABI programs can simply be started from the command line like any UNIX process, the preferred way for starting them is using the cloudabi-run utility. cloudabi-run parses a YAML file that contains the configuration for the program that you want to run. Special tags can be used in the YAML file to indicate that the program depends on a resources (a socket or a file). cloudabi-run then attempts to obtain these resources and startes the program for you. The end result is that it's possible to build software that looks like traditional UNIX software (executable + config file), but still gets run in this completely sandboxed environment. Reviewers: bapt Reviewed By: bapt Differential Revision: https://reviews.freebsd.org/D3067
2015-07-13 14:26:40 +02:00
# Created by: Ed Schouten <ed@FreeBSD.org>
# $FreeBSD$
PORTNAME= cloudabi-utils
Upgrade the CloudABI toolchain and utilities. A new version of cloudlibc and cloudabi-utils has been released, to catch up with ABI changes (due to the import into FreeBSD HEAD). Bump these ports up to v0.4. While there, upgrade the LLVM packages. It looks like the LLVM project is finally releasing tarballs itself, meaning we can use those instead of requiring me to host them myself. Update the ports to use a common Makefile (cloudabi-libc++/Makefile.common) to set the PORTVERSION, MASTER_SITES, etc. Reviewed by: bapt Differential Revision: https://reviews.freebsd.org/D3332
2015-08-09 13:42:05 +02:00
PORTVERSION= 0.4
Add sysutils/cloudabi-utils. Summary: Though CloudABI programs can simply be started from the command line like any UNIX process, the preferred way for starting them is using the cloudabi-run utility. cloudabi-run parses a YAML file that contains the configuration for the program that you want to run. Special tags can be used in the YAML file to indicate that the program depends on a resources (a socket or a file). cloudabi-run then attempts to obtain these resources and startes the program for you. The end result is that it's possible to build software that looks like traditional UNIX software (executable + config file), but still gets run in this completely sandboxed environment. Reviewers: bapt Reviewed By: bapt Differential Revision: https://reviews.freebsd.org/D3067
2015-07-13 14:26:40 +02:00
CATEGORIES= sysutils
MASTER_SITES= https://nuxi.nl/distfiles/cloudabi-utils/
MAINTAINER= ed@FreeBSD.org
COMMENT= Utilities for running CloudABI programs
LICENSE= BSD2CLAUSE
BUILD_DEPENDS= cloudabi-toolchain>=0:${PORTSDIR}/devel/cloudabi-toolchain
LIB_DEPENDS= libyaml.so:${PORTSDIR}/textproc/libyaml
ONLY_FOR_ARCHS= amd64
ONLY_FOR_ARCHS_REASON= CloudABI has not yet been ported to other architectures
Add compiler:c11. cloudabi-run depends on a couple of C11 tricks (e.g., _Generic). Make sure we have the right compiler for that. Discussed with: bapt
2015-07-13 14:41:44 +02:00
USES= compiler:c11 tar:xz
Add sysutils/cloudabi-utils. Summary: Though CloudABI programs can simply be started from the command line like any UNIX process, the preferred way for starting them is using the cloudabi-run utility. cloudabi-run parses a YAML file that contains the configuration for the program that you want to run. Special tags can be used in the YAML file to indicate that the program depends on a resources (a socket or a file). cloudabi-run then attempts to obtain these resources and startes the program for you. The end result is that it's possible to build software that looks like traditional UNIX software (executable + config file), but still gets run in this completely sandboxed environment. Reviewers: bapt Reviewed By: bapt Differential Revision: https://reviews.freebsd.org/D3067
2015-07-13 14:26:40 +02:00
PLIST_FILES= bin/cloudabi-run \
libexec/cloudabi-reexec \
man/man1/cloudabi-run.1.gz
Make this port build properly. Summary: It looks like we forgot to add '${SETENV} ${MAKE_ENV}' to the build script. Right now it ignores the compiler entirely. Furthermore, regardless of whether a C11 compiler is being used, the build will fail, for the reason that some C11 headers such as <stdnoreturn.h> are being used in the code. Instead of trying to fix that, simply disable this port on FreeBSD <10.1. I have no intent on ever getting CloudABI to work on FreeBSD 9. Reviewers: bapt Reviewed By: bapt Differential Revision: https://reviews.freebsd.org/D3077
2015-07-21 11:00:00 +02:00
CFLAGS+= -I${LOCALBASE}/include
LDFLAGS+= -L${LOCALBASE}/lib
Add sysutils/cloudabi-utils. Summary: Though CloudABI programs can simply be started from the command line like any UNIX process, the preferred way for starting them is using the cloudabi-run utility. cloudabi-run parses a YAML file that contains the configuration for the program that you want to run. Special tags can be used in the YAML file to indicate that the program depends on a resources (a socket or a file). cloudabi-run then attempts to obtain these resources and startes the program for you. The end result is that it's possible to build software that looks like traditional UNIX software (executable + config file), but still gets run in this completely sandboxed environment. Reviewers: bapt Reviewed By: bapt Differential Revision: https://reviews.freebsd.org/D3067
2015-07-13 14:26:40 +02:00
do-build:
@cd ${WRKSRC} && \
Make this port build properly. Summary: It looks like we forgot to add '${SETENV} ${MAKE_ENV}' to the build script. Right now it ignores the compiler entirely. Furthermore, regardless of whether a C11 compiler is being used, the build will fail, for the reason that some C11 headers such as <stdnoreturn.h> are being used in the code. Instead of trying to fix that, simply disable this port on FreeBSD <10.1. I have no intent on ever getting CloudABI to work on FreeBSD 9. Reviewers: bapt Reviewed By: bapt Differential Revision: https://reviews.freebsd.org/D3077
2015-07-21 11:00:00 +02:00
${SETENV} ${MAKE_ENV} \
Upgrade the CloudABI toolchain to a newer version. Due to the CloudABI code being reviewed before hitting the tree, some minor ABI tweaks are made in a couple of places, while we still can. Unfortunately, this means that the previous version of cloudlibc now generates binaries that are not compatible with the latest kernel sources. Roll a new release that makes the toolchain compatible with what's in FreeBSD HEAD.
2015-07-22 14:54:48 +02:00
PREFIX=${PREFIX} \
Add sysutils/cloudabi-utils. Summary: Though CloudABI programs can simply be started from the command line like any UNIX process, the preferred way for starting them is using the cloudabi-run utility. cloudabi-run parses a YAML file that contains the configuration for the program that you want to run. Special tags can be used in the YAML file to indicate that the program depends on a resources (a socket or a file). cloudabi-run then attempts to obtain these resources and startes the program for you. The end result is that it's possible to build software that looks like traditional UNIX software (executable + config file), but still gets run in this completely sandboxed environment. Reviewers: bapt Reviewed By: bapt Differential Revision: https://reviews.freebsd.org/D3067
2015-07-13 14:26:40 +02:00
CLOUDABI_CC=${LOCALBASE}/bin/x86_64-unknown-cloudabi-cc \
${SH} build
do-install:
@cd ${WRKSRC} && \
Upgrade the CloudABI toolchain to a newer version. Due to the CloudABI code being reviewed before hitting the tree, some minor ABI tweaks are made in a couple of places, while we still can. Unfortunately, this means that the previous version of cloudlibc now generates binaries that are not compatible with the latest kernel sources. Roll a new release that makes the toolchain compatible with what's in FreeBSD HEAD.
2015-07-22 14:54:48 +02:00
DESTDIR=${STAGEDIR} \
PREFIX=${PREFIX} \
Add sysutils/cloudabi-utils. Summary: Though CloudABI programs can simply be started from the command line like any UNIX process, the preferred way for starting them is using the cloudabi-run utility. cloudabi-run parses a YAML file that contains the configuration for the program that you want to run. Special tags can be used in the YAML file to indicate that the program depends on a resources (a socket or a file). cloudabi-run then attempts to obtain these resources and startes the program for you. The end result is that it's possible to build software that looks like traditional UNIX software (executable + config file), but still gets run in this completely sandboxed environment. Reviewers: bapt Reviewed By: bapt Differential Revision: https://reviews.freebsd.org/D3067
2015-07-13 14:26:40 +02:00
${SH} install
Make this port build properly. Summary: It looks like we forgot to add '${SETENV} ${MAKE_ENV}' to the build script. Right now it ignores the compiler entirely. Furthermore, regardless of whether a C11 compiler is being used, the build will fail, for the reason that some C11 headers such as <stdnoreturn.h> are being used in the code. Instead of trying to fix that, simply disable this port on FreeBSD <10.1. I have no intent on ever getting CloudABI to work on FreeBSD 9. Reviewers: bapt Reviewed By: bapt Differential Revision: https://reviews.freebsd.org/D3077
2015-07-21 11:00:00 +02:00
.include <bsd.port.pre.mk>
.if ${OSVERSION} < 1000100
IGNORE= CloudABI will never support this version of FreeBSD
.endif
.include <bsd.port.post.mk>
Reference in a new issue Copy permalink