From: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
To: git@vger.kernel.org
Cc: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Subject: [GSoC PATCH 2/2] MyFirstContribution: add walken.c to meson.build
Date: Thu, 29 May 2025 16:20:36 -0300 [thread overview]
Message-ID: <20250529192036.75408-3-lucasseikioshiro@gmail.com> (raw)
In-Reply-To: <20250529192036.75408-1-lucasseikioshiro@gmail.com>
Instruct in the documentation to also add an entry in meson.build for
builtin/walken.c, as currently both Meson and Make are supported.
Signed-off-by: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
---
Documentation/MyFirstObjectWalk.adoc | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/Documentation/MyFirstObjectWalk.adoc b/Documentation/MyFirstObjectWalk.adoc
index 29d26abb47..3b66e48dd9 100644
--- a/Documentation/MyFirstObjectWalk.adoc
+++ b/Documentation/MyFirstObjectWalk.adoc
@@ -96,12 +96,19 @@ maintaining alphabetical ordering:
{ "walken", cmd_walken, RUN_SETUP },
----
-Add it to the `Makefile` near the line for `builtin/worktree.o`:
+Add an entry for the new command in the file of our two build systems (Make
+and Meson) before the entry for `worktree`:
+- In the `Makefile`:
----
BUILTIN_OBJS += builtin/walken.o
----
+- In the `meson.build` file:
+----
+ 'builtin/walken.c',
+----
+
Build and test out your command, without forgetting to ensure the `DEVELOPER`
flag is set, and with `GIT_TRACE` enabled so the debug output can be seen:
--
2.39.5 (Apple Git-154)
next prev parent reply other threads:[~2025-05-29 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 19:20 [GSoC PATCH 0/2] Update MyFirstObjectWalk with struct repository and meson Lucas Seiki Oshiro
2025-05-29 19:20 ` [GSoC PATCH 1/2] MyFirstContribution: use struct repository in examples Lucas Seiki Oshiro
2025-05-29 19:57 ` Karthik Nayak
2025-05-29 19:20 ` Lucas Seiki Oshiro [this message]
2025-05-29 20:02 ` [GSoC PATCH 2/2] MyFirstContribution: add walken.c to meson.build Karthik Nayak
2025-05-30 8:00 ` Patrick Steinhardt
2025-05-29 20:06 ` [GSoC PATCH 0/2] Update MyFirstObjectWalk with struct repository and meson Karthik Nayak
2025-06-02 20:50 ` [GSoC PATCH v2 0/2] MyFirstObjectWalk: update " Lucas Seiki Oshiro
2025-06-02 20:50 ` [GSoC PATCH v2 1/2] MyFirstContribution: use struct repository in examples Lucas Seiki Oshiro
2025-06-02 20:50 ` [GSoC PATCH v2 2/2] MyFirstContribution: add walken.c to meson.build Lucas Seiki Oshiro
2025-06-03 6:08 ` [GSoC PATCH v2 0/2] MyFirstObjectWalk: update with struct repository and meson Patrick Steinhardt
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=20250529192036.75408-3-lucasseikioshiro@gmail.com \
--to=lucasseikioshiro@gmail.com \
--cc=git@vger.kernel.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).