From: "Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>
To: 69440@debbugs.gnu.org
Cc: "Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>
Subject: [bug#69440] [PATCH] gnu: Add compdb.
Date: Tue, 27 Feb 2024 23:17:35 +0100 [thread overview]
Message-ID: <PAXP251MB03484C3E7307C67EC6E2557AF3592@PAXP251MB0348.EURP251.PROD.OUTLOOK.COM> (raw)
* gnu/packages/build-tools.scm (compdb): New variable.
Change-Id: Ia221f21f38e4def239b82654c678fbe42b995878
---
gnu/packages/build-tools.scm | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/gnu/packages/build-tools.scm b/gnu/packages/build-tools.scm
index 15d88ded80..74e28f0e98 100644
--- a/gnu/packages/build-tools.scm
+++ b/gnu/packages/build-tools.scm
@@ -667,6 +667,29 @@ (define-public osc
be reached via direct API calls.")
(license license:gpl2+)))
+(define-public compdb
+ (package
+ (name "compdb")
+ (version "0.2.0")
+ (source
+ (origin
+ (method git-fetch)
+ (uri (git-reference
+ (url "https://github.com/Sarcasm/compdb")
+ (commit (string-append "v" version))))
+ (file-name (git-file-name name version))
+ (sha256
+ (base32 "0f4x0gm5n1mr87dx3gzn5da16a1qhd2y3kz22dl5xsd9pd720l4w"))))
+ (build-system pyproject-build-system)
+ (propagated-inputs (list python-configparser))
+ (home-page "https://github.com/Sarcasm/compdb")
+ (synopsis "Compilation database Swiss army knife")
+ (description
+ "@command{compdb} is a command line tool to manipulate compilation
+databases. It eases the usage of tooling in a codebase by spoon-feeding the
+right compilation options.")
+ (license license:expat)))
+
(define-public compiledb
(package
(name "compiledb")
base-commit: c99069e6295d41087ecfc70484f47ff73de5b2c0
--
2.41.0
next reply other threads:[~2024-02-27 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 22:17 Sergio Pastor Pérez [this message]
2024-03-29 12:33 ` bug#69440: [PATCH] gnu: Add compdb Nicolas Goaziou via Guix-patches via
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=PAXP251MB03484C3E7307C67EC6E2557AF3592@PAXP251MB0348.EURP251.PROD.OUTLOOK.COM \
--to=sergio.pastorperez@outlook.es \
--cc=69440@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.