Cool, plans on automating this to nimble.directory?
I'm new to nim and am getting `could not load: libraylib.dll` as well. I've got
it in the same directory as my .exe. When I clone the repo to my other windows
computer it runs fine. Can anyone point this dummy in the right direction?
Oh! I was under the impression that raylib wasn't distributed in dll, for some
reason. Thanks. Got it working now.
Pick your poison:
[https://github.com/raysan5/raylib/releases/tag/3.0.0](https://github.com/raysan5/raylib/releases/tag/3.0.0)
Doesn't seem to work for me, though. I just tried compiling the samples and it
says `could not load: libraylib.dll` when I run the executables. :(
While I always advocate for lib wrappings to be as faithful to the originals as
possible, to make it easy for people to follow their documentations, in this
case I'll have to agree that at least proc names should change to lower case
first letter (which doesn't make it harder to follow the docs
This is cool! I gave it a spin and it Just Worked™ with the latest raylib dll,
very painless experience :)
Some thoughts:
As neat as this generator page is, I'd rather have a regularly updated nimble
package. But hey, you've already done the hard part! Maintaining such a package
would be a
Sorry for rather long delay: added 5 new examples from text and models
categories. Project != dead.
I guess, it't time to decide if heavier samples is needed - I hate adding aux
files to this repository, yet demand is demand.
Shameless plug: This can help updating the naming style:
[https://github.com/FedericoCeratto/nimfmt](https://github.com/FedericoCeratto/nimfmt)
Oh I'm aware there is a tradeoff here and everybody's time is finite. I only
tried to get the point across **why** some people, me included, prefer code
that uses Nim's naming conventions.
Well, right, but... Look, there are 90+ examples provided for original raylib,
yet almost none of them was converted to Nim. I started translating some more
basic stuff today and I'm completely, absolutely, positively against additional
procname fixing.
Samples conversion is already errartic
> Except... why ? It will only make it's harder to translate existing code.
Because many Nim programmers prefer to read Nim code, not some unidiomatic code
that constantly reminds them of the fact the source code was ported over from
some other language. Translations are better if one put some
rlgl module support added.
Yes, of course. Except... why ? It will only make it's harder to translate
existing code.
This is awesome, many thanks! Can you convert to Nim's naming convention for
function names?
I will even star this. Seriously.
I'll add some more wood to the fire:
[https://github.com/oswjk/foolib](https://github.com/oswjk/foolib). I did that
just as an experiment, didn't know what to name it though. It combines raylib +
Dear ImGui. The thing is a bit of a hack. Raylib binding was generated with
nimterop and Dear
Suggestion: now create a virus which will spread around the world and install
everywhere a fully automated service to convert and deliver latest possible
raylib headers, why not? Why your 4 previous wrapping attempts failed?
Mine ? Good god, no !
Previous 4 attempts were:
*
[https://github.com/Skrylar/raylib-nim](https://github.com/Skrylar/raylib-nim)
*
[https://gitlab.com/define-private-public/raylib-Nim](https://gitlab.com/define-private-public/raylib-Nim)
*
So, I did something strange again. This time it's fully automated webservice to
convert and deliver latest possible _raylib_ headers for modern Nim users:
[https://github.com/Guevara-chan/Raylib-Forever](https://github.com/Guevara-chan/Raylib-Forever)
While it's mostly a proof-of-concept so far
20 matches
Mail list logo
