consider making the wrapper independent of nimterop and publish the actual generated wrapper #1
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jyapayne/nim-glfw#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Its an issue very specific tbh, but i just have problems installing nimterop, and i cant use the wrapper, however, if im not mistaken, nimterop generated wrappers no longer need the library to work, so uploading the generated wrapper directly would be very useful.
There are a couple problems with generating the wrapper and storing it in Git.
The first is that the wrapper generated is platform dependent (since nimterop runs a preprocessor on the C headers, any platform independent code gets lost). I would need to generate the wrapper for each platform (may not matter in glfw's case, since there doesn't appear to be much in the way of that from just a quick scan through)
The second is that it can easily get out of date if the generation isn't maintained. Ideally it should be automated.
That being said, I've created a file called
src/glfw/glfw_standalone.nimwith a warning at the top and some instructions. Let me know if it works for you. You'll probably have to clone the repo manually since nimble will still try to install nimterop.thanks for the information, my nimterop problems are not related to this package though, so until i can fix that, i wont be able to use the wrapper thanks for the answer anyway