From: "Alper Ak" <alperyasinak1@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] tk: add INCLUDEDIR for tcl9.0
Date: Mon, 30 Jun 2025 11:05:16 -0700 [thread overview]
Message-ID: <25294.1751306716982813583@lists.openembedded.org> (raw)
In-Reply-To: <20250630151655.3505250-1-f_l_k@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
Hi Markus,
I recently sent a patch similar to yours. Yes, this really solves the problem, but there seem to be two things to think about:
1) if tcl and tk can be upgraded independently (tcl recipe is in poky, tk is in meta-oe), this may cause failure if tcl is upgraded without upgrading tk. We are telling him to look at “-I${STAGING_INCDIR}/tcl${VER}” but when tcl is upgraded, if tk isn't upgraded to the same version, it will probably fail.
2) tk uses pkgconfig that's the way for tcl to tell tk where to find its headers. When I look at the compile logs, it really tells but there is a situation like this in include path:
-I.../recipe-sysroot/usr/include/sources/tcl9.0.1/generic
Somehow, the "sources" is added to the path from somewhere, and it must be /usr/include/tcl9.0.1/generic
I know that the "tcl.h" file is available in both ../recipe-sysroot/usr/include/tcl9.0/ and ../recipe-sysroot/usr/include/tcl9.0.1/generic/ but considering the path provided to the compiler as an include, we should use the generic one.
I have been sick for a while and haven't had much time to look at the situation with pkgconfig. I wanted to write to see if it might help you.
[-- Attachment #2: Type: text/html, Size: 1331 bytes --]
next prev parent reply other threads:[~2025-06-30 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 15:16 [meta-oe][PATCH] tk: add INCLUDEDIR for tcl9.0 Markus Volk
2025-06-30 18:05 ` Alper Ak [this message]
2025-06-30 20:47 ` [oe] " Markus Volk
[not found] ` <184DED0D44CD195B.28277@lists.openembedded.org>
2025-07-01 10:29 ` Markus Volk
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=25294.1751306716982813583@lists.openembedded.org \
--to=alperyasinak1@gmail.com \
--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.