From: Alan Martinovic <Alan.Martinovic@zenitel.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>,
Juergen Borleis <jbe@pengutronix.de>
Subject: Re: [ptxdist] install_copy not recognizing path to a file
Date: Tue, 23 Sep 2014 08:54:58 +0000 [thread overview]
Message-ID: <916A03CCEB30DF44AD98D4CFDC7448D00D59BA23@nooslzsmx1.zenitelcss.com> (raw)
In-Reply-To: <916A03CCEB30DF44AD98D4CFDC7448D00D59BA0A@nooslzsmx1.zenitelcss.com>
It seems we've traced the problem to the versioning number.
Conclusion:
We had a dummy version number 1234.
So the varable was: $(LIBZXMLCONFIG_SOURCE_LOCAL) -> /home/user/Workspace/oselas.bsp/build/libzxmlconfig-1234
in which case it didn't append the aditional path to it. $(LIBZXMLCONFIG_SOURCE_LOCAL)/libzxmlconfig.a -> /home/user/Workspace/oselas.bsp/build/libzxmlconfig-1234
Once the version was changed to a format with dots 1.0.0.0
So the varable was: $(LIBZXMLCONFIG_SOURCE_LOCAL) -> /home/user/Workspace/oselas.bsp/build/libzxmlconfig-1.0.0.0
It started to append: $(LIBZXMLCONFIG_SOURCE_LOCAL)/libzxmlconfig.a -> /home/user/Workspace/oselas.bsp/build/libzxmlconfig-1.0.0.0/libzxmlconfig.a
-----Original Message-----
From: ptxdist-bounces@pengutronix.de [mailto:ptxdist-bounces@pengutronix.de] On Behalf Of Alan Martinovic
Sent: Tuesday, September 23, 2014 10:20 AM
To: Juergen Borleis; ptxdist@pengutronix.de
Subject: Re: [ptxdist] install_copy not recognizing path to a file
I've tried to make things more readable and did a typo. There aren't any whitespaces in the original.
libzxmlconfig.make:
# ----------------------------------------------------------------------------
# Target-Install
# ----------------------------------------------------------------------------
$(STATEDIR)/libzxmlconfig.targetinstall:
@$(call targetinfo)
@$(call install_init, libzxmlconfig)
@$(call install_fixup, libzxmlconfig,PRIORITY,optional)
@$(call install_fixup, libzxmlconfig,SECTION,base)
@$(call install_fixup, libzxmlconfig,AUTHOR,"<>")
@$(call install_fixup, libzxmlconfig,DESCRIPTION,missing)
@$(call install_copy, libzxmlconfig, 0, 0, 0755, $(LIBZXMLCONFIG_SOURCE_LOCAL)/libzxmlconfig.a, $(PTXDIST_WORKSPACE)/platform-turbine/sysroot-target/usr/lib/libzxmlconfig.a)
@$(call install_copy, libzxmlconfig, 0, 0, 0755, $(LIBZXMLCONFIG_SOURCE_LOCAL)/include/SipServerConfig.h, $(PTXDIST_WORKSPACE)/platform-turbine/sysroot-target/usr/include/SipServerConfig.h)
@$(call install_copy, libzxmlconfig, 0, 0, 0755, $(LIBZXMLCONFIG_SOURCE_LOCAL)/include/ZConfig_globals.h, $(PTXDIST_WORKSPACE)/platform-turbine/sysroot-target/usr/include/ZConfig_globals.h)
@$(call install_copy, libzxmlconfig, 0, 0, 0755, $(LIBZXMLCONFIG_SOURCE_LOCAL)/include/z_xml.h, $(PTXDIST_WORKSPACE)/platform-turbine/sysroot-target/usr/include/z_xml.h)
@$(call install_finish, libzxmlconfig)
@$(call touch)
Output from running "ptxdist targetinstall libzxmlconfig":
-----------------------------------
target: libzxmlconfig.targetinstall
-----------------------------------
install_init: preparing for image creation of 'libzxmlconfig'...
install_init: @ARCH@ -> armel
install_init: @PACKAGE@ -> libzxmlconfig
install_init: @VERSION@ -> 1234
install_init: @DEPENDS@ ->
install_init: preinst not available
install_init: postinst not available
install_init: prerm not available
install_init: postrm not available
install_fixup: @PRIORITY@ -> optional ... done.
install_fixup: @SECTION@ -> base ... done.
install_fixup: @AUTHOR@ -> "<>" ... done.
install_fixup: @DESCRIPTION@ -> missing ... done.
xpkg_finish: collecting license (unknown) ... done.
xpkg_finish: creating ipkg package ...
install file:
src=oselas.bsp/build/libzxmlconfig-1234
dst=/usr/lib/libzxmlconfig.a
owner=0
group=0
permissions=0755
install: omitting directory '/home/user/Workspace/oselas.bsp/build/libzxmlconfig-1234'
Error: install_file failed!
make: *** [/home/user/Workspace/oselas.bsp/platform-turbine/state/libzxmlconfig.targetinstall] Error 1 failed
> BTW: why do you want to install a library archive? *.a archives are used at link time only and not used at runtime. Same is valid for header files. They are used at compile time only.
Thank you for pointing out the error.
It should be moved to the sysroot-target/lib (as in above sample)?
-----Original Message-----
From: Juergen Borleis [mailto:jbe@pengutronix.de]
Sent: Tuesday, September 23, 2014 9:34 AM
To: ptxdist@pengutronix.de
Cc: Alan Martinovic
Subject: Re: [ptxdist] install_copy not recognizing path to a file
Hi Alan,
On Tuesday 23 September 2014 09:11:32 Alan Martinovic wrote:
> 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)
Please don't use whitespaces in path names.
> $(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
Your output here does not match to your shown rule file content above.
> For some reason it doesn't append the /mylib.a to the path. Any ideas
> on this?
Remove the whitespace from the path name.
BTW: why do you want to install a library archive? *.a archives are used at link time only and not used at runtime. Same is valid for header files. They are used at compile time only.
Regards
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
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.
--
ptxdist mailing list
ptxdist@pengutronix.de
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.
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-09-23 8:54 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 [this message]
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
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=916A03CCEB30DF44AD98D4CFDC7448D00D59BA23@nooslzsmx1.zenitelcss.com \
--to=alan.martinovic@zenitel.com \
--cc=jbe@pengutronix.de \
--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