search

Schmavery / reprocessing

ReasonML graphics library inspired by Processing
https://schmavery.github.io/reprocessing/
MIT License
682 stars 24 forks source link

Can't run bytecode or native #56

Closed boyswan closed 6 years ago

boyswan commented 6 years ago

`❯ ./lib/bs/bytecode/indexhot.byte

dyld: Library not loaded: /Users/Jack/Desktop/regl/node_modules/sdl2/libSDL2-2.0.0.dylib Referenced from: /Users/Jack/Desktop/reprocessing-example/./lib/bs/bytecode/indexhot.byte Reason: image not found [1] 79641 abort ./lib/bs/bytecode/indexhot.byte`

same error for byte and native, not sure why it's pointing to a regl directory?

bsansouci commented 6 years ago

Could you give us a bit of context as to what you did to install and build?

This looks to me like you installed stuff in a folder called regl and then moved the node_modules into another project.

boyswan commented 6 years ago

cloned the reprocessing-example project and tried both yarn and npm (v4) install.

Seemed to be working a week or so ago, updated to High Sierra OSX so wondering if that has something to do with it. The regl directory is very odd, it doesn't even exist.

All the build scripts work fine, but running the start/start:native fail with above error

bsansouci commented 6 years ago

That's... super strange. Have you tried nuking node_modules and yarn.lock and re-installing?

Schmavery commented 6 years ago

Yeah this is super weird, we definitely want to make sure we can get this working for you asap. Just to cover our bases, I'm assuming your install would have gone like this: 

git clone https://github.com/bsansouci/reprocessing-example.git
cd reprocessing-example
npm install
npm run build
npm start

Assuming @bsansouci's advice doesn't work, can you tell us some more about your environment? Do you have opam installed? A global bs-platform? reason-cli? (None of these should be a problem, just trying to get an idea.)

boyswan commented 6 years ago

So I think I've figured it out, seems like a process didn't quit properly and was running in the background even when seemingly killed! I can replicate if I run npm start, then try npm start in another terminal whilst it's running. Thanks for your help, sorry for the slight false alarm!

Schmavery commented 6 years ago

Thanks for letting us know, @boyswan! Glad you got it sorted out. Feel free to open more issues if I can help with reprocessing in any way.