Well I grabbed the .deb that one of those links mentioned and converted it to an rpm, but of course there are a ton of unmet dependencies, so I might have to build it anyway.
I found these instructions for building it, which are pinned to an older version (which is probably fine) https://github.com/futurejones/code-oss-aarch64 I have gotten most of the dependencies built with bitbake, except for the x11 stuff: ERROR: Nothing RPROVIDES 'packagegroup-core-x11' (but /home/aarons/sri/bullitt/nxp/imx-yocto-bsp/sources/meta-fsl-bsp-release/imx/meta-sdk/dynamic-layers/qt5-layer/recipes-fsl/images/fsl-image-qt5-validation-imx.bb RDEPENDS on or otherwise requires it) packagegroup-core-x11 was skipped: missing required distro feature 'x11' (not in DISTRO_FEATURES) NOTE: Runtime target 'packagegroup-core-x11' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-core-x11'] ERROR: Required build target 'fsl-image-qt5-validation-imx' has no buildable providers. Missing or unbuildable dependency chain was: ['fsl-image-qt5-validation-imx', 'packagegroup-core-x11'] But this is my local.conf: MACHINE ??= 'imx8mqevk' DISTRO ?= 'fsl-imx-wayland' PACKAGE_CLASSES ?= "package_rpm" EXTRA_IMAGE_FEATURES ?= "debug-tweaks" USER_CLASSES ?= "buildstats image-mklibs image-prelink" PATCHRESOLVE = "noop" BB_DISKMON_DIRS ??= "\ STOPTASKS,${TMPDIR},1G,100K \ STOPTASKS,${DL_DIR},1G,100K \ STOPTASKS,${SSTATE_DIR},1G,100K \ STOPTASKS,/tmp,100M,100K \ ABORT,${TMPDIR},100M,1K \ ABORT,${DL_DIR},100M,1K \ ABORT,${SSTATE_DIR},100M,1K \ ABORT,/tmp,10M,1K" PACKAGECONFIG_append_pn-qemu-native = " sdl" PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" CONF_VERSION = "1" #IMAGE_FEATURES_append = " package-management tools-sdk x11-base x11" IMAGE_FEATURES += "package-management" IMAGE_FEATURES += "tools-sdk" IMAGE_FEATURES += "x11-base" IMAGE_FEATURES += "x11" As you can see, I tried adding x11 both using IMAGE_FEATURES += as well as IMAGE_FEATURES_append (where I would then comment out the += lines) Why is x11 never getting added to the DISTRO_FEATURES? I also tried putting x11 in DISTRO_FEATURES and DISTRO_FEATURES_append. What is the correct thing here? I also installed yarn according to those instructions, which worked (it said it was successfully installed) however when I tried to use it I got an error about not finding gulp: # yarn watch yarn run v1.19.1 $ gulp watch --max_old_space_size=4095 /bin/sh: gulp: command not found error Command failed with exit code 127. I don't know anything about yarn. Is gulp another package I need to install, or should it be part of yarn? Thank you. -Aaron -----Original Message----- From: Ross Burton <ross.bur...@intel.com> Sent: Friday, November 1, 2019 12:52 PM To: Aaron Solochek <aaron.soloc...@sri.com>; yocto@yoctoproject.org Subject: Re: [yocto] visual studio code packages or building instructions? On 01/11/2019 16:35, Aaron Solochek wrote: > I would like to get visual studio code on my NXP i.MX8. If someone is > aware of a aarch64 rpm of it, that would be the easiest. > Alternatively, if anyone knows how to build it using bitbake, I can build it > myself. Well Microsoft only make x86 binaries available: https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcode.visualstudio.com%2F%23alt-downloads&data=01%7C01%7Caaron.solochek%40sri.com%7Ca9ecc8ecbf4e4aeb6bf208d75eebd148%7C40779d3379c44626b8bf140c4d5e9075%7C1&sdata=mSWDKRoSwEfy2SiGAgOdcKZvcrvofVPqriDnu5Pd3bI%3D&reserved=0 So you'll have to follow the instructions at https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvscode%2Fwiki%2FHow-to-Contribute%23build-and-run&data=01%7C01%7Caaron.solochek%40sri.com%7Ca9ecc8ecbf4e4aeb6bf208d75eebd148%7C40779d3379c44626b8bf140c4d5e9075%7C1&sdata=3WHuWNu9ngP%2Fbymit1UgnuBawO1b123F1LdwTuHot0U%3D&reserved=0 They use Yarn, so you'll have to package that first. Comments like https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fvscode%2Fissues%2F6442%23issuecomment-509605292&data=01%7C01%7Caaron.solochek%40sri.com%7Ca9ecc8ecbf4e4aeb6bf208d75eebd148%7C40779d3379c44626b8bf140c4d5e9075%7C1&sdata=F0XX9b%2FADWjPJbeis%2FgIlyRunHbb4zpj6Mw3ac1Cs%2Fw%3D&reserved=0 on the bug asking for RPi support isn't exactly encouraging though. Ross -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
