All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] qt5/qt5webchannel: add qwebchannel.js installation choice
Date: Wed, 23 Dec 2015 17:28:27 +0100	[thread overview]
Message-ID: <20151223172827.25bfa9c5@free-electrons.com> (raw)
In-Reply-To: <eef8db72-7643-4c20-8dd4-f24d61dbb50d@MAIL-SINTERS-01.sinters-int.fr>

Hello,

On Wed, 23 Dec 2015 16:24:20 +0000, Julien CORJON wrote:

> I should be agree with this, but in that case the javascript file should 
> be installed in a website hosting path. For my application this one is 
> in /usr/local/myApp/www for others it can be in an apache, lighttpd, 
> monkey, etc directory.
> 
> I'm not a web hosting expert, so if there is an generic path for that we 
> can remove that customisation and let the specific applications make a 
> symbolic link if they don't comply with the generic path.

Do like we do for all other Javascript packages (see jquery* packages):

define JQUERY_INSTALL_TARGET_CMDS
        $(INSTALL) -m 0644 -D $(@D)/$(JQUERY_SOURCE) \
                $(TARGET_DIR)/var/www/jquery.js
endef

define JQUERY_VALIDATION_INSTALL_TARGET_CMDS
        $(INSTALL) -m 0644 -D $(@D)/dist/jquery.validate.min.js \
                $(TARGET_DIR)/var/www/jquery.validate.js
endef

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-12-23 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 12:12 [Buildroot] [PATCH 1/1] qt5/qt5webchannel: add qwebchannel.js installation choice Julien Corjon
2015-12-23 16:02 ` Thomas Petazzoni
2015-12-23 16:24   ` Julien CORJON
2015-12-23 16:28     ` Thomas Petazzoni [this message]

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=20151223172827.25bfa9c5@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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.