-
Notifications
You must be signed in to change notification settings - Fork 68
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
'json/reader.h' file not found #60
Comments
Hey David, |
Removing the reference to the include/libs/json folder seems to have solved it. |
Great! I'll add a note to the readme. |
Hi, I'm having similar issues, and I would like both add-ons (ofxLibwebsockets & ofxJSON) to be using their own version of JsonCpp. For example, the version of JsonCpp included in ofxLibwebsockets' repo has been modified. Would it make sense to change the name of the Cheers. |
I'm getting the same problem. It seems like the project structure has changed since @davivid 's advice above? I tried deleting the libs/jsoncpp folder and removing the header search paths but then ofxlibwebsockets complains about not being able to find jsoncpp at all. Any ideas? |
@aferriss are you using ofxJson? and what version of OF? |
@robotconscience yes ofxJson and ofxLibwebsockets in tandem was my attempt, with 0.9.2. I ended up doing my parsing on the server side before having it sent to oF so I got it sorted! Seems like it will just be easiest to wait for 0.10 |
Hi, I too just ran into this with a 0.9.7 project with both ofxJSON and ofxLibwebsockets. I also see this #include lands within a !defined(JSON_IS_AMALGATED) section. Any recommendations on how I should build this? |
Hi @visualist. I haven't tried with 0.9.7 yet, but with older 0.9.x releases you should be able to remove the libs/jsoncpp files from one of the addons (I'm not sure if it matters whether you remove them from ofxJSON or ofxLibwebsockets) in your project to get around these errors. |
Using ofxLibwebsockets & ofxJSON in the same project (of_v0.8.4_osx_release ) seems to cause the error above. Is there a solution for this?
Thanks,
David
The text was updated successfully, but these errors were encountered: