Open ErichDonGubler opened 2 years ago
Thanks for this info! I pointed to your notes here in the README until I make more progress on this. I would also not be surprised if configuring LLVM (also removed with --no-default-features
) was different on Windows.
I'll keep this issue open for now as I should probably get around to testing frawk on Windows. The fact that it builds is a good sign that I may not have a ton to fix on this front.
As for having better defaults, I think the standard move here is to sidestep platform-specific configurations entirely by publishing pre-built binaries or packages on language package registries. Both of those are on the roadmap, but LLVM support remains a troublesome blocker on that front (see #53 #33)
The problem seems to be that sh
is not valid on Windows - I guess this should be reported to the tikv-jemalloc-sys
maintainer(s).
To my surprise, this crate compiles with
cargo build --no-default-features
on Windows 10! Woot,awk
on Windows! :DAttempting to compile with the
use_jemalloc
againstx86_64-pc-windows-msvc
(the most common Windows target AFAIK), one gets a compile error of the form:Basically,
jemalloc
isn't something we should expect to compile on Windows right now. I think this is unfortunate, given that it's currently impossible to define a feature that only isdefault
for a specific platform.