mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alan Martinovic <Alan.Martinovic@zenitel.com>
Subject: Re: [ptxdist] install_copy not recognizing path to a file
Date: Tue, 23 Sep 2014 09:33:48 +0200	[thread overview]
Message-ID: <201409230933.49889.jbe@pengutronix.de> (raw)
In-Reply-To: <916A03CCEB30DF44AD98D4CFDC7448D00D59B9BE@nooslzsmx1.zenitelcss.com>

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/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-09-23  7:33 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 [this message]
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

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=201409230933.49889.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=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