Fails to build without modification on OSX (AFAIK) about yajl

[mikefullerton]

Also, please let me know if my description of the problem is confusing or needs elaboration.

thanks

[winterweird]

I was actually going to create a new issue here if I didn't see something similar. As an additional note, I'd like to add that the build fails just from having "yajl/yajl_common.h" in the relative path from the source file. That is not ideal. It's easily circumvented by adding a -I. option to the compile flags (GCC at least), but I really think it should work out of the box. As such, I'd actually recommend to modify the includes to use quotes instead of angle brackets. The only difference it makes is that the preprocessor looks for a "yajl/yajl_common.h" in the relative path first before going through everything else. This would also be more consistent with how yajl_tree.h is included in the example program.

Personally I don't consider the folder structure YAJL expects as a problem. In one of my normal projects, even this little peculiarity wouldn't be a problem, since I tend to put everything under include/ and have a compiler flag for searching that folder. There wouldn't be a problem putting YAJL-related headers in a folder named "yajl". The only reason I discovered this problem was from adapting another person's project and not wanting to refactor too much and/or wanting to be consistent. However, in the case that "yajl/yajl_common.h" is in the relative path to the source file, you wouldn't expect it to flat out error, so I'm in favor of the way of the double quotes.

Best regards! (Also, I'm not really expecting a comment on an issue from 2011 to have an impact, but I wanted to put this out there.)