forestdb source files referenced incorrectly by xcode? about cbforest HOT 4 CLOSED

Are you checking out and building CBForest on its own, not as part of Couchbase Lite? It should work, but I haven't tried it in a while.

From your screenshot, the source paths in the project look wrong — it has .../vendor/CBForest/blockcache.cc, which is missing the last 3 directories in the path, vendor/forestdb/src. If so, I have no idea why the project would build for me and not you…

from cbforest.

Are you checking out and building CBForest on its own, not as part of Couchbase Lite? It should work, but I haven't tried it in a while.

I've been using Couchbase-Lite as a submodule in my project repo for... a while. Since the beginning of the year, I guess. All I did was switch from master to forestdb and pull, and git submodule update --init --recursive from the CBL root. I got appropriate messages, git log et al. seems correct and up to date, etc.

I encountered the first error when trying to build my entire project (which links to the CBL Mac framework). I thought, okay, maybe my header search paths are off or something, so I just tried building CBForest itself and got the same error, so I poked into the directory and found the red file names.

From your screenshot, the source paths in the project look wrong — it has .../vendor/CBForest/blockcache.cc, which is missing the last 3 directories in the path, vendor/forestdb/src. If so, I have no idea why the project would build for me and not you…

I can't imagine why this would affect CBForest, but I keep my Xcode groups/items mirroring my FS folder/file hierarchy, and all "Location"s are set to "relative to group". Again, I can't imagine why this would cause any issue, and it hasn't with CBL in the past, but perhaps there's some side effect to this that I don't know about.

from cbforest.

Well, here's something weird:

The group's path seems set correctly...

and yet the file contained within the group, which seems also to be set correctly, generates an incorrect path...

so this kind of looks like an Xcode bug to me.

from cbforest.

Deleted derived files, etc, closed and relaunched Xcode... and everything's fine :-/ I guess it was Xcode.

Nevermind! :-D

from cbforest.