All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] doxygen: upgrade 1.17.0 -> 1.18.0
Date: Sun, 30 Aug 2026 03:50:31 -0700	[thread overview]
Message-ID: <2925873.1788087031374594528@lists.openembedded.org> (raw)
In-Reply-To: <CAGAhMBw=XgtZ5cQ0wpWj7ySiEZEtLhAVrbUYjGOx=ALPcJyAtQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 875 bytes --]

Hi Robb,

the buildpath issue is present on my system too. The generated files show:

/* WARNING: This file is generated!
* Do not edit this file, but edit /home/jaipaul/.../workspace/sources/doxygen/src/config.xml instead and run
* python configgen.py -maph /home/jaipaul/.../workspace/sources/doxygen/src/config.xml to regenerate this file!
*/

All three files — configvalues.h, configvalues.cpp, and configoptions.cpp — have the build path included.

The reason I missed it is that I used devtool upgrade and devtool build to build the recipe. devtool build only runs do_populate_sysroot and do_packagedata by default (hardcoded in scripts/lib/devtool/build.py),
so do_package_qa never executed.
A normal bitbake doxygen would have triggered do_build which depends on do_package_qa, catching the error.

So, your patch is needed .

Regards,
Jaipaul

[-- Attachment #2: Type: text/html, Size: 1148 bytes --]

      reply	other threads:[~2026-08-30 10:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 12:20 [PATCH] doxygen: upgrade 1.17.0 -> 1.18.0 Jaipaul Cheernam
2026-08-29 20:19 ` [oe] " Rob Woolley
2026-08-30  7:07   ` Jaipaul Cheernam
2026-08-30  9:39     ` [oe] " Rob Woolley
2026-08-30 10:50       ` Jaipaul Cheernam [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2925873.1788087031374594528@lists.openembedded.org \
    --to=jaipaul.cheernam@est.tech \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.