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

Question about usage documentation #215

Open
fedor-rusak opened this issue Sep 24, 2019 · 3 comments
Open

Question about usage documentation #215

fedor-rusak opened this issue Sep 24, 2019 · 3 comments

Comments

@fedor-rusak
Copy link

fedor-rusak commented Sep 24, 2019

Context: I want (more like wish) to modify ggez to use rendy under the hood. And use this package later as a dependency for actual project.

Problem:t Made a simple example with rendy having different features for different OS'es. Example. But it fails on Win 10.

Question: How to integrate rendy in helper crate that would work on different Operationg Systems? Is there a documentation for such question?

Sorry if this is not intended use for Rendy package.

@zakarumych
Copy link
Member

The way you wrote Cargo.toml hits cargo own limitations - cargo will try to build dependency with accumulated features even if some are specified under [target.'cfg(<platform_flag>)'.dependencies]

Instead rendy should be buildable with any set of features on any platform. This is the case in branch dedicated to {open,web}gl backend support which should be merged soom™️ .

By the way @icefoxen (ggez author) has plans to power-up ggez with rendy, so you probably should collaborate with him on the matter.

@fedor-rusak
Copy link
Author

So correct me if I am wrong but intended usage of rendy crate is to create a project for ONE platform and specify only needed features.

I understand that limitations of cargo are beyond scope of Rendy.

Thank you for your response. I assume this integration info already documented and issue can be closed.

@zakarumych
Copy link
Member

intended usage of rendy crate is to create a project for ONE platform and specify only needed features.

Correction. No. Intended usage is to specify all features you need and build on all platforms. But currently required config-macro-magic isn't merged to master so you have to reexport backend features from your crate.

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

2 participants