From: zimoun <zimon.toutoune@gmail.com>
To: ng0 <ng0@libertad.pw>,
Hartmut Goebel <h.goebel@crazy-compilers.com>,
John Soo <jsoo1@asu.edu>
Cc: 25327@debbugs.gnu.org
Subject: bug#25327: cargo build-system should be able to filter out target.cfg(windows) dependencies
Date: Fri, 18 Dec 2020 20:56:37 +0100 [thread overview]
Message-ID: <86pn36vqfe.fsf@gmail.com> (raw)
In-Reply-To: <87zijathke.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (ng0@libertad.pw's message of "Mon, 02 Jan 2017 00:46:09 +0000")
Hi,
On Mon, 02 Jan 2017 at 00:46, ng0 <ng0@libertad.pw> wrote:
> The cargo build-system should be able to filter out Windows
> dependencies.
> Ignore blocks with this in Cargo.toml files:
> [target.'cfg(windows)'.dependencies]
>
> until the next [ ] starts.
>
> I also found that most *32-sys packages (currently ALL *32-sys
> I've seen) are windows specific.
> As the build system is simple enough to not complain, you just
> have to learn about this while doing the work.
This bug is really old and the story about cargo has a bit evolved. Is
it still relevant with the recent additions?
If no, feel free to close it. And without more comment, I will close it
after the usual 2 weeks delay.
All the best,
simon
next prev parent reply other threads:[~2020-12-18 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 0:46 bug#25327: cargo build-system should be able to filter out target.cfg(windows) dependencies ng0
2020-12-18 19:56 ` zimoun [this message]
2020-12-19 13:10 ` Hartmut Goebel
2021-01-11 12:41 ` zimoun
2021-01-11 13:33 ` John Soo
2022-03-24 17:18 ` bug#25327: windows-related dependencies in crates Nicolas Graves via Bug reports for GNU Guix
2022-03-24 19:10 ` Maxime Devos
2022-10-08 14:15 ` bug#25327: cargo build-system should be able to filter out target.cfg(windows) dependencies zimoun
2022-10-08 16:03 ` Maxime Devos
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86pn36vqfe.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=25327@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.com \
--cc=jsoo1@asu.edu \
--cc=ng0@libertad.pw \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).