Yocto SDK: how to deploy application with step "make install" to target?

Yocto SDK: how to deploy application with step "make install" to target?

[Jerry Lian]

[-- Attachment #1: Type: text/plain, Size: 707 bytes --]

I am new to embedded linux, and some concepts confuse me:
* I have downloaded an Autotools-based application to run on my board.
* If I boot the board with original image/original SDK, I normally
build/install it with steps:
----- ./bootstrap
----- ./configure
----- make
----- make install
* Now if I boot the board with yocto image without SDK, how can I deploy
the application?
---- (surely I do "bitbake -c populate_sdk some-image", and source the
environment!)
----- ./bootstrap (Yocto SDK on host)
----- ./configure (Yocto SDK on host)
----- make         (Yocto SDK on host)
----- make install (???)

* How to do "make install"? (I want to install it on target, but how?)

Thanks!

[-- Attachment #2: Type: text/html, Size: 942 bytes --]

Re: Yocto SDK: how to deploy application with step "make install" to target?

[Eric Schwarz]

Hi Jerry,

Am 01.12.2017 15:07, schrieb Jerry Lian:

> I am new to embedded linux, and some concepts confuse me:
> * I have downloaded an Autotools-based application to run on my board.
> * If I boot the board with original image/original SDK, I normally 
> build/install it with steps:
> ----- ./bootstrap
> ----- ./configure
> ----- make
> ----- make install

You may build your app within yocto build process so your application is 
contained in your rootFS directly.

> * Now if I boot the board with yocto image without SDK, how can I 
> deploy the application?
> ---- (surely I do "bitbake -c populate_sdk some-image", and source the 
> environment!)
> 
> ----- ./bootstrap (Yocto SDK on host)
> ----- ./configure (Yocto SDK on host)
> ----- make         (Yocto SDK on host)
> ----- make install (???)

If you build it w/ the SDK outside of the yocto build process just 
install it to a local directory and copy all the stuff w/ e.g. scp onto 
your boards rootFS.

> * How to do "make install"? (I want to install it on target, but how?)
> 
> Thanks!

Cheers
Eric

Re: Yocto SDK: how to deploy application with step "make install" to target?

[Eric Schwarz]

Am 01.12.2017 15:16, schrieb Eric Schwarz:

> Hi Jerry,
> 
> Am 01.12.2017 15:07, schrieb Jerry Lian:
> 
>> I am new to embedded linux, and some concepts confuse me:
>> * I have downloaded an Autotools-based application to run on my board.
>> * If I boot the board with original image/original SDK, I normally 
>> build/install it with steps:
>> ----- ./bootstrap
>> ----- ./configure
>> ----- make
>> ----- make install
> 
> You may build your app within yocto build process so your application 
> is contained in your rootFS directly.
> 
>> * Now if I boot the board with yocto image without SDK, how can I 
>> deploy the application?
>> ---- (surely I do "bitbake -c populate_sdk some-image", and source the 
>> environment!)
>> 
>> ----- ./bootstrap (Yocto SDK on host)
>> ----- ./configure (Yocto SDK on host)
>> ----- make         (Yocto SDK on host)
>> ----- make install (???)
> 
> If you build it w/ the SDK outside of the yocto build process just 
> install it to a local directory and copy all the stuff w/ e.g. scp onto 
> your boards rootFS.

... you may supply a custom install prefix directory to configure.

> 
>> * How to do "make install"? (I want to install it on target, but how?)
>> 
>> Thanks!
> 
> Cheers
> Eric

Re: Yocto SDK: how to deploy application with step "make install" to target?

[Jerry Lian]

[-- Attachment #1: Type: text/plain, Size: 2075 bytes --]

Thanks Eric for your explanation!
* (I know I can build the app within yocto build, but sometimes I prefer
the SDK method outside yocto build.)
* So just copy manually? I thought there are some tricks  that I don't know.

Now I have follow-up question:
* It seems that "make install" will copy different files to different
folders
* Can I do like these:?
--- make
--- copy (via scp)
--- make install
* Or it needs to be:
--- make
--- make install
--- copy (via scp) -----then how do I know: what files to go which folder?
--- can you explain:
    "... you may supply a custom install prefix directory to configure."
--- how?

Thanks!





On Fri, Dec 1, 2017 at 9:34 AM, Eric Schwarz <eas@sw-optimization.com>
wrote:

> Am 01.12.2017 15:16, schrieb Eric Schwarz:
>
> Hi Jerry,
>>
>> Am 01.12.2017 15:07, schrieb Jerry Lian:
>>
>> I am new to embedded linux, and some concepts confuse me:
>>> * I have downloaded an Autotools-based application to run on my board.
>>> * If I boot the board with original image/original SDK, I normally
>>> build/install it with steps:
>>> ----- ./bootstrap
>>> ----- ./configure
>>> ----- make
>>> ----- make install
>>>
>>
>> You may build your app within yocto build process so your application is
>> contained in your rootFS directly.
>>
>> * Now if I boot the board with yocto image without SDK, how can I deploy
>>> the application?
>>> ---- (surely I do "bitbake -c populate_sdk some-image", and source the
>>> environment!)
>>>
>>> ----- ./bootstrap (Yocto SDK on host)
>>> ----- ./configure (Yocto SDK on host)
>>> ----- make         (Yocto SDK on host)
>>> ----- make install (???)
>>>
>>
>> If you build it w/ the SDK outside of the yocto build process just
>> install it to a local directory and copy all the stuff w/ e.g. scp onto
>> your boards rootFS.
>>
>
> ... you may supply a custom install prefix directory to configure.
>
>
>
>> * How to do "make install"? (I want to install it on target, but how?)
>>>
>>> Thanks!
>>>
>>
>> Cheers
>> Eric
>>
>

[-- Attachment #2: Type: text/html, Size: 3374 bytes --]

Re: Yocto SDK: how to deploy application with step "make install" to target?

[Eric Schwarz]

Am 01.12.2017 16:15, schrieb Jerry Lian:

> Thanks Eric for your explanation!
> * (I know I can build the app within yocto build, but sometimes I 
> prefer the SDK method outside yocto build.)
> 
> * So just copy manually? I thought there are some tricks  that I don't 
> know.
> 

Acutally that's how we are doing it ...

> Now I have follow-up question:
> * It seems that "make install" will copy different files to different 
> folders
> * Can I do like these:?
> --- make
> --- copy (via scp)
> --- make install
> * Or it needs to be:
> --- make
> --- make install

Install the cross-compiled stuff on your local disc e.g. into a 
"transfer" directory. Then copy it to the target.
On the target 'cp -Rfa <transfer-dir>/* /' should do it if the basic 
directory structure fits to your rootFS.

> --- copy (via scp) -----then how do I know: what files to go which 
> folder?
> --- can you explain:
> "... you may supply a custom install prefix directory to configure." 
> --- how?
> 

There is IMHO no standardized variable available. Just look into the 
configure script how the variable is named and if it is actually 
available at all.

> Thanks!
> 
> On Fri, Dec 1, 2017 at 9:34 AM, Eric Schwarz <eas@sw-optimization.com> 
> wrote:
> Am 01.12.2017 15:16, schrieb Eric Schwarz:
> 
> Hi Jerry,
> 
> Am 01.12.2017 15:07, schrieb Jerry Lian:
> 
> I am new to embedded linux, and some concepts confuse me:
> * I have downloaded an Autotools-based application to run on my board.
> * If I boot the board with original image/original SDK, I normally 
> build/install it with steps:
> ----- ./bootstrap
> ----- ./configure
> ----- make
> ----- make install
> You may build your app within yocto build process so your application 
> is contained in your rootFS directly.
> 
> * Now if I boot the board with yocto image without SDK, how can I 
> deploy the application?
> ---- (surely I do "bitbake -c populate_sdk some-image", and source the 
> environment!)
> 
> ----- ./bootstrap (Yocto SDK on host)
> ----- ./configure (Yocto SDK on host)
> ----- make         (Yocto SDK on host)
> ----- make install (???)
> If you build it w/ the SDK outside of the yocto build process just 
> install it to a local directory and copy all the stuff w/ e.g. scp onto 
> your boards rootFS.
  ... you may supply a custom install prefix directory to configure.

>> * How to do "make install"? (I want to install it on target, but how?)
>> 
>> Thanks!
> 
> Cheers
> Eric

Re: Yocto SDK: how to deploy application with step "make install" to target?

[Jerry Lian]

[-- Attachment #1: Type: text/plain, Size: 5317 bytes --]

Thanks Eric again.
* So you mean "copy -Rfa" can match folder-by-folder, so long as the
folder-tree are the same?
                (if yes, that is super great!!!)
* I check that "make install" copy files to one folder, so that is easy for
deployment!

Another question:
* My application actually has another step: "make modules_install" (surely
step "make modules" also)
* But I got error (see below):
               what could be wrong with "SSL error"? isn't build already
passed successfully?

------------------------------------------------------------
----------------------------------------
jerry@yct:~/ecat-33b922$ make modules_install
make -C "/usr/src/linux-headers-4.10.0-28-generic"
M="/home/jerry/ecat-33b922" \
    INSTALL_MOD_DIR="ethercat" modules_install
make[1]: Entering directory '/usr/src/linux-headers-4.10.0-28-generic'
mkdir: cannot create directory ‘/lib/modules/4.10.0-28-generic/ethercat’:
Permission denied
Makefile:1536: recipe for target '_emodinst_' failed
make[1]: *** [_emodinst_] Error 1
make[1]: Leaving directory '/usr/src/linux-headers-4.10.0-28-generic'
Makefile:934: recipe for target 'modules_install' failed
make: *** [modules_install] Error 2

jerry@yct:~/ecat-33b922$ sudo make modules_install
make -C "/usr/src/linux-headers-4.10.0-28-generic"
M="/home/jerry/ecat-33b922" \
    INSTALL_MOD_DIR="ethercat" modules_install
make[1]: Entering directory '/usr/src/linux-headers-4.10.0-28-generic'
  INSTALL /home/jerry/ecat-33b922/devices/ec_generic.ko
At main.c:158:
- SSL error:02001002:system library:fopen:No such file or directory:
bss_file.c:175
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178
sign-file: certs/signing_key.pem: No such file or directory
  INSTALL /home/jerry/ecat-33b922/examples/mini/ec_mini.ko
At main.c:158:
- SSL error:02001002:system library:fopen:No such file or directory:
bss_file.c:175
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178
sign-file: certs/signing_key.pem: No such file or directory
  INSTALL /home/jerry/ecat-33b922/master/ec_master.ko
At main.c:158:
- SSL error:02001002:system library:fopen:No such file or directory:
bss_file.c:175
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178
sign-file: certs/signing_key.pem: No such file or directory
  DEPMOD  4.10.0-28-generic
make[1]: Leaving directory '/usr/src/linux-headers-4.10.0-28-generic'

jerry@yct:~/ecat-33b922$
------------------------------------------------------------
-------------------------------------------

Thanks!






On Fri, Dec 1, 2017 at 10:37 AM, Eric Schwarz <eas@sw-optimization.com>
wrote:

> Am 01.12.2017 16:15, schrieb Jerry Lian:
>
> Thanks Eric for your explanation!
>> * (I know I can build the app within yocto build, but sometimes I prefer
>> the SDK method outside yocto build.)
>>
>> * So just copy manually? I thought there are some tricks  that I don't
>> know.
>>
>>
> Acutally that's how we are doing it ...
>
> Now I have follow-up question:
>> * It seems that "make install" will copy different files to different
>> folders
>> * Can I do like these:?
>> --- make
>> --- copy (via scp)
>> --- make install
>> * Or it needs to be:
>> --- make
>> --- make install
>>
>
> Install the cross-compiled stuff on your local disc e.g. into a "transfer"
> directory. Then copy it to the target.
> On the target 'cp -Rfa <transfer-dir>/* /' should do it if the basic
> directory structure fits to your rootFS.
>
> --- copy (via scp) -----then how do I know: what files to go which folder?
>> --- can you explain:
>> "... you may supply a custom install prefix directory to configure." ---
>> how?
>>
>>
> There is IMHO no standardized variable available. Just look into the
> configure script how the variable is named and if it is actually available
> at all.
>
>
> Thanks!
>>
>> On Fri, Dec 1, 2017 at 9:34 AM, Eric Schwarz <eas@sw-optimization.com>
>> wrote:
>> Am 01.12.2017 15:16, schrieb Eric Schwarz:
>>
>> Hi Jerry,
>>
>> Am 01.12.2017 15:07, schrieb Jerry Lian:
>>
>> I am new to embedded linux, and some concepts confuse me:
>> * I have downloaded an Autotools-based application to run on my board.
>> * If I boot the board with original image/original SDK, I normally
>> build/install it with steps:
>> ----- ./bootstrap
>> ----- ./configure
>> ----- make
>> ----- make install
>> You may build your app within yocto build process so your application is
>> contained in your rootFS directly.
>>
>> * Now if I boot the board with yocto image without SDK, how can I deploy
>> the application?
>> ---- (surely I do "bitbake -c populate_sdk some-image", and source the
>> environment!)
>>
>> ----- ./bootstrap (Yocto SDK on host)
>> ----- ./configure (Yocto SDK on host)
>> ----- make         (Yocto SDK on host)
>> ----- make install (???)
>> If you build it w/ the SDK outside of the yocto build process just
>> install it to a local directory and copy all the stuff w/ e.g. scp onto
>> your boards rootFS.
>>
>  ... you may supply a custom install prefix directory to configure.
>
> * How to do "make install"? (I want to install it on target, but how?)
>>>
>>> Thanks!
>>>
>>
>> Cheers
>> Eric
>>
>

[-- Attachment #2: Type: text/html, Size: 7091 bytes --]

Re: Yocto SDK: how to deploy application with step "make install" to target?

[Eric Schwarz]

Am 01.12.2017 16:58, schrieb Jerry Lian:

> Thanks Eric again.
> * So you mean "copy -Rfa" can match folder-by-folder, so long as the 
> folder-tree are the same?
> (if yes, that is super great!!!)

Yes.

> * I check that "make install" copy files to one folder, so that is easy 
> for deployment!
> 
> Another question:
> * My application actually has another step: "make modules_install" 
> (surely step "make modules" also)
> * But I got error (see below):
> what could be wrong with "SSL error"? isn't build already passed 
> successfully?

You are doing the 'make modules_install' on the target or where else? 
You need to build the modules within the Yocto environment and may 
create a package e.g. *.deb you may install later on the target or copy 
the modules by hand including relevant other files needed. Obviously the 
system tries to recompile the kernel modules. That's what 'make 
modules_install' does.

> 
> ----------------------------------------------------------------------------------------------------
> jerry@yct:~/ecat-33b922$ make modules_install
> make -C "/usr/src/linux-headers-4.10.0-28-generic" 
> M="/home/jerry/ecat-33b922" \
> INSTALL_MOD_DIR="ethercat" modules_install
> make[1]: Entering directory '/usr/src/linux-headers-4.10.0-28-generic'
> mkdir: cannot create directory 
> '/lib/modules/4.10.0-28-generic/ethercat': Permission denied
> Makefile:1536: recipe for target '_emodinst_' failed
> make[1]: *** [_emodinst_] Error 1
> make[1]: Leaving directory '/usr/src/linux-headers-4.10.0-28-generic'
> Makefile:934: recipe for target 'modules_install' failed
> make: *** [modules_install] Error 2
> 
> jerry@yct:~/ecat-33b922$ sudo make modules_install
> make -C "/usr/src/linux-headers-4.10.0-28-generic" 
> M="/home/jerry/ecat-33b922" \
> INSTALL_MOD_DIR="ethercat" modules_install
> make[1]: Entering directory '/usr/src/linux-headers-4.10.0-28-generic'
> INSTALL /home/jerry/ecat-33b922/devices/ec_generic.ko
> At main.c:158:
> - SSL error:02001002:system library:fopen:No such file or directory: 
> bss_file.c:175
> - SSL error:2006D080:BIO routines:BIO_new_file:no such file: 
> bss_file.c:178
> sign-file: certs/signing_key.pem: No such file or directory
> INSTALL /home/jerry/ecat-33b922/examples/mini/ec_mini.ko
> At main.c:158:
> - SSL error:02001002:system library:fopen:No such file or directory: 
> bss_file.c:175
> - SSL error:2006D080:BIO routines:BIO_new_file:no such file: 
> bss_file.c:178
> sign-file: certs/signing_key.pem: No such file or directory
> INSTALL /home/jerry/ecat-33b922/master/ec_master.ko
> At main.c:158:
> - SSL error:02001002:system library:fopen:No such file or directory: 
> bss_file.c:175
> - SSL error:2006D080:BIO routines:BIO_new_file:no such file: 
> bss_file.c:178
> sign-file: certs/signing_key.pem: No such file or directory
> DEPMOD  4.10.0-28-generic
> make[1]: Leaving directory '/usr/src/linux-headers-4.10.0-28-generic'
> 
> jerry@yct:~/ecat-33b922$
> -------------------------------------------------------------------------------------------------------
> 
> Thanks!
> 
> On Fri, Dec 1, 2017 at 10:37 AM, Eric Schwarz <eas@sw-optimization.com> 
> wrote:
> Am 01.12.2017 16:15, schrieb Jerry Lian:
> 
> Thanks Eric for your explanation!
> * (I know I can build the app within yocto build, but sometimes I 
> prefer the SDK method outside yocto build.)
> 
> * So just copy manually? I thought there are some tricks  that I don't 
> know.
> 
> Acutally that's how we are doing it ...
> 
> Now I have follow-up question:
> * It seems that "make install" will copy different files to different 
> folders
> * Can I do like these:?
> --- make
> --- copy (via scp)
> --- make install
> * Or it needs to be:
> --- make
> --- make install Install the cross-compiled stuff on your local disc 
> e.g. into a "transfer" directory. Then copy it to the target.
> On the target 'cp -Rfa <transfer-dir>/* /' should do it if the basic 
> directory structure fits to your rootFS.
> 
> --- copy (via scp) -----then how do I know: what files to go which 
> folder?
> --- can you explain:
> "... you may supply a custom install prefix directory to configure." 
> --- how?
> 
> There is IMHO no standardized variable available. Just look into the 
> configure script how the variable is named and if it is actually 
> available at all.
> 
> Thanks!
> 
> On Fri, Dec 1, 2017 at 9:34 AM, Eric Schwarz <eas@sw-optimization.com> 
> wrote:
> Am 01.12.2017 15:16, schrieb Eric Schwarz:
> 
> Hi Jerry,
> 
> Am 01.12.2017 15:07, schrieb Jerry Lian:
> 
> I am new to embedded linux, and some concepts confuse me:
> * I have downloaded an Autotools-based application to run on my board.
> * If I boot the board with original image/original SDK, I normally 
> build/install it with steps:
> ----- ./bootstrap
> ----- ./configure
> ----- make
> ----- make install
> You may build your app within yocto build process so your application 
> is contained in your rootFS directly.
> 
> * Now if I boot the board with yocto image without SDK, how can I 
> deploy the application?
> ---- (surely I do "bitbake -c populate_sdk some-image", and source the 
> environment!)
> 
> ----- ./bootstrap (Yocto SDK on host)
> ----- ./configure (Yocto SDK on host)
> ----- make         (Yocto SDK on host)
> ----- make install (???)
> If you build it w/ the SDK outside of the yocto build process just 
> install it to a local directory and copy all the stuff w/ e.g. scp onto 
> your boards rootFS.  ... you may supply a custom install prefix 
> directory to configure.
> 
> * How to do "make install"? (I want to install it on target, but how?)
> 
> Thanks!
> Cheers
> Eric

Re: Yocto SDK: how to deploy application with step "make install" to target?

[Jerry Lian]

[-- Attachment #1: Type: text/plain, Size: 6430 bytes --]

OK, that is what confused me: I DID try "make modules_install" on host!

So according to what you said, the right procedure is:
* do          "make install"                on host, then copy to target:
* don't do "make modules_install" on host, but make a package first, then
copy to target and install.
* right?

* then how to make a package?
* how do I know which are "relevant other files"?

sorry for my newbie questions, thanks!





On Fri, Dec 1, 2017 at 11:30 AM, Eric Schwarz <eas@sw-optimization.com>
wrote:

> Am 01.12.2017 16:58, schrieb Jerry Lian:
>
> Thanks Eric again.
>> * So you mean "copy -Rfa" can match folder-by-folder, so long as the
>> folder-tree are the same?
>> (if yes, that is super great!!!)
>>
>
> Yes.
>
> * I check that "make install" copy files to one folder, so that is easy
>> for deployment!
>>
>> Another question:
>> * My application actually has another step: "make modules_install"
>> (surely step "make modules" also)
>> * But I got error (see below):
>> what could be wrong with "SSL error"? isn't build already passed
>> successfully?
>>
>
> You are doing the 'make modules_install' on the target or where else? You
> need to build the modules within the Yocto environment and may create a
> package e.g. *.deb you may install later on the target or copy the modules
> by hand including relevant other files needed. Obviously the system tries
> to recompile the kernel modules. That's what 'make modules_install' does.
>
>
>
>> ------------------------------------------------------------
>> ----------------------------------------
>> jerry@yct:~/ecat-33b922$ make modules_install
>> make -C "/usr/src/linux-headers-4.10.0-28-generic"
>> M="/home/jerry/ecat-33b922" \
>> INSTALL_MOD_DIR="ethercat" modules_install
>> make[1]: Entering directory '/usr/src/linux-headers-4.10.0-28-generic'
>> mkdir: cannot create directory '/lib/modules/4.10.0-28-generic/ethercat':
>> Permission denied
>> Makefile:1536: recipe for target '_emodinst_' failed
>> make[1]: *** [_emodinst_] Error 1
>> make[1]: Leaving directory '/usr/src/linux-headers-4.10.0-28-generic'
>> Makefile:934: recipe for target 'modules_install' failed
>> make: *** [modules_install] Error 2
>>
>> jerry@yct:~/ecat-33b922$ sudo make modules_install
>> make -C "/usr/src/linux-headers-4.10.0-28-generic"
>> M="/home/jerry/ecat-33b922" \
>> INSTALL_MOD_DIR="ethercat" modules_install
>> make[1]: Entering directory '/usr/src/linux-headers-4.10.0-28-generic'
>> INSTALL /home/jerry/ecat-33b922/devices/ec_generic.ko
>> At main.c:158:
>> - SSL error:02001002:system library:fopen:No such file or directory:
>> bss_file.c:175
>> - SSL error:2006D080:BIO routines:BIO_new_file:no such file:
>> bss_file.c:178
>> sign-file: certs/signing_key.pem: No such file or directory
>> INSTALL /home/jerry/ecat-33b922/examples/mini/ec_mini.ko
>> At main.c:158:
>> - SSL error:02001002:system library:fopen:No such file or directory:
>> bss_file.c:175
>> - SSL error:2006D080:BIO routines:BIO_new_file:no such file:
>> bss_file.c:178
>> sign-file: certs/signing_key.pem: No such file or directory
>> INSTALL /home/jerry/ecat-33b922/master/ec_master.ko
>> At main.c:158:
>> - SSL error:02001002:system library:fopen:No such file or directory:
>> bss_file.c:175
>> - SSL error:2006D080:BIO routines:BIO_new_file:no such file:
>> bss_file.c:178
>> sign-file: certs/signing_key.pem: No such file or directory
>> DEPMOD  4.10.0-28-generic
>> make[1]: Leaving directory '/usr/src/linux-headers-4.10.0-28-generic'
>>
>> jerry@yct:~/ecat-33b922$
>> ------------------------------------------------------------
>> -------------------------------------------
>>
>> Thanks!
>>
>> On Fri, Dec 1, 2017 at 10:37 AM, Eric Schwarz <eas@sw-optimization.com>
>> wrote:
>> Am 01.12.2017 16:15, schrieb Jerry Lian:
>>
>> Thanks Eric for your explanation!
>> * (I know I can build the app within yocto build, but sometimes I prefer
>> the SDK method outside yocto build.)
>>
>> * So just copy manually? I thought there are some tricks  that I don't
>> know.
>>
>> Acutally that's how we are doing it ...
>>
>> Now I have follow-up question:
>> * It seems that "make install" will copy different files to different
>> folders
>> * Can I do like these:?
>> --- make
>> --- copy (via scp)
>> --- make install
>> * Or it needs to be:
>> --- make
>> --- make install Install the cross-compiled stuff on your local disc e.g.
>> into a "transfer" directory. Then copy it to the target.
>> On the target 'cp -Rfa <transfer-dir>/* /' should do it if the basic
>> directory structure fits to your rootFS.
>>
>> --- copy (via scp) -----then how do I know: what files to go which folder?
>> --- can you explain:
>> "... you may supply a custom install prefix directory to configure." ---
>> how?
>>
>> There is IMHO no standardized variable available. Just look into the
>> configure script how the variable is named and if it is actually available
>> at all.
>>
>> Thanks!
>>
>> On Fri, Dec 1, 2017 at 9:34 AM, Eric Schwarz <eas@sw-optimization.com>
>> wrote:
>> Am 01.12.2017 15:16, schrieb Eric Schwarz:
>>
>> Hi Jerry,
>>
>> Am 01.12.2017 15:07, schrieb Jerry Lian:
>>
>> I am new to embedded linux, and some concepts confuse me:
>> * I have downloaded an Autotools-based application to run on my board.
>> * If I boot the board with original image/original SDK, I normally
>> build/install it with steps:
>> ----- ./bootstrap
>> ----- ./configure
>> ----- make
>> ----- make install
>> You may build your app within yocto build process so your application is
>> contained in your rootFS directly.
>>
>> * Now if I boot the board with yocto image without SDK, how can I deploy
>> the application?
>> ---- (surely I do "bitbake -c populate_sdk some-image", and source the
>> environment!)
>>
>> ----- ./bootstrap (Yocto SDK on host)
>> ----- ./configure (Yocto SDK on host)
>> ----- make         (Yocto SDK on host)
>> ----- make install (???)
>> If you build it w/ the SDK outside of the yocto build process just
>> install it to a local directory and copy all the stuff w/ e.g. scp onto
>> your boards rootFS.  ... you may supply a custom install prefix directory
>> to configure.
>>
>> * How to do "make install"? (I want to install it on target, but how?)
>>
>> Thanks!
>> Cheers
>> Eric
>>
>

[-- Attachment #2: Type: text/html, Size: 7859 bytes --]

Re: Yocto SDK: how to deploy application with step "make install" to target?

[Philip Balister]

On 12/01/2017 10:15 AM, Jerry Lian wrote:
> Thanks Eric for your explanation!
> * (I know I can build the app within yocto build, but sometimes I prefer
> the SDK method outside yocto build.)
> * So just copy manually? I thought there are some tricks  that I don't know.
> 
> Now I have follow-up question:
> * It seems that "make install" will copy different files to different
> folders
> * Can I do like these:?
> --- make
> --- copy (via scp)
> --- make install
> * Or it needs to be:
> --- make
> --- make install
> --- copy (via scp) -----then how do I know: what files to go which folder?
> --- can you explain:
>     "... you may supply a custom install prefix directory to configure."
> --- how?

I've used sshfs to mount the target on the machine with the sdk and then
something like:

make install DESTDIR=~/mydevice

From:

https://wiki.gnuradio.org/index.php/Cross_compile_an_OOT_and_install_on_target

Philip

> 
> Thanks!
> 
> 
> 
> 
> 
> On Fri, Dec 1, 2017 at 9:34 AM, Eric Schwarz <eas@sw-optimization.com>
> wrote:
> 
>> Am 01.12.2017 15:16, schrieb Eric Schwarz:
>>
>> Hi Jerry,
>>>
>>> Am 01.12.2017 15:07, schrieb Jerry Lian:
>>>
>>> I am new to embedded linux, and some concepts confuse me:
>>>> * I have downloaded an Autotools-based application to run on my board.
>>>> * If I boot the board with original image/original SDK, I normally
>>>> build/install it with steps:
>>>> ----- ./bootstrap
>>>> ----- ./configure
>>>> ----- make
>>>> ----- make install
>>>>
>>>
>>> You may build your app within yocto build process so your application is
>>> contained in your rootFS directly.
>>>
>>> * Now if I boot the board with yocto image without SDK, how can I deploy
>>>> the application?
>>>> ---- (surely I do "bitbake -c populate_sdk some-image", and source the
>>>> environment!)
>>>>
>>>> ----- ./bootstrap (Yocto SDK on host)
>>>> ----- ./configure (Yocto SDK on host)
>>>> ----- make         (Yocto SDK on host)
>>>> ----- make install (???)
>>>>
>>>
>>> If you build it w/ the SDK outside of the yocto build process just
>>> install it to a local directory and copy all the stuff w/ e.g. scp onto
>>> your boards rootFS.
>>>
>>
>> ... you may supply a custom install prefix directory to configure.
>>
>>
>>
>>> * How to do "make install"? (I want to install it on target, but how?)
>>>>
>>>> Thanks!
>>>>
>>>
>>> Cheers
>>> Eric
>>>
>>
> 
> 
> 

Re: Yocto SDK: how to deploy application with step "make install" to target?

[Jerry Lian]

[-- Attachment #1: Type: text/plain, Size: 2908 bytes --]

Thanks Philip!
I will try "sshfs" later. Right now using copy (via scp) works fine for
both "make install" and "make modules_install", and my application runs.





On Sun, Dec 3, 2017 at 9:17 AM, Philip Balister <philip@balister.org> wrote:

> On 12/01/2017 10:15 AM, Jerry Lian wrote:
> > Thanks Eric for your explanation!
> > * (I know I can build the app within yocto build, but sometimes I prefer
> > the SDK method outside yocto build.)
> > * So just copy manually? I thought there are some tricks  that I don't
> know.
> >
> > Now I have follow-up question:
> > * It seems that "make install" will copy different files to different
> > folders
> > * Can I do like these:?
> > --- make
> > --- copy (via scp)
> > --- make install
> > * Or it needs to be:
> > --- make
> > --- make install
> > --- copy (via scp) -----then how do I know: what files to go which
> folder?
> > --- can you explain:
> >     "... you may supply a custom install prefix directory to configure."
> > --- how?
>
> I've used sshfs to mount the target on the machine with the sdk and then
> something like:
>
> make install DESTDIR=~/mydevice
>
> From:
>
> https://wiki.gnuradio.org/index.php/Cross_compile_an_
> OOT_and_install_on_target
>
> Philip
>
> >
> > Thanks!
> >
> >
> >
> >
> >
> > On Fri, Dec 1, 2017 at 9:34 AM, Eric Schwarz <eas@sw-optimization.com>
> > wrote:
> >
> >> Am 01.12.2017 15:16, schrieb Eric Schwarz:
> >>
> >> Hi Jerry,
> >>>
> >>> Am 01.12.2017 15:07, schrieb Jerry Lian:
> >>>
> >>> I am new to embedded linux, and some concepts confuse me:
> >>>> * I have downloaded an Autotools-based application to run on my board.
> >>>> * If I boot the board with original image/original SDK, I normally
> >>>> build/install it with steps:
> >>>> ----- ./bootstrap
> >>>> ----- ./configure
> >>>> ----- make
> >>>> ----- make install
> >>>>
> >>>
> >>> You may build your app within yocto build process so your application
> is
> >>> contained in your rootFS directly.
> >>>
> >>> * Now if I boot the board with yocto image without SDK, how can I
> deploy
> >>>> the application?
> >>>> ---- (surely I do "bitbake -c populate_sdk some-image", and source the
> >>>> environment!)
> >>>>
> >>>> ----- ./bootstrap (Yocto SDK on host)
> >>>> ----- ./configure (Yocto SDK on host)
> >>>> ----- make         (Yocto SDK on host)
> >>>> ----- make install (???)
> >>>>
> >>>
> >>> If you build it w/ the SDK outside of the yocto build process just
> >>> install it to a local directory and copy all the stuff w/ e.g. scp onto
> >>> your boards rootFS.
> >>>
> >>
> >> ... you may supply a custom install prefix directory to configure.
> >>
> >>
> >>
> >>> * How to do "make install"? (I want to install it on target, but how?)
> >>>>
> >>>> Thanks!
> >>>>
> >>>
> >>> Cheers
> >>> Eric
> >>>
> >>
> >
> >
> >
>

[-- Attachment #2: Type: text/html, Size: 4395 bytes --]