From: mtvrsh <mtvrsh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] rust: build rust-analyzer-proc-macro-srv
Date: Thu, 14 Mar 2024 00:15:15 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49282@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
There is a new pull request by mtvrsh against master on the void-packages repository
https://github.com/mtvrsh/void-packages rust-proc-macro-srv
https://github.com/void-linux/void-packages/pull/49282
rust: build rust-analyzer-proc-macro-srv
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
Without it rust-analyzer doesn't expand macros.
A patch file from https://github.com/void-linux/void-packages/pull/49282.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rust-proc-macro-srv-49282.patch --]
[-- Type: text/x-diff, Size: 1020 bytes --]
From dccc61839c0805ff11cbfc57cbf1805f635865a6 Mon Sep 17 00:00:00 2001
From: mtvrs <mtvrs@tuta.io>
Date: Wed, 13 Mar 2024 23:29:20 +0100
Subject: [PATCH] rust: build rust-analyzer-proc-macro-srv
---
srcpkgs/rust/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/rust/template b/srcpkgs/rust/template
index 2ce75af7b3a9cb..b93271e97ded86 100644
--- a/srcpkgs/rust/template
+++ b/srcpkgs/rust/template
@@ -9,7 +9,7 @@
#
pkgname=rust
version=1.76.0
-revision=1
+revision=2
hostmakedepends="curl pkg-config python3 tar cargo-bootstrap"
makedepends="libffi-devel ncurses-devel libxml2-devel zlib-devel llvm17-devel"
depends="rust-std gcc"
@@ -128,7 +128,7 @@ do_configure() {
--release-description="Void Linux" \
--llvm-libunwind=no \
--llvm-config=/usr/bin/llvm-config \
- --tools=clippy,rustdoc,rustfmt \
+ --tools=clippy,rustdoc,rustfmt,rust-analyzer-proc-macro-srv \
--set="rust.optimize=true" \
--set="rust.debug=false" \
--set="rust.codegen-units=1" \
next reply other threads:[~2024-03-13 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 23:15 mtvrsh [this message]
2024-03-14 13:05 ` leahneukirchen
2024-03-15 16:07 ` [PR PATCH] [Merged]: " leahneukirchen
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-49282@inbox.vuxu.org \
--to=mtvrsh@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).