Hi,
I was trying to build a linux image for the microchip SAMA7 board with the
dm-verity feature of the meta-security layer. But using this layer for
dm-verity causes a circular dependency error during build.
my *local.conf *changes:
*INITRAMFS_IMAGE_BUNDLE = "1"INITRAMFS_IMAGE =
I see, are you talking about ${MLPREFIX} variable? The target itself
compiles fine, all are 32-bit binaries in userspace. I have this issue only
for SDK.
On Tue, Sep 14, 2021 at 7:21 PM Khem Raj wrote:
>
>
> On 9/14/21 6:13 PM, Arun wrote:
> > The packages that SDK is
The packages that SDK is trying to build are userspace packages and they
haven't been ported for 64-bit. There are quite a few of them and short of
fixing 64-bit compile issues for all of them, I am trying to see if I can build
SDK without these packages built for. 64-bit. The SDK users will
Bumping this question...
Is there a way for me to disable building of 64-bit packages when building SDK
with a multilib config? I have no use for 64-bit userspace package artifacts.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54720):
e: I am building SDK via this command without lib32- prefix for target,
following details from this commit message
<http://git.openembedded.org/openembedded-core/commit/?id=77144bc808be02deb3351c9c1bf5b4f2b8c3a6ec>
stating that lib32- prefix is not required
*MACHINE= bitbake -c po
to the target
add_subdirectory(src)
that has one CMakeList.txt.
# Set minimum required CMake version
cmake_minimum_required(VERSION 3.5.1)
# Name the project
project (sources)
add_subdirectory(calsimple)
add_subdirectory(calibinfo)
add_subdirectory(writer)
add_subdirectory(converter)
add_subdirectory(serv
