* Generating SPDX documents without actually building anything
@ 2024-05-08 11:59 Sebastian Schuberth
2024-05-08 12:13 ` [yocto] " Alexander Kanavin
2024-05-08 12:53 ` Richard Purdie
0 siblings, 2 replies; 3+ messages in thread
From: Sebastian Schuberth @ 2024-05-08 11:59 UTC (permalink / raw
To: yocto
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
Hi all,
to start with a disclaimer, I'm a total noob when it comes to Open Embedded
/ Embedded Linux / Yocto / BitBake stuff. That said, I'm in need of
creating SPDX documents for Yocto projects in the context of [1]. I'm
already quite far in that I work with Poky and programmatically run
something like
bitbake -r
/home/sebastian/Development/GitHub/doubleopen-project/ort/plugins/package-managers/bitbake/src/main/resources/spdx.conf
-c create_spdx xmlto
However, I continuously run into various build problems on my Fedora 40
machine (one of which has been recently addressed by [2]), let alone the
time it takes to build something from scratch, even something as small as
e.g. the "xmlto" target. So, ideally, I would be able to create SPDX
documents without really building any binaries at all. I probably want all
the source download and patching to happen, in order to archive the patched
code that goes into the binaries, but skip the actual compiler / linker
invocations to save time, and just create the SPDX documents.
Is something like this already possible somehow, maybe by setting from
compiler / linker variables to fake scripts that just do nothing?
Thanks for any insights!
[1]: https://github.com/oss-review-toolkit/ort/issues/722
[2]:
https://github.com/openembedded/bitbake/commit/f10e630fd7561746d835a4378e8777e78f56e44a
--
Sebastian Schuberth
[-- Attachment #2: Type: text/html, Size: 3196 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [yocto] Generating SPDX documents without actually building anything
2024-05-08 11:59 Generating SPDX documents without actually building anything Sebastian Schuberth
@ 2024-05-08 12:13 ` Alexander Kanavin
2024-05-08 12:53 ` Richard Purdie
1 sibling, 0 replies; 3+ messages in thread
From: Alexander Kanavin @ 2024-05-08 12:13 UTC (permalink / raw
To: yocto, sschuberth
I'm not sure I understand how this would even be possible? You can't
generate SPDX until you have the binary artefacts and they've been
split into packages as far as I understand. The spdx code in yocto
explicitly establishes that relation between tasks.
Alex
On Wed, 8 May 2024 at 13:59, Sebastian Schuberth via
lists.yoctoproject.org <sschuberth=gmail.com@lists.yoctoproject.org>
wrote:
>
> Hi all,
>
> to start with a disclaimer, I'm a total noob when it comes to Open Embedded / Embedded Linux / Yocto / BitBake stuff. That said, I'm in need of creating SPDX documents for Yocto projects in the context of [1]. I'm already quite far in that I work with Poky and programmatically run something like
>
> bitbake -r /home/sebastian/Development/GitHub/doubleopen-project/ort/plugins/package-managers/bitbake/src/main/resources/spdx.conf -c create_spdx xmlto
>
> However, I continuously run into various build problems on my Fedora 40 machine (one of which has been recently addressed by [2]), let alone the time it takes to build something from scratch, even something as small as e.g. the "xmlto" target. So, ideally, I would be able to create SPDX documents without really building any binaries at all. I probably want all the source download and patching to happen, in order to archive the patched code that goes into the binaries, but skip the actual compiler / linker invocations to save time, and just create the SPDX documents.
>
> Is something like this already possible somehow, maybe by setting from compiler / linker variables to fake scripts that just do nothing?
>
> Thanks for any insights!
>
> [1]: https://github.com/oss-review-toolkit/ort/issues/722
> [2]: https://github.com/openembedded/bitbake/commit/f10e630fd7561746d835a4378e8777e78f56e44a
>
> --
> Sebastian Schuberth
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#63052): https://lists.yoctoproject.org/g/yocto/message/63052
> Mute This Topic: https://lists.yoctoproject.org/mt/105979197/1686489
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [yocto] Generating SPDX documents without actually building anything
2024-05-08 11:59 Generating SPDX documents without actually building anything Sebastian Schuberth
2024-05-08 12:13 ` [yocto] " Alexander Kanavin
@ 2024-05-08 12:53 ` Richard Purdie
1 sibling, 0 replies; 3+ messages in thread
From: Richard Purdie @ 2024-05-08 12:53 UTC (permalink / raw
To: yocto, sschuberth
On Wed, 2024-05-08 at 13:59 +0200, Sebastian Schuberth via
lists.yoctoproject.org wrote:
> Hi all,
>
> to start with a disclaimer, I'm a total noob when it comes to Open
> Embedded / Embedded Linux / Yocto / BitBake stuff. That said, I'm in
> need of creating SPDX documents for Yocto projects in the context of
> [1]. I'm already quite far in that I work with Poky and
> programmatically run something like
>
> bitbake -r /home/sebastian/Development/GitHub/doubleopen-
> project/ort/plugins/package-
> managers/bitbake/src/main/resources/spdx.conf -c create_spdx xmlto
>
> However, I continuously run into various build problems on my Fedora
> 40 machine (one of which has been recently addressed by [2]), let
> alone the time it takes to build something from scratch, even
> something as small as e.g. the "xmlto" target. So, ideally, I would
> be able to create SPDX documents without really building any binaries
> at all. I probably want all the source download and patching to
> happen, in order to archive the patched code that goes into the
> binaries, but skip the actual compiler / linker invocations to save
> time, and just create the SPDX documents.
>
> Is something like this already possible somehow, maybe by setting
> from compiler / linker variables to fake scripts that just do
> nothing?
The SPDX generated information includes information about the generated
binaries, the dependencies between them and also traces license headers
used by a given binary through the binary debug information.
Whilst it is true you could generate a simpler SPDX document without
compiling anything, that isn't how our SPDX generation currently works,
it includes a lot more information and some of that is from the
binaries.
You could create a different simpler spdx like class that could do what
you describe but that isn't what we have today. We went for the version
with all the information.
Cheers,
Richard
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-05-08 12:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-05-08 11:59 Generating SPDX documents without actually building anything Sebastian Schuberth
2024-05-08 12:13 ` [yocto] " Alexander Kanavin
2024-05-08 12:53 ` Richard Purdie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).