Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no_std support #91

Open
jlxip opened this issue Mar 22, 2023 · 2 comments
Open

no_std support #91

jlxip opened this issue Mar 22, 2023 · 2 comments

Comments

@jlxip
Copy link

jlxip commented Mar 22, 2023

This is an issue to propose the idea of considering adding no_std support. include_str! and include_bytes! both have it, so it would make sense for this too.

@gwen-lg
Copy link

gwen-lg commented Jun 18, 2024

I have take a look, and it's seem not possible.
include_dir use the Path struct and fs module witch can't be avoided.

include_str! seems to use compiler built-in, so it's seems not possible to copy it in the crate.

@doinkythederp
Copy link

I've implemented no_std support in a fork by using the unix_path crate. However, this is a breaking change. doinkythederp@030a2cd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants