From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: phosphor-dbus-interfaces transitioning to meson
Date: Sat, 5 Sep 2020 12:04:07 -0500 [thread overview]
Message-ID: <20200905170407.GA6152@heinlein> (raw)
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
Hello,
I just merged a patchset into phosphor-dbus-interfaces which starts a
transition from autotools to meson. Right now you can build PDI with
either autotools or meson and it should be equivalent. With meson, you
should also be able to use PDI as a subproject. I will begin transitioning
the bitbake recipes to use the meson as well and then after that I will
clean up the autotools support.
There is one change for contributors to PDI because meson does not have
the same capabilities for generating code that our previous autotools
structure allowed. When an sdbus++ YAML file is added or removed, there
is now an additional step to get that YAML file included into the meson
build process. Within the `gen` subdirectory is a script
`regenerate-meson` which will identify all the YAML files present and
update the `meson.build` files to include (or remove) the YAML file.
This new process is documented at:
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/README.md#building
For the next few weeks, I will try to pay closer attention to any new
YAML file in the repository and confirm that the meson.build files have
been updated appropriately. Please reach out to me if you encounter any
issues.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-09-05 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 17:04 Patrick Williams [this message]
2020-09-16 18:57 ` phosphor-dbus-interfaces transitioning to meson Patrick Williams
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=20200905170407.GA6152@heinlein \
--to=patrick@stwcx.xyz \
--cc=openbmc@lists.ozlabs.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.