Github messages for voidlinux
 help / color / mirror / Atom feed
From: Owenlaw222 <Owenlaw222@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] dbus pkg-config file sets incorrect include directory
Date: Thu, 15 Dec 2022 04:47:29 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41102@inbox.vuxu.org> (raw)

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

New issue by Owenlaw222 on void-packages repository

https://github.com/void-linux/void-packages/issues/41102

Description:
### Is this a new report?

Yes

### System Info

Void 6.0.12_1 x86_64 AuthenticAMD uptodate FFFFFFF

### Package(s) Affected

dbus-devel-1.14.4_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

When calling `pkg_check_modules(dbus REQUIRED "dbus-1")` in a cmake file the `dbus_INCLUDE_DIRS` variable should be set to `/usr/include/dbus-1.0/dbus` as that is where the headers are located.

### Actual behaviour

When calling `pkg_check_modules(dbus REQUIRED "dbus-1")` the include directory variable is instead set to the path `/usr/include/dbus-1.0/usr/lib64/dbus-1.0/include` which does not exist.

### Steps to reproduce

1. Call `pkg_check_modules(dbus REQUIRED "dbus-1")` in a cmake file
2. Call `message(DEBUG ${dbus_INCLUDE_DIRS})` following the previous call
3. Note that the path which is returned is not valid

             reply	other threads:[~2022-12-15  3:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15  3:47 Owenlaw222 [this message]
2022-12-15  7:12 ` sgn
2022-12-15  7:12 ` [ISSUE] [CLOSED] " sgn

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41102@inbox.vuxu.org \
    --to=owenlaw222@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 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 NNTP newsgroup(s).