All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 07/24] luarocks: allow to work with host-luajit
Date: Thu, 27 Feb 2014 08:02:26 +0100	[thread overview]
Message-ID: <530EE302.70507@mind.be> (raw)
In-Reply-To: <1393227301-14874-8-git-send-email-francois.perrad@gadz.org>

On 02/24/14 08:34, Francois Perrad wrote:
> when we use luajit on target

 Can you explain more clearly why this is needed? I.e., why can't you use
host-lua for luarocks to build packages for luajit on the target? You'll
need at least two paragraphs to explain that properly. I can write the
explanation if you like, only I don't understand myself why it is needed :-)

> 
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
>  package/luainterpreter/luainterpreter.mk |    4 ++++
>  package/luarocks/luarocks.mk             |   18 ++++++++++++------
>  2 files changed, 16 insertions(+), 6 deletions(-)
> 
> diff --git a/package/luainterpreter/luainterpreter.mk b/package/luainterpreter/luainterpreter.mk
> index c37d621..d5b95db 100644
> --- a/package/luainterpreter/luainterpreter.mk
> +++ b/package/luainterpreter/luainterpreter.mk
> @@ -5,8 +5,12 @@
>  #############################################################
>  
>  LUAINTERPRETER_SOURCE =
> +HOST_LUAINTERPRETER_SOURCE =
>  LUAINTERPRETER_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_LUA_INTERPRETER))
>  
>  LUAINTERPRETER_ABIVER = $(call qstrip,$(BR2_PACKAGE_LUAINTERPRETER_ABI_VERSION))
>  
>  $(eval $(generic-package))
> +$(eval $(host-generic-package))

 This should be a separate patch - with explanation in the commit log! E.g.

luainterpreter: add host-luainterpreter

host-luainterpreter is needed for luarocks to work with the same lua
implementation as the one on the target.

> +
> +LUA_RUN = $(HOST_DIR)/usr/bin/$(call qstrip,$(BR2_PACKAGE_PROVIDES_LUA_INTERPRETER))

 Wouldn't it be easier to just symlink lua -> luajit in luajit?

 Actually, in the luajit Makefile I see:

$(SYMLINK) $(INSTALL_TNAME) $(INSTALL_TSYM)

which smells to me as if it is already symlinking...

> diff --git a/package/luarocks/luarocks.mk b/package/luarocks/luarocks.mk
> index 86e57d2..0b99de6 100644
> --- a/package/luarocks/luarocks.mk
> +++ b/package/luarocks/luarocks.mk
> @@ -9,16 +9,22 @@ LUAROCKS_SITE = http://luarocks.org/releases/
>  LUAROCKS_LICENSE = MIT
>  LUAROCKS_LICENSE_FILES = COPYING
>  
> -HOST_LUAROCKS_DEPENDENCIES = host-lua luainterpreter
> +HOST_LUAROCKS_DEPENDENCIES = host-luainterpreter luainterpreter
>  
>  LUAROCKS_CONFIG_DIR  = $(HOST_DIR)/usr/etc/luarocks
>  LUAROCKS_CONFIG_FILE = $(LUAROCKS_CONFIG_DIR)/config-$(LUAINTERPRETER_ABIVER).lua
>  
> +HOST_LUAROCKS_CONF_OPT = \
> +	--prefix=$(HOST_DIR)/usr \
> +	--sysconfdir=$(LUAROCKS_CONFIG_DIR) \
> +	--with-lua=$(HOST_DIR)/usr
> +
> +ifeq ($(BR2_PACKAGE_LUAJIT),y)
> +HOST_LUAROCKS_CONF_OPT += --lua-suffix=jit
> +endif
> +
>  define HOST_LUAROCKS_CONFIGURE_CMDS
> -	cd $(@D) && ./configure \
> -		--prefix=$(HOST_DIR)/usr \
> -		--sysconfdir=$(LUAROCKS_CONFIG_DIR) \
> -		--with-lua=$(HOST_DIR)/usr
> +	cd $(@D) && ./configure $(HOST_LUAROCKS_CONF_OPT)
>  endef
>  
>  define HOST_LUAROCKS_INSTALL_CMDS
> @@ -43,4 +49,4 @@ endef
>  $(eval $(host-generic-package))
>  
>  LUAROCKS_RUN = LUA_PATH="$(HOST_DIR)/usr/share/lua/$(LUAINTERPRETER_ABIVER)/?.lua" \
> -	$(HOST_DIR)/usr/bin/lua $(HOST_DIR)/usr/bin/luarocks
> +	$(LUA_RUN) $(HOST_DIR)/usr/bin/luarocks

 This should be mentioned and explained explicitly in the commit message.
E.g.:

Since the host-lua executable can be either lua or luajit, use $(LUA_RUN)
to call it instead of an explicit path.

 Unless of course the symlink is installed :-)

 Regards,
 Arnout

> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-02-27  7:02 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24  7:34 [Buildroot] [PATCH 00/24] lua Francois Perrad
2014-02-24  7:34 ` [Buildroot] [PATCH 01/24] lua: remove LUA_INSTALLED_FILES Francois Perrad
2014-02-24 19:44   ` Arnout Vandecappelle
2014-02-24  7:34 ` [Buildroot] [PATCH 02/24] lua: refactor install steps Francois Perrad
2014-02-25 17:39   ` Arnout Vandecappelle
2014-02-25 20:30     ` Arnout Vandecappelle
2014-02-25 21:07     ` François Perrad
2014-02-25 21:38       ` Arnout Vandecappelle
2014-02-24  7:34 ` [Buildroot] [PATCH 03/24] luarocks: never wraps script Francois Perrad
2014-02-24  7:34 ` [Buildroot] [PATCH 04/24] luajit: refactor without dont-strip.patch Francois Perrad
2014-02-27  6:39   ` Arnout Vandecappelle
2014-02-24  7:34 ` [Buildroot] [PATCH 05/24] luajit: refactor without shared-lib.patch Francois Perrad
2014-02-27  6:40   ` Arnout Vandecappelle
2014-02-27  9:05   ` Samuel Martin
2014-02-28  8:22     ` François Perrad
2014-02-24  7:34 ` [Buildroot] [PATCH 06/24] luajit: add host-luajit Francois Perrad
2014-02-27  6:44   ` Arnout Vandecappelle
2014-02-24  7:34 ` [Buildroot] [PATCH 07/24] luarocks: allow to work with host-luajit Francois Perrad
2014-02-27  7:02   ` Arnout Vandecappelle [this message]
2014-02-24  7:34 ` [Buildroot] [PATCH 08/24] ljlinenoise: new package Francois Perrad
2014-02-27  7:04   ` Arnout Vandecappelle
2014-02-24  7:34 ` [Buildroot] [PATCH 09/24] lpeg: " Francois Perrad
2014-02-27  7:08   ` Arnout Vandecappelle
2014-03-01 14:40   ` Thomas Petazzoni
2014-02-24  7:34 ` [Buildroot] [PATCH 10/24] cosmo: " Francois Perrad
2014-02-27  7:08   ` Arnout Vandecappelle
2014-03-01 14:42   ` Thomas Petazzoni
2014-02-24  7:34 ` [Buildroot] [PATCH 11/24] lua-iconv: " Francois Perrad
2014-02-27  7:16   ` Arnout Vandecappelle
2014-03-01 15:58     ` François Perrad
2014-02-24  7:34 ` [Buildroot] [PATCH 12/24] luajson: " Francois Perrad
2014-02-27  7:18   ` Arnout Vandecappelle
2014-03-01 15:06   ` Thomas Petazzoni
2014-02-24  7:34 ` [Buildroot] [PATCH 13/24] lualogging: " Francois Perrad
2014-03-01 15:10   ` Thomas Petazzoni
2014-02-24  7:34 ` [Buildroot] [PATCH 14/24] dado: " Francois Perrad
2014-03-01 15:12   ` Thomas Petazzoni
2014-02-24  7:34 ` [Buildroot] [PATCH 15/24] lrandom: " Francois Perrad
2014-03-01 15:15   ` Thomas Petazzoni
2014-02-24  7:34 ` [Buildroot] [PATCH 16/24] lua-testmore: " Francois Perrad
2014-02-24  7:34 ` [Buildroot] [PATCH 17/24] lua-coat: " Francois Perrad
2014-02-24  7:34 ` [Buildroot] [PATCH 18/24] lua-coatpersistent: " Francois Perrad
2014-02-24  7:34 ` [Buildroot] [PATCH 19/24] lua-messagepack: " Francois Perrad
2014-02-24  7:34 ` [Buildroot] [PATCH 20/24] lua-csnappy: " Francois Perrad
2014-02-24  7:34 ` [Buildroot] [PATCH 21/24] lzlib: " Francois Perrad
2014-02-24  7:34 ` [Buildroot] [PATCH 22/24] lunit: " Francois Perrad
2014-02-24  7:34 ` [Buildroot] [PATCH 23/24] lpty: " Francois Perrad
2014-02-24  7:35 ` [Buildroot] [PATCH 24/24] lsqlite3: " Francois Perrad
2014-03-01 15:09 ` [Buildroot] [PATCH 00/24] lua Thomas Petazzoni
2014-03-01 15:34   ` François Perrad
2014-03-01 15:42     ` Thomas Petazzoni
2014-03-02  7:57       ` François Perrad
2014-03-02  8:39         ` Thomas Petazzoni
2014-03-01 16:12 ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=530EE302.70507@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.