Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Fix Absolute Paths in Xcode #261
Conversation
azmfaridee
added the
Bugs
label
Aug 4, 2016
mothur-westcott
was assigned
by azmfaridee
Aug 4, 2016
|
Setting it to works for files like ... path = source/subsample.cpp; sourceTree = "group"; }; where you only have one directory layer. For source files with multiple directory levels when I set it to relative to group, it's causing issues for you. It needs to be set to relative to project. ... path = source/commands/makecontigscommand.cpp; sourceTree = SOURCE_ROOT; }; The chimera.vsearch command was set relative to group in Xcode, but needed to be set relative to project to resolve the absolute path issue. Thanks for bringing this back up. New files default to relative to group and I missed it. |
|
Branch 1.39.0 has the paths fixed. |
azmfaridee commentedAug 4, 2016
•
edited
While trying to solve the RF issue, I came across this one.
A lot of files in the project still have absolute paths like this:
/Users/sarahwestcott/Desktop/mothur/source/commands/chimeravsearchcommand.cppso when I tried compiling it in a number of Macs I got the following error in Xcode 7.3.1:I replaced the
<absolute>references with<group>and it solved the problems (stack overflow link for a similar issue http://stackoverflow.com/questions/11614919/file-in-the-project-not-seen-by-xcode-after-git-pull)Please take a look and see if this branch properly compiles in your setup.
Detailed Log