From: Alan Martinovic <Alan.Martinovic@zenitel.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] install_copy not recognizing path to a file
Date: Fri, 3 Oct 2014 13:38:57 +0000 [thread overview]
Message-ID: <916A03CCEB30DF44AD98D4CFDC7448D01D52E4AB@nooslzsmx1.zenitelcss.com> (raw)
In-Reply-To: <916A03CCEB30DF44AD98D4CFDC7448D00D59B9BE@nooslzsmx1.zenitelcss.com>
[-- Attachment #1.1: Type: text/plain, Size: 2506 bytes --]
A note on the problem.
Striping and removing quotes from env variables from Kconfig also solved the problem.
For quotes:
$(subst $\",,$(PTXCONF_YOUR_VARIABLE))
For whitespaces
$(strip $(PTXDIST_ YOUR_VARIABLE))
From: ptxdist-bounces@pengutronix.de [mailto:ptxdist-bounces@pengutronix.de] On Behalf Of Alan Martinovic
Sent: Tuesday, September 23, 2014 9:12 AM
To: ptxdist@pengutronix.de
Subject: [ptxdist] install_copy not recognizing path to a file
Hi,
I'm adding a custom application into the build system and I'm having undefined issues with install_copy.
I have defined the rule as follows:
*$(MYLIB_SOURCE_LOCAL) is the path where the binaries are located. (oselas.project/build/mylib -1234)
$(STATEDIR)/mylib.targetinstall:
@$(call targetinfo)
@$(call install_init, mylib)
@$(call install_fixup, mylib,PRIORITY,optional)
@$(call install_fixup, mylib,SECTION,base)
@$(call install_fixup, mylib,AUTHOR,"<>")
@$(call install_fixup, mylib,DESCRIPTION,missing)
@$(call install_copy, mylib, 0, 0, 0755, $(MYLIB_SOURCE_LOCAL)/mylib.a, /usr/lib/mylib.a)
@$(call install_copy, mylib, 0, 0, 0755, $(MYLIB_SOURCE_LOCAL)/include/mylib.h, /usr/include/mylib.h)
@$(call install_finish, mylib)
@$(call touch)
When I run targetinstall I get the following error:
install file:
src=oselas.project/build/mylib -1234
dst=/usr/lib/libzxmlconfig.a
owner=0
group=0
permissions=0755
install: omitting directory '/home/user/Workspace/oselas.project/build/mylib -1234
For some reason it doesn't append the /mylib.a to the path. Any ideas on this?
BR
Alan
DISCLAIMER:
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.
DISCLAIMER:
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.
[-- Attachment #1.2: Type: text/html, Size: 8213 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-10-03 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 7:11 Alan Martinovic
2014-09-23 7:33 ` Juergen Borleis
2014-09-23 8:20 ` Alan Martinovic
2014-09-23 8:54 ` Alan Martinovic
2014-09-23 9:57 ` Juergen Borleis
2014-09-23 10:04 ` Juergen Borleis
2014-09-23 12:34 ` Alan Martinovic
2014-10-03 13:38 ` Alan Martinovic [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=916A03CCEB30DF44AD98D4CFDC7448D01D52E4AB@nooslzsmx1.zenitelcss.com \
--to=alan.martinovic@zenitel.com \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox