Skip to content
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

Use an absolute path to identify the modulemap. #518

Merged
merged 1 commit into from
May 25, 2015

Conversation

bjhomer
Copy link
Contributor

@bjhomer bjhomer commented May 22, 2015

In some cases when adding CocoaLumberjack as a submodule, Xcode can get confused and attempts to find the modulemap file in the wrong directory (e.g. Mobile/Lumberjack/CocoaLumberjack.modulemap, which does not exist). I'm not sure why happens or in exactly which situations, but using an absolute path (via $PROJECT_DIR) makes our intention more explicit and avoids this problem.

In some cases when adding CocoaLumberjack as a submodule, Xcode can get confused and attempts to find the modulemap file in the wrong directory (e.g. `Lumberjack/Mobile/CocoaLumberjack.modulemap`). I'm not sure why this happens, but using an absolute path (via `$PROJECT_DIR`) makes our intention more explicit and avoids this problem.
@bjhomer
Copy link
Contributor Author

bjhomer commented May 22, 2015

Hm. It appears that some Travis CI tests failed, but I don't see how those failures could be related to the changes in this commit. Is the master branch passing its tests?

@rivera-ernesto
Copy link
Member

Yes, they are nor related. Unit Tests are broken because of a race condition.

rivera-ernesto added a commit that referenced this pull request May 25, 2015
Use an absolute path to identify the modulemap.
@rivera-ernesto rivera-ernesto merged commit 704bd39 into CocoaLumberjack:master May 25, 2015
@bpoplauschi bpoplauschi added this to the 2.0.1 milestone Jun 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants