Enaable to add binary in /usr/bin using .bb file


NIKHIL PATIL
 

Hi ,
    I want to add binary in /usr/bin , for these i made own .bb file (obexpushtest.bb),      When i am compiling obexpushtest package separately that time it is compiling fine  , but when i am adding obexpushtest in local.conf as a IMAGE_INSTALL , i am getting error.

## Error :-

/data/nikhil/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-intel/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:01 ago on Thu 19 Nov 2020 05:57:19 AM UTC.
No match for argument: obexpushtest
Error: Unable to find a match
    
## obexpushtest.bb file :-

    # file recipes-kernel/linux-firmware/linux-firmware_%.bbappend
SUMMARY = "tset_mount example"
SECTION = "test_mount"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

S = "${WORKDIR}"

SRC_URI += "file://obexpushd"

INSANE_SKIP_${PN} = "ldflags"
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
INHIBIT_PACKAGE_STRIP = "1"

do_install_append () {
        install -d ${D}/${bindir}
        install -m 0644 ${WORKDIR}/obexpushd ${D}/${bindir}
        cp ${WORKDIR}/obexpushd ${D}/${bindir}
}

# NOTE: Use "=+" instead of "+=". Otherwise, the file is placed into the linux-firmware package.
PACKAGES =+ "${PN}-example"
FILES_${PN}-example = "/usr/bin/obexpushd"






NIKHIL PATIL
 

Hi ,
    If anyone know , please help on these .

On Thu, Nov 19, 2020 at 1:14 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> wrote:
Hi ,
    I want to add binary in /usr/bin , for these i made own .bb file (obexpushtest.bb),      When i am compiling obexpushtest package separately that time it is compiling fine  , but when i am adding obexpushtest in local.conf as a IMAGE_INSTALL , i am getting error.

## Error :-

/data/nikhil/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-intel/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:01 ago on Thu 19 Nov 2020 05:57:19 AM UTC.
No match for argument: obexpushtest
Error: Unable to find a match
    
## obexpushtest.bb file :-

    # file recipes-kernel/linux-firmware/linux-firmware_%.bbappend
SUMMARY = "tset_mount example"
SECTION = "test_mount"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

S = "${WORKDIR}"

SRC_URI += "file://obexpushd"

INSANE_SKIP_${PN} = "ldflags"
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
INHIBIT_PACKAGE_STRIP = "1"

do_install_append () {
        install -d ${D}/${bindir}
        install -m 0644 ${WORKDIR}/obexpushd ${D}/${bindir}
        cp ${WORKDIR}/obexpushd ${D}/${bindir}
}

# NOTE: Use "=+" instead of "+=". Otherwise, the file is placed into the linux-firmware package.
PACKAGES =+ "${PN}-example"
FILES_${PN}-example = "/usr/bin/obexpushd"









 

On Thu, 19 Nov 2020 at 08:40, NIKHIL PATIL <nikhilvp29@gmail.com> wrote:

Hi ,
If anyone know , please help on these .
It looks like your original email was sent less than an hour ago, give
people some time.

I also recommend looking at the docs yourself.

Thanks,

--
Paul Barker
Konsulko Group


Quentin Schulz
 

Hi,

On Thu, Nov 19, 2020 at 01:13:43PM +0530, NIKHIL PATIL wrote:
Hi ,
I want to add binary in /usr/bin , for these i made own .bb file (
obexpushtest.bb), When i am compiling obexpushtest package separately
You're not compiling a package, you're compiling a recipe named
obexpushtest whose output is packages (one of which is named the same as
the recipe, hence the confusion).

that time it is compiling fine , but when i am adding obexpushtest in
local.conf as a IMAGE_INSTALL , i am getting error.
But here, you're adding a package into an image. Effectively, the first
and second commands you ran don't do the same thing.

## Error :-

/data/nikhil/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-intel/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:01 ago on Thu 19 Nov 2020 05:57:19 AM
UTC.
No match for argument: obexpushtest
Error: Unable to find a match

## obexpushtest.bb file :-

# file recipes-kernel/linux-firmware/linux-firmware_%.bbappend
SUMMARY = "tset_mount example"
SECTION = "test_mount"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

S = "${WORKDIR}"

SRC_URI += "file://obexpushd"

INSANE_SKIP_${PN} = "ldflags"
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
INHIBIT_PACKAGE_STRIP = "1"
You should probably inherit bin_package but override do_install
(otherwise you'll have an issue with the do_install task coming from the
bin_package bbclass trying to pack your whole ${WORKDIR} (S) which
include way too many files you're not interested in).

do_install_append () {
No need for _append since the following is the only thing your recipe
will do, so better just override do_install.

install -d ${D}/${bindir}
install -m 0644 ${WORKDIR}/obexpushd ${D}/${bindir}
cp ${WORKDIR}/obexpushd ${D}/${bindir}
}

# NOTE: Use "=+" instead of "+=". Otherwise, the file is placed into the
linux-firmware package.
PACKAGES =+ "${PN}-example"
FILES_${PN}-example = "/usr/bin/obexpushd"
Here's the issue, you put your file into the obexpushtest-example and
I'm pretty sure that your obexpushtest package is actually empty and by
default empty packages are removed, hence why the image recipe can't
include this package.

IMHO, no need for your PACKAGES and FILES variables as the default will
put your binary in the obexpushtest package, and since your recipe isn't
creating any other package (explicitly), I don't see the use for a new
package.

Quentin


NIKHIL PATIL
 

Hi ,
     Yours correct only , but the thing is we are taking binary(obexpushd) from other source and only need to copy that binary into /usr/bin of our platform(intel board).
     
     Hence how we can achieve these using .bb file ? is there any sample example .

On Thu, Nov 19, 2020 at 2:46 PM Quentin Schulz <quentin.schulz@...> wrote:
Hi,

On Thu, Nov 19, 2020 at 01:13:43PM +0530, NIKHIL PATIL wrote:
> Hi ,
>     I want to add binary in /usr/bin , for these i made own .bb file (
> obexpushtest.bb),      When i am compiling obexpushtest package separately

You're not compiling a package, you're compiling a recipe named
obexpushtest whose output is packages (one of which is named the same as
the recipe, hence the confusion).

> that time it is compiling fine  , but when i am adding obexpushtest in
> local.conf as a IMAGE_INSTALL , i am getting error.
>

But here, you're adding a package into an image. Effectively, the first
and second commands you ran don't do the same thing.

> ## Error :-
>
> /data/nikhil/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-intel/1.0-r0/oe-rootfs-repo
> Last metadata expiration check: 0:00:01 ago on Thu 19 Nov 2020 05:57:19 AM
> UTC.
> No match for argument: obexpushtest
> Error: Unable to find a match
>
> ## obexpushtest.bb file :-
>
>     # file recipes-kernel/linux-firmware/linux-firmware_%.bbappend
> SUMMARY = "tset_mount example"
> SECTION = "test_mount"
> LICENSE = "MIT"
> LIC_FILES_CHKSUM =
> "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
>
> S = "${WORKDIR}"
>
> SRC_URI += "file://obexpushd"
>
> INSANE_SKIP_${PN} = "ldflags"
> INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> INHIBIT_PACKAGE_STRIP = "1"
>

You should probably inherit bin_package but override do_install
(otherwise you'll have an issue with the do_install task coming from the
bin_package bbclass trying to pack your whole ${WORKDIR} (S) which
include way too many files you're not interested in).

> do_install_append () {

No need for _append since the following is the only thing your recipe
will do, so better just override do_install.

>         install -d ${D}/${bindir}
>         install -m 0644 ${WORKDIR}/obexpushd ${D}/${bindir}
>         cp ${WORKDIR}/obexpushd ${D}/${bindir}
> }
>
> # NOTE: Use "=+" instead of "+=". Otherwise, the file is placed into the
> linux-firmware package.
> PACKAGES =+ "${PN}-example"
> FILES_${PN}-example = "/usr/bin/obexpushd"

Here's the issue, you put your file into the obexpushtest-example and
I'm pretty sure that your obexpushtest package is actually empty and by
default empty packages are removed, hence why the image recipe can't
include this package.

IMHO, no need for your PACKAGES and FILES variables as the default will
put your binary in the obexpushtest package, and since your recipe isn't
creating any other package (explicitly), I don't see the use for a new
package.

Quentin


Quentin Schulz
 

Hi,

On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
Hi ,
Yours correct only , but the thing is we are taking* binary(obexpushd)*
from other source and only need to copy that binary into* /usr/bin* of our
platform(*intel board*).

Hence how we can achieve these using .bb file ? is there any sample
example .
I gave you what you have to do in the previous mail. Remove the last two
lines of your bb file.

If it does not work, give the full error logs and what you're trying to
achieve and what you have.

Quentin


NIKHIL PATIL
 

Hi ,
   Thank You very much , we are able to copy obexpushd to /usr/bin using .bb file.  

  I have one more dout ;
1)  We created our own custom image (bitbake core-image-xxxx) , after flashing image to board . when we run obexpushd binary  it shows as follows :-
    
root@intel-corei7-64:~#
root@intel-corei7-64:~# obexpushd
-sh: /usr/bin/obexpushd: No such file or directory
root@intel-corei7-64:~# cd /usr/bin          
root@intel-corei7-64:/usr/bin# ls | grep obexpush
obexpushd
root@intel-corei7-64:/usr/bin#

Even though binary is there it shows no such file or directory.

2) But when we are flashing a sato image (bitbake core-image-sato-sdk ) , that time obexpushd binary is working fine .
    
    Why it is happening like these ?
    Is there any permission related issue with custom image and sato image ?
 

On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <quentin.schulz@...> wrote:
Hi,

On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
> Hi ,
>      Yours correct only , but the thing is we are taking* binary(obexpushd)*
> from other source and only need to copy that binary into* /usr/bin* of our
> platform(*intel board*).
>
>      Hence how we can achieve these using .bb file ? is there any sample
> example .
>

I gave you what you have to do in the previous mail. Remove the last two
lines of your bb file.

If it does not work, give the full error logs and what you're trying to
achieve and what you have.

Quentin


NIKHIL PATIL
 

Hi , 
  for these issue we got solution ,
   obexpushd binary interpreter is on /lib64  folder ,   but in our custom image /lib64 support is not there .
   so we are trying to add lib64 support for our custom image .

   For sato image by default it is taking lib64 support , so it work there.
   

On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> wrote:
Hi ,
   Thank You very much , we are able to copy obexpushd to /usr/bin using .bb file.  

  I have one more dout ;
1)  We created our own custom image (bitbake core-image-xxxx) , after flashing image to board . when we run obexpushd binary  it shows as follows :-
    
root@intel-corei7-64:~#
root@intel-corei7-64:~# obexpushd
-sh: /usr/bin/obexpushd: No such file or directory
root@intel-corei7-64:~# cd /usr/bin          
root@intel-corei7-64:/usr/bin# ls | grep obexpush
obexpushd
root@intel-corei7-64:/usr/bin#

Even though binary is there it shows no such file or directory.

2) But when we are flashing a sato image (bitbake core-image-sato-sdk ) , that time obexpushd binary is working fine .
    
    Why it is happening like these ?
    Is there any permission related issue with custom image and sato image ?
 

On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <quentin.schulz@...> wrote:
Hi,

On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
> Hi ,
>      Yours correct only , but the thing is we are taking* binary(obexpushd)*
> from other source and only need to copy that binary into* /usr/bin* of our
> platform(*intel board*).
>
>      Hence how we can achieve these using .bb file ? is there any sample
> example .
>

I gave you what you have to do in the previous mail. Remove the last two
lines of your bb file.

If it does not work, give the full error logs and what you're trying to
achieve and what you have.

Quentin




Quentin Schulz
 

Hi,

On Thu, Nov 19, 2020 at 01:13:43PM +0530, NIKHIL PATIL wrote:
Hi ,
I want to add binary in /usr/bin , for these i made own .bb file (
obexpushtest.bb), When i am compiling obexpushtest package separately
You're not compiling a package, you're compiling a recipe named
obexpushtest whose output is packages (one of which is named the same as
the recipe, hence the confusion).

that time it is compiling fine , but when i am adding obexpushtest in
local.conf as a IMAGE_INSTALL , i am getting error.
But here, you're adding a package into an image. Effectively, the first
and second commands you ran don't do the same thing.

## Error :-

/data/nikhil/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-intel/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:01 ago on Thu 19 Nov 2020 05:57:19 AM
UTC.
No match for argument: obexpushtest
Error: Unable to find a match

## obexpushtest.bb file :-

# file recipes-kernel/linux-firmware/linux-firmware_%.bbappend
SUMMARY = "tset_mount example"
SECTION = "test_mount"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

S = "${WORKDIR}"

SRC_URI += "file://obexpushd"

INSANE_SKIP_${PN} = "ldflags"
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
INHIBIT_PACKAGE_STRIP = "1"
You should probably inherit bin_package but override do_install
(otherwise you'll have an issue with the do_install task coming from the
bin_package bbclass trying to pack your whole ${WORKDIR} (S) which
include way too many files you're not interested in).

do_install_append () {
No need for _append since the following is the only thing your recipe
will do, so better just override do_install.

install -d ${D}/${bindir}
install -m 0644 ${WORKDIR}/obexpushd ${D}/${bindir}
cp ${WORKDIR}/obexpushd ${D}/${bindir}
}

# NOTE: Use "=+" instead of "+=". Otherwise, the file is placed into the
linux-firmware package.
PACKAGES =+ "${PN}-example"
FILES_${PN}-example = "/usr/bin/obexpushd"
Here's the issue, you put your file into the obexpushtest-example and
I'm pretty sure that your obexpushtest package is actually empty and by
default empty packages are removed, hence why the image recipe can't
include this package.

IMHO, no need for your PACKAGES and FILES variables as the default will
put your binary in the obexpushtest package, and since your recipe isn't
creating any other package (explicitly), I don't see the use for a new
package.

Quentin


 

On Thu, 19 Nov 2020 at 08:40, NIKHIL PATIL <nikhilvp29@gmail.com> wrote:

Hi ,
If anyone know , please help on these .
It looks like your original email was sent less than an hour ago, give
people some time.

I also recommend looking at the docs yourself.

Thanks,

--
Paul Barker
Konsulko Group


NIKHIL PATIL
 

Hi ,
    If anyone know , please help on these .

On Thu, Nov 19, 2020 at 1:14 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> wrote:
Hi ,
    I want to add binary in /usr/bin , for these i made own .bb file (obexpushtest.bb),      When i am compiling obexpushtest package separately that time it is compiling fine  , but when i am adding obexpushtest in local.conf as a IMAGE_INSTALL , i am getting error.

## Error :-

/data/nikhil/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-intel/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:01 ago on Thu 19 Nov 2020 05:57:19 AM UTC.
No match for argument: obexpushtest
Error: Unable to find a match
    
## obexpushtest.bb file :-

    # file recipes-kernel/linux-firmware/linux-firmware_%.bbappend
SUMMARY = "tset_mount example"
SECTION = "test_mount"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

S = "${WORKDIR}"

SRC_URI += "file://obexpushd"

INSANE_SKIP_${PN} = "ldflags"
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
INHIBIT_PACKAGE_STRIP = "1"

do_install_append () {
        install -d ${D}/${bindir}
        install -m 0644 ${WORKDIR}/obexpushd ${D}/${bindir}
        cp ${WORKDIR}/obexpushd ${D}/${bindir}
}

# NOTE: Use "=+" instead of "+=". Otherwise, the file is placed into the linux-firmware package.
PACKAGES =+ "${PN}-example"
FILES_${PN}-example = "/usr/bin/obexpushd"









NIKHIL PATIL
 

Hi ,
    I want to add binary in /usr/bin , for these i made own .bb file (obexpushtest.bb),      When i am compiling obexpushtest package separately that time it is compiling fine  , but when i am adding obexpushtest in local.conf as a IMAGE_INSTALL , i am getting error.

## Error :-

/data/nikhil/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-intel/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:01 ago on Thu 19 Nov 2020 05:57:19 AM UTC.
No match for argument: obexpushtest
Error: Unable to find a match
    
## obexpushtest.bb file :-

    # file recipes-kernel/linux-firmware/linux-firmware_%.bbappend
SUMMARY = "tset_mount example"
SECTION = "test_mount"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

S = "${WORKDIR}"

SRC_URI += "file://obexpushd"

INSANE_SKIP_${PN} = "ldflags"
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
INHIBIT_PACKAGE_STRIP = "1"

do_install_append () {
        install -d ${D}/${bindir}
        install -m 0644 ${WORKDIR}/obexpushd ${D}/${bindir}
        cp ${WORKDIR}/obexpushd ${D}/${bindir}
}

# NOTE: Use "=+" instead of "+=". Otherwise, the file is placed into the linux-firmware package.
PACKAGES =+ "${PN}-example"
FILES_${PN}-example = "/usr/bin/obexpushd"






NIKHIL PATIL
 

Hi ,
     Yours correct only , but the thing is we are taking binary(obexpushd) from other source and only need to copy that binary into /usr/bin of our platform(intel board).
     
     Hence how we can achieve these using .bb file ? is there any sample example .

On Thu, Nov 19, 2020 at 2:46 PM Quentin Schulz <quentin.schulz@...> wrote:
Hi,

On Thu, Nov 19, 2020 at 01:13:43PM +0530, NIKHIL PATIL wrote:
> Hi ,
>     I want to add binary in /usr/bin , for these i made own .bb file (
> obexpushtest.bb),      When i am compiling obexpushtest package separately

You're not compiling a package, you're compiling a recipe named
obexpushtest whose output is packages (one of which is named the same as
the recipe, hence the confusion).

> that time it is compiling fine  , but when i am adding obexpushtest in
> local.conf as a IMAGE_INSTALL , i am getting error.
>

But here, you're adding a package into an image. Effectively, the first
and second commands you ran don't do the same thing.

> ## Error :-
>
> /data/nikhil/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-intel/1.0-r0/oe-rootfs-repo
> Last metadata expiration check: 0:00:01 ago on Thu 19 Nov 2020 05:57:19 AM
> UTC.
> No match for argument: obexpushtest
> Error: Unable to find a match
>
> ## obexpushtest.bb file :-
>
>     # file recipes-kernel/linux-firmware/linux-firmware_%.bbappend
> SUMMARY = "tset_mount example"
> SECTION = "test_mount"
> LICENSE = "MIT"
> LIC_FILES_CHKSUM =
> "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
>
> S = "${WORKDIR}"
>
> SRC_URI += "file://obexpushd"
>
> INSANE_SKIP_${PN} = "ldflags"
> INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> INHIBIT_PACKAGE_STRIP = "1"
>

You should probably inherit bin_package but override do_install
(otherwise you'll have an issue with the do_install task coming from the
bin_package bbclass trying to pack your whole ${WORKDIR} (S) which
include way too many files you're not interested in).

> do_install_append () {

No need for _append since the following is the only thing your recipe
will do, so better just override do_install.

>         install -d ${D}/${bindir}
>         install -m 0644 ${WORKDIR}/obexpushd ${D}/${bindir}
>         cp ${WORKDIR}/obexpushd ${D}/${bindir}
> }
>
> # NOTE: Use "=+" instead of "+=". Otherwise, the file is placed into the
> linux-firmware package.
> PACKAGES =+ "${PN}-example"
> FILES_${PN}-example = "/usr/bin/obexpushd"

Here's the issue, you put your file into the obexpushtest-example and
I'm pretty sure that your obexpushtest package is actually empty and by
default empty packages are removed, hence why the image recipe can't
include this package.

IMHO, no need for your PACKAGES and FILES variables as the default will
put your binary in the obexpushtest package, and since your recipe isn't
creating any other package (explicitly), I don't see the use for a new
package.

Quentin


Quentin Schulz
 

Hi,

On Thu, Nov 19, 2020 at 01:13:43PM +0530, NIKHIL PATIL wrote:
Hi ,
I want to add binary in /usr/bin , for these i made own .bb file (
obexpushtest.bb), When i am compiling obexpushtest package separately
You're not compiling a package, you're compiling a recipe named
obexpushtest whose output is packages (one of which is named the same as
the recipe, hence the confusion).

that time it is compiling fine , but when i am adding obexpushtest in
local.conf as a IMAGE_INSTALL , i am getting error.
But here, you're adding a package into an image. Effectively, the first
and second commands you ran don't do the same thing.

## Error :-

/data/nikhil/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-intel/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:01 ago on Thu 19 Nov 2020 05:57:19 AM
UTC.
No match for argument: obexpushtest
Error: Unable to find a match

## obexpushtest.bb file :-

# file recipes-kernel/linux-firmware/linux-firmware_%.bbappend
SUMMARY = "tset_mount example"
SECTION = "test_mount"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

S = "${WORKDIR}"

SRC_URI += "file://obexpushd"

INSANE_SKIP_${PN} = "ldflags"
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
INHIBIT_PACKAGE_STRIP = "1"
You should probably inherit bin_package but override do_install
(otherwise you'll have an issue with the do_install task coming from the
bin_package bbclass trying to pack your whole ${WORKDIR} (S) which
include way too many files you're not interested in).

do_install_append () {
No need for _append since the following is the only thing your recipe
will do, so better just override do_install.

install -d ${D}/${bindir}
install -m 0644 ${WORKDIR}/obexpushd ${D}/${bindir}
cp ${WORKDIR}/obexpushd ${D}/${bindir}
}

# NOTE: Use "=+" instead of "+=". Otherwise, the file is placed into the
linux-firmware package.
PACKAGES =+ "${PN}-example"
FILES_${PN}-example = "/usr/bin/obexpushd"
Here's the issue, you put your file into the obexpushtest-example and
I'm pretty sure that your obexpushtest package is actually empty and by
default empty packages are removed, hence why the image recipe can't
include this package.

IMHO, no need for your PACKAGES and FILES variables as the default will
put your binary in the obexpushtest package, and since your recipe isn't
creating any other package (explicitly), I don't see the use for a new
package.

Quentin


NIKHIL PATIL
 

Hi , 
  for these issue we got solution ,
   obexpushd binary interpreter is on /lib64  folder ,   but in our custom image /lib64 support is not there .
   so we are trying to add lib64 support for our custom image .

   For sato image by default it is taking lib64 support , so it work there.
   

On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> wrote:
Hi ,
   Thank You very much , we are able to copy obexpushd to /usr/bin using .bb file.  

  I have one more dout ;
1)  We created our own custom image (bitbake core-image-xxxx) , after flashing image to board . when we run obexpushd binary  it shows as follows :-
    
root@intel-corei7-64:~#
root@intel-corei7-64:~# obexpushd
-sh: /usr/bin/obexpushd: No such file or directory
root@intel-corei7-64:~# cd /usr/bin          
root@intel-corei7-64:/usr/bin# ls | grep obexpush
obexpushd
root@intel-corei7-64:/usr/bin#

Even though binary is there it shows no such file or directory.

2) But when we are flashing a sato image (bitbake core-image-sato-sdk ) , that time obexpushd binary is working fine .
    
    Why it is happening like these ?
    Is there any permission related issue with custom image and sato image ?
 

On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <quentin.schulz@...> wrote:
Hi,

On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
> Hi ,
>      Yours correct only , but the thing is we are taking* binary(obexpushd)*
> from other source and only need to copy that binary into* /usr/bin* of our
> platform(*intel board*).
>
>      Hence how we can achieve these using .bb file ? is there any sample
> example .
>

I gave you what you have to do in the previous mail. Remove the last two
lines of your bb file.

If it does not work, give the full error logs and what you're trying to
achieve and what you have.

Quentin




NIKHIL PATIL
 

Hi , 
  for these issue we got solution ,
   obexpushd binary interpreter is on /lib64  folder ,   but in our custom image /lib64 support is not there .
   so we are trying to add lib64 support for our custom image .

   For sato image by default it is taking lib64 support , so it work there.
   

On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> wrote:
Hi ,
   Thank You very much , we are able to copy obexpushd to /usr/bin using .bb file.  

  I have one more dout ;
1)  We created our own custom image (bitbake core-image-xxxx) , after flashing image to board . when we run obexpushd binary  it shows as follows :-
    
root@intel-corei7-64:~#
root@intel-corei7-64:~# obexpushd
-sh: /usr/bin/obexpushd: No such file or directory
root@intel-corei7-64:~# cd /usr/bin          
root@intel-corei7-64:/usr/bin# ls | grep obexpush
obexpushd
root@intel-corei7-64:/usr/bin#

Even though binary is there it shows no such file or directory.

2) But when we are flashing a sato image (bitbake core-image-sato-sdk ) , that time obexpushd binary is working fine .
    
    Why it is happening like these ?
    Is there any permission related issue with custom image and sato image ?
 

On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <quentin.schulz@...> wrote:
Hi,

On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
> Hi ,
>      Yours correct only , but the thing is we are taking* binary(obexpushd)*
> from other source and only need to copy that binary into* /usr/bin* of our
> platform(*intel board*).
>
>      Hence how we can achieve these using .bb file ? is there any sample
> example .
>

I gave you what you have to do in the previous mail. Remove the last two
lines of your bb file.

If it does not work, give the full error logs and what you're trying to
achieve and what you have.

Quentin




NIKHIL PATIL
 

Hi , 
  for these issue we got solution ,
   obexpushd binary interpreter is on /lib64  folder ,   but in our custom image /lib64 support is not there .
   so we are trying to add lib64 support for our custom image .

   For sato image by default it is taking lib64 support , so it work there.
   

On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> wrote:
Hi ,
   Thank You very much , we are able to copy obexpushd to /usr/bin using .bb file.  

  I have one more dout ;
1)  We created our own custom image (bitbake core-image-xxxx) , after flashing image to board . when we run obexpushd binary  it shows as follows :-
    
root@intel-corei7-64:~#
root@intel-corei7-64:~# obexpushd
-sh: /usr/bin/obexpushd: No such file or directory
root@intel-corei7-64:~# cd /usr/bin          
root@intel-corei7-64:/usr/bin# ls | grep obexpush
obexpushd
root@intel-corei7-64:/usr/bin#

Even though binary is there it shows no such file or directory.

2) But when we are flashing a sato image (bitbake core-image-sato-sdk ) , that time obexpushd binary is working fine .
    
    Why it is happening like these ?
    Is there any permission related issue with custom image and sato image ?
 

On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <quentin.schulz@...> wrote:
Hi,

On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
> Hi ,
>      Yours correct only , but the thing is we are taking* binary(obexpushd)*
> from other source and only need to copy that binary into* /usr/bin* of our
> platform(*intel board*).
>
>      Hence how we can achieve these using .bb file ? is there any sample
> example .
>

I gave you what you have to do in the previous mail. Remove the last two
lines of your bb file.

If it does not work, give the full error logs and what you're trying to
achieve and what you have.

Quentin




NIKHIL PATIL
 

Hi , 
  for these issue we got solution ,
   obexpushd binary interpreter is on /lib64  folder ,   but in our custom image /lib64 support is not there .
   so we are trying to add lib64 support for our custom image .

   For sato image by default it is taking lib64 support , so it work there.
   

On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> wrote:
Hi ,
   Thank You very much , we are able to copy obexpushd to /usr/bin using .bb file.  

  I have one more dout ;
1)  We created our own custom image (bitbake core-image-xxxx) , after flashing image to board . when we run obexpushd binary  it shows as follows :-
    
root@intel-corei7-64:~#
root@intel-corei7-64:~# obexpushd
-sh: /usr/bin/obexpushd: No such file or directory
root@intel-corei7-64:~# cd /usr/bin          
root@intel-corei7-64:/usr/bin# ls | grep obexpush
obexpushd
root@intel-corei7-64:/usr/bin#

Even though binary is there it shows no such file or directory.

2) But when we are flashing a sato image (bitbake core-image-sato-sdk ) , that time obexpushd binary is working fine .
    
    Why it is happening like these ?
    Is there any permission related issue with custom image and sato image ?
 

On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <quentin.schulz@...> wrote:
Hi,

On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
> Hi ,
>      Yours correct only , but the thing is we are taking* binary(obexpushd)*
> from other source and only need to copy that binary into* /usr/bin* of our
> platform(*intel board*).
>
>      Hence how we can achieve these using .bb file ? is there any sample
> example .
>

I gave you what you have to do in the previous mail. Remove the last two
lines of your bb file.

If it does not work, give the full error logs and what you're trying to
achieve and what you have.

Quentin




NIKHIL PATIL
 

Hi , 
  for these issue we got solution ,
   obexpushd binary interpreter is on /lib64  folder ,   but in our custom image /lib64 support is not there .
   so we are trying to add lib64 support for our custom image .

   For sato image by default it is taking lib64 support , so it work there.
   

On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> wrote:
Hi ,
   Thank You very much , we are able to copy obexpushd to /usr/bin using .bb file.  

  I have one more dout ;
1)  We created our own custom image (bitbake core-image-xxxx) , after flashing image to board . when we run obexpushd binary  it shows as follows :-
    
root@intel-corei7-64:~#
root@intel-corei7-64:~# obexpushd
-sh: /usr/bin/obexpushd: No such file or directory
root@intel-corei7-64:~# cd /usr/bin          
root@intel-corei7-64:/usr/bin# ls | grep obexpush
obexpushd
root@intel-corei7-64:/usr/bin#

Even though binary is there it shows no such file or directory.

2) But when we are flashing a sato image (bitbake core-image-sato-sdk ) , that time obexpushd binary is working fine .
    
    Why it is happening like these ?
    Is there any permission related issue with custom image and sato image ?
 

On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <quentin.schulz@...> wrote:
Hi,

On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
> Hi ,
>      Yours correct only , but the thing is we are taking* binary(obexpushd)*
> from other source and only need to copy that binary into* /usr/bin* of our
> platform(*intel board*).
>
>      Hence how we can achieve these using .bb file ? is there any sample
> example .
>

I gave you what you have to do in the previous mail. Remove the last two
lines of your bb file.

If it does not work, give the full error logs and what you're trying to
achieve and what you have.

Quentin




NIKHIL PATIL
 

Hi , 
  for these issue we got solution ,
   obexpushd binary interpreter is on /lib64  folder ,   but in our custom image /lib64 support is not there .
   so we are trying to add lib64 support for our custom image .

   For sato image by default it is taking lib64 support , so it work there.
   

On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> wrote:
Hi ,
   Thank You very much , we are able to copy obexpushd to /usr/bin using .bb file.  

  I have one more dout ;
1)  We created our own custom image (bitbake core-image-xxxx) , after flashing image to board . when we run obexpushd binary  it shows as follows :-
    
root@intel-corei7-64:~#
root@intel-corei7-64:~# obexpushd
-sh: /usr/bin/obexpushd: No such file or directory
root@intel-corei7-64:~# cd /usr/bin          
root@intel-corei7-64:/usr/bin# ls | grep obexpush
obexpushd
root@intel-corei7-64:/usr/bin#

Even though binary is there it shows no such file or directory.

2) But when we are flashing a sato image (bitbake core-image-sato-sdk ) , that time obexpushd binary is working fine .
    
    Why it is happening like these ?
    Is there any permission related issue with custom image and sato image ?
 

On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <quentin.schulz@...> wrote:
Hi,

On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
> Hi ,
>      Yours correct only , but the thing is we are taking* binary(obexpushd)*
> from other source and only need to copy that binary into* /usr/bin* of our
> platform(*intel board*).
>
>      Hence how we can achieve these using .bb file ? is there any sample
> example .
>

I gave you what you have to do in the previous mail. Remove the last two
lines of your bb file.

If it does not work, give the full error logs and what you're trying to
achieve and what you have.

Quentin