unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / Atom feed
* bug#25327: cargo build-system should be able to filter out target.cfg(windows) dependencies
@ 2017-01-02  0:46 ng0
  2020-12-18 19:56 ` zimoun
  0 siblings, 1 reply; 5+ messages in thread
From: ng0 @ 2017-01-02  0:46 UTC (permalink / raw)
  To: 25327

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.

-- 
♥Ⓐ  ng0
PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org

^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#25327: cargo build-system should be able to filter out target.cfg(windows) dependencies
  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
  2020-12-19 13:10   ` Hartmut Goebel
  0 siblings, 1 reply; 5+ messages in thread
From: zimoun @ 2020-12-18 19:56 UTC (permalink / raw)
  To: ng0, Hartmut Goebel, John Soo; +Cc: 25327

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




^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#25327: cargo build-system should be able to filter out target.cfg(windows) dependencies
  2020-12-18 19:56 ` zimoun
@ 2020-12-19 13:10   ` Hartmut Goebel
  2021-01-11 12:41     ` zimoun
  0 siblings, 1 reply; 5+ messages in thread
From: Hartmut Goebel @ 2020-12-19 13:10 UTC (permalink / raw)
  To: zimoun, ng0, John Soo; +Cc: 25327

Am 18.12.20 um 20:56 schrieb zimoun:
> Is it still relevant with the recent additions?

I just checked this with sequoia 0.20.0: The package "winapi" is still 
downloaded and compiled - even if obviously not used sicne on Linux.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |





^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#25327: cargo build-system should be able to filter out target.cfg(windows) dependencies
  2020-12-19 13:10   ` Hartmut Goebel
@ 2021-01-11 12:41     ` zimoun
  2021-01-11 13:33       ` John Soo
  0 siblings, 1 reply; 5+ messages in thread
From: zimoun @ 2021-01-11 12:41 UTC (permalink / raw)
  To: Hartmut Goebel; +Cc: ng0, 25327, John Soo

Hi Hartmut,

On Sat, 19 Dec 2020 at 14:10, Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
> Am 18.12.20 um 20:56 schrieb zimoun:
>> Is it still relevant with the recent additions?
>
> I just checked this with sequoia 0.20.0: The package "winapi" is still
> downloaded and compiled - even if obviously not used sicne on Linux.

Should the remove of this “winapi” happen at the build-system level or
at the package per package level?

Other said, are the Windows dependencies normalized by Cargo?

All the best,
simon






^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#25327: cargo build-system should be able to filter out target.cfg(windows) dependencies
  2021-01-11 12:41     ` zimoun
@ 2021-01-11 13:33       ` John Soo
  0 siblings, 0 replies; 5+ messages in thread
From: John Soo @ 2021-01-11 13:33 UTC (permalink / raw)
  To: zimoun; +Cc: Hartmut Goebel, ng0, 25327

[-- Attachment #1: Type: text/plain, Size: 185 bytes --]

     Hi zimoun,  

  
I think that the configuration phase will fail even if conditional compilation dependencies are missing.    It’s worth a shot though!
  

  
- John
     

[-- Attachment #2: Type: text/html, Size: 232 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-01-11 13:35 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2020-12-19 13:10   ` Hartmut Goebel
2021-01-11 12:41     ` zimoun
2021-01-11 13:33       ` John Soo

unofficial mirror of bug-guix@gnu.org 

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://yhetil.org/guix-bugs/0 guix-bugs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guix-bugs guix-bugs/ https://yhetil.org/guix-bugs \
		bug-guix@gnu.org
	public-inbox-index guix-bugs

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.gnu.guix.bugs
	nntp://news.gmane.io/gmane.comp.gnu.guix.bugs


AGPL code for this site: git clone http://ou63pmih66umazou.onion/public-inbox.git