Hi

I'm building an SDK and decided to adapt the default SDK path for each release 
to allow users to have the SDK of multiple releases installed in parallel 
without them changing the path during installation.

According to the Yocto Reference Manual, this can be achieved via the SDKPATH 
variable. Unfortunately changing this variable breaks the generated SDK 
installer.

I'm using Yocto 1.7.1 and generate the SDK with the following command:
        MACHINE=my-machine bitbake core-image-myimage  -c populate_sdk 

First of all, when building the SDK from scratch (fresh build directory), the 
generated installer looks complete, but when trying to run it, I get the 
following error:
        Enter target directory for SDK (default: /opt/mysdk-v2/): 
        You are about to install the SDK to "/ opt/mysdk-v2". Proceed[Y/n]?
        Extracting SDK...done
        Setting it up...ls: cannot access / opt/mysdk-v2/environment-setup-*: 
No such file or directory

Additionally, if I then decide to change the SDK path and generate it NOT from 
scratch, the SDK installer is much smaller, meaning some packages where build 
for the original SDK path only and therefore not installed, if the path changed.

Finally if I revert to use the default SDK path, but don't build it from 
scratch, the installer works, but the generated file is slightly smaller 
(~100K) than the SDK build from scratch.

Is this a bug or maybe SDKPATH isn't meant to be changed?

Best regards

Isak



-- 
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to