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

simplify build #11

Merged
merged 1 commit into from
Dec 22, 2023
Merged

simplify build #11

merged 1 commit into from
Dec 22, 2023

Conversation

pepyakin
Copy link
Contributor

Remove build.rs for just a standard relative path include.

build scripts are an advanced feature. It just happened that this
particular crate did not play nice with a non-cargo build system.

Likely it would be possible to fix it locally, but I actually don't
see any reason for this crate to have a build.rs

I checked it locally and it seems to produce exactly the same results.

LMK if I am missing something.

Remove build.rs for just a standard relative path include.
Copy link
Owner

@ggwpez ggwpez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it was needed to find the README for cargo publish since that builds the crate on its own outside of the workspace.
Anyway, its probably better to write a small publish.sh that shuffles the files prio to publishing than using a build.rs - i dont like it either 😆

@ggwpez
Copy link
Owner

ggwpez commented Dec 22, 2023

Thanks Sergei!

@ggwpez ggwpez merged commit dcc2ce1 into ggwpez:master Dec 22, 2023
1 check passed
@ggwpez ggwpez mentioned this pull request Dec 22, 2023
ggwpez added a commit that referenced this pull request Dec 22, 2023
Changes:
- Add MAINTAIN.md to explain publishing after #11 
- Update deps
- Set version to 1.0.1
- Correctly set the workspace.readme key

---------

Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
@pepyakin
Copy link
Contributor Author

Do you mind making a release? Would be really helpful!

@pepyakin
Copy link
Contributor Author

Oh sorry, I missed your message above. I wonder if a symbolic link would help.

Check out #14 . GH renders it as a file but it's actually a symbolic link (created by ln -s). It seems that the file is packaged properly, but I also saw your other changes now and they also make sense.

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

Successfully merging this pull request may close these issues.

2 participants