NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
9a7eca9baa
kumquat-buildroot/package/prosody/prosody.mk

73 lines
1.8 KiB
Makefile
Raw Normal View History

package/prosody: new package As stated by the upstream developers, Prosody only supports lua-5.1 or luajit (which is a lua-5.1 interpreter): > Response from zash at zash.se: > >> I pegged the package to lua 5,1 based on the contents of the >> INSTALL file. Is this a hard requirement? > > Up until Prosody 0.9 Lua 5.1 is required. However LuaJIT > implements Lua 5.1 so it works. The license terms are not very consistent: the source files all state to be "MIT/X11 licensed" and defer to the COPYING file for details, but that file only has the text for the MIT license. Thus, we believe the license to be MIT/X11, as stated in the source files. This installs the base system with certificates for two domains: localhost and example.com The default runtime configuration is tweaked during installation to properly setup logging and pid-file directories. Prosody doesn't like being executed as root, and thus the daemon is executed as the user prosody. The startup script creates the pid file write location with appropriate permissions. Signed-off-by: Dushara Jayasinghe <nidujay@gmail.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-10-01 00:13:03 +02:00
################################################################################
#
# prosody
#
################################################################################
PROSODY_VERSION = 0.9.12
PROSODY_SITE = https://prosody.im/downloads/source
PROSODY_LICENSE = MIT
PROSODY_LICENSE_FILES = COPYING
PROSODY_DEPENDENCIES = openssl libidn
ifeq ($(BR2_PACKAGE_LUA_5_1),y)
PROSODY_DEPENDENCIES += lua
endif
ifeq ($(BR2_PACKAGE_LUAJIT),y)
PROSODY_DEPENDENCIES += luajit
endif
prosody: refactor with PROSODY_CONF_OPTS variable Signed-off-by: Francois Perrad <francois.perrad@gadz.org> [Thomas: keep TARGET_CONFIGURE_OPTS in the environment.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-10-18 18:46:48 +02:00
PROSODY_CONF_OPTS = \
--with-lua=$(STAGING_DIR)/usr \
--c-compiler=$(TARGET_CC) \
prosody: build with -fPIC The prosody configure script defines CFLAGS as -fPIC -Wall, but because we pass our own CFLAGS, the -fPIC goes away, causing a build failure when building shared libraries on x86-64: /home/test/autobuild/run/instance-0/output/host/opt/ext-toolchain/bin/../lib/gcc/x86_64-amd-linux-gnu/6.2.0/../../../../x86_64-amd-linux-gnu/bin/ld: encodings.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC So let's pass this -fPIC flag explicitly in CFLAGS. We don't bother passing it conditionally !BR2_STATIC_LIBS because other packages (e.g lua) also pass -fPIC unconditionally. Fixes: http://autobuild.buildroot.net/results/7f0eb285b75cdeacb21a1f9a9f64d2f0cbbf1d59/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-11-06 21:04:14 +01:00
--cflags="$(TARGET_CFLAGS) -fPIC" \
prosody: refactor with PROSODY_CONF_OPTS variable Signed-off-by: Francois Perrad <francois.perrad@gadz.org> [Thomas: keep TARGET_CONFIGURE_OPTS in the environment.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-10-18 18:46:48 +02:00
--linker=$(TARGET_CC) \
--ldflags="$(TARGET_LDFLAGS) -shared" \
--sysconfdir=/etc/prosody \
--prefix=/usr
package/prosody: new package As stated by the upstream developers, Prosody only supports lua-5.1 or luajit (which is a lua-5.1 interpreter): > Response from zash at zash.se: > >> I pegged the package to lua 5,1 based on the contents of the >> INSTALL file. Is this a hard requirement? > > Up until Prosody 0.9 Lua 5.1 is required. However LuaJIT > implements Lua 5.1 so it works. The license terms are not very consistent: the source files all state to be "MIT/X11 licensed" and defer to the COPYING file for details, but that file only has the text for the MIT license. Thus, we believe the license to be MIT/X11, as stated in the source files. This installs the base system with certificates for two domains: localhost and example.com The default runtime configuration is tweaked during installation to properly setup logging and pid-file directories. Prosody doesn't like being executed as root, and thus the daemon is executed as the user prosody. The startup script creates the pid file write location with appropriate permissions. Signed-off-by: Dushara Jayasinghe <nidujay@gmail.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-10-01 00:13:03 +02:00
define PROSODY_CONFIGURE_CMDS
cd $(@D) && \
$(TARGET_CONFIGURE_OPTS) \
prosody: refactor with PROSODY_CONF_OPTS variable Signed-off-by: Francois Perrad <francois.perrad@gadz.org> [Thomas: keep TARGET_CONFIGURE_OPTS in the environment.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-10-18 18:46:48 +02:00
./configure $(PROSODY_CONF_OPTS)
package/prosody: new package As stated by the upstream developers, Prosody only supports lua-5.1 or luajit (which is a lua-5.1 interpreter): > Response from zash at zash.se: > >> I pegged the package to lua 5,1 based on the contents of the >> INSTALL file. Is this a hard requirement? > > Up until Prosody 0.9 Lua 5.1 is required. However LuaJIT > implements Lua 5.1 so it works. The license terms are not very consistent: the source files all state to be "MIT/X11 licensed" and defer to the COPYING file for details, but that file only has the text for the MIT license. Thus, we believe the license to be MIT/X11, as stated in the source files. This installs the base system with certificates for two domains: localhost and example.com The default runtime configuration is tweaked during installation to properly setup logging and pid-file directories. Prosody doesn't like being executed as root, and thus the daemon is executed as the user prosody. The startup script creates the pid file write location with appropriate permissions. Signed-off-by: Dushara Jayasinghe <nidujay@gmail.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-10-01 00:13:03 +02:00
endef
define PROSODY_BUILD_CMDS
$(TARGET_MAKE_ENV) $(MAKE) -C $(@D)
endef
define PROSODY_INSTALL_TARGET_CMDS
$(TARGET_MAKE_ENV) $(MAKE) DESTDIR="$(TARGET_DIR)" -C $(@D) install
endef
define PROSODY_INSTALL_INIT_SYSV
$(INSTALL) -D -m 0755 package/prosody/S50prosody \
$(TARGET_DIR)/etc/init.d/S50prosody
endef
define PROSODY_USERS
prosody -1 prosody -1 * - - - Prosody user
endef
# make install installs a Makefile and meta data to generate certs
define PROSODY_REMOVE_CERT_GENERATOR
rm -f $(TARGET_DIR)/etc/prosody/certs/Makefile
rm -f $(TARGET_DIR)/etc/prosody/certs/*.cnf
endef
PROSODY_POST_INSTALL_TARGET_HOOKS += PROSODY_REMOVE_CERT_GENERATOR
# 1. Enable posix functionality
# 2. Log to syslog
# 3. Specify pid file write location
# 4. Enable virtual host example.com
define PROSODY_TWEAK_DEFAULT_CONF
$(INSTALL) -D package/prosody/prosody.cfg.lua \
$(TARGET_DIR)/etc/prosody/prosody.cfg.lua
endef
PROSODY_POST_INSTALL_TARGET_HOOKS += PROSODY_TWEAK_DEFAULT_CONF
$(eval $(generic-package))
Reference in New Issue Copy Permalink