When i come to the step MACHINE=cyclone5 . ./setup-environment i see an error saying that the folder setup-environment does not exist. not sure how to go about this. any inputs would be greatly appreciated!
Iâm not sure if .repo/local_manifests/altera.xml can append/overwrite to default.xml (iâm not a repo-tool expert) but if after you do repo sync you canât see setup-environment* scripts maybe is because the altera.xml manifest⌠can you post your .repo/manifest.xml (it is a soft link to the real one)
hello,
from your reply, i noticed that the setup-environment file was not in the angstrom-build folder. it was outside it. does it need to be in that folder? also the name is setup-environment.
after moved the file to the angstrom-build folder, and run Machine=cyclone5⌠command, i see the below, which i assume is correct??
looks like you are messing things up with sed command probably a space before a backslash, not sure iâm not familiar with regexp, but they put this to add meta-altera-refdes to bblayers, bitbake already has a tool for this(if you donât want to manually edit the bblayers file).
No, bitbake will be available whenever you setup your build environment, commonly using oe-init-build-env but it looks like your setup-environment script set your PATH already.
Short Answer : You will only be available to run bitbake after sourcing your setup-environment script.
okay. i am a novice and have trouble understanding this. what does sourcing the setup-environment script mean? how do i do that. sorry for asking a lot of questions. thanks for taking the time again!
Ok it looks like the setup script is doing its job, i just follow the steps that you should be following and this is what your angstrom dir should be looking after a $repo sync
Then after sourcing the setup script i can run bitbake as you can see in the following image
Also, I notice that if i add a build_test where i want to keep my build configuration isolated it canât find the âlayersâ dir⌠i think they only give the option to have just one builddir i.e. angstrom-build.
I think what you did wrong was to badly export your PATH
I donât know why you have meta-* outside angstrom-build not sure if you are also using linux-socfpga-gsrd-13.1-src.bsx to setup your build-environment⌠you should be following just one set of instructions and not mixing them if you are not really sure what you are doing.
Probably the only thing that you need is as you said move bitbake dir to your angstrom-build/, but i donât know if this bitbake dir that you have in there was the one downloaded by repo sync operation or linux-socfpga-gsrd-13.1-src.bsx install method. You should be using the one that corresponds with the version of your meta-*
on your suggestion, i moved the bitbake folder to theangstrom-build environment. i honestly dont know if that folder was from another project i was working on. i donât think i organised these folders right. i probably need to delete this folder and re-do it.
after i moved the bitbake folder, i tried the bitbake command to run into another error.
Yes, you will probably need to delete these dirs and start all over again remember to set properly your PATH before you do repo sync.
About the error looks like you missed the following instructions:
$ sed -i â/meta-altera/a \ \ ${TOPDIR}/layers/meta-altera-refdes \â conf/bblayers.conf # This is to add the meta-altera-refdes layer to conf/bblayers.conf
$ sed -i â/meta-atmel/dâ conf/bblayers.conf # this has conflicting packages
$ sed -i â/meta-freescale/dâ conf/bblayers.conf # this has conflicting packages
$ echo âDISTRO_FEATURES_remove = " wayland "â >> conf/local.conf # broke builds prior to this not needed for GSRD
$ echo âDISTRO_FEATURES_remove = " alsa "â >> conf/local.conf # breaking builds prior to this not needed for GSRD
$ rm layers/meta-altera-refdes/recipes-devtools/socfpga-test/socfpga-test_1.0.bb # developmental unit tests stub for older kernels
$ export KERNEL_PROVIDER=linux-altera-ltsi
$ export KERNEL_TAG=refs/tags/ACDS19.3_REL_GSRD_PR
$ export KBRANCH=socfpga-4.14.130-ltsi
$ export BB_ENV_EXTRAWHITE=â$BB_ENV_EXTRAWHITE KBRANCH KERNEL_TAG UBOOT_TAG KERNEL_PROVIDERâ
i did a cleanup of the folders and started the process again. it went much smoother than before though i did encounter an error in the last step which was different than the previous errors that i saw. one question that i have about repo sync is, whenever i executed that command, i saw the .repo folder come up in a different folder. how do i have it sync in the folder that i want?
below is what i see nowâŚ