From d4c953f1a987ecde294a586c5c09955d87473100 Mon Sep 17 00:00:00 2001 From: Kristina Chodorow Date: Wed, 11 Nov 2015 17:24:14 +0000 Subject: C++ libraries in remote repos don't need to set include paths Fixes #445, based on https://github.com/bazelbuild/bazel/compare/master...ulfjack:cpp-include-path. RELNOTES: C++ libraries no longer need includes = ["."] (or similar copts) to include paths relative to a remote repository's root. -- MOS_MIGRATED_REVID=107593486 --- src/main/java/com/google/devtools/build/lib/vfs/PathFragment.java | 3 +++ 1 file changed, 3 insertions(+) (limited to 'src/main/java/com/google/devtools/build/lib/vfs/PathFragment.java') diff --git a/src/main/java/com/google/devtools/build/lib/vfs/PathFragment.java b/src/main/java/com/google/devtools/build/lib/vfs/PathFragment.java index 434cdcfc2c..97221abf6f 100644 --- a/src/main/java/com/google/devtools/build/lib/vfs/PathFragment.java +++ b/src/main/java/com/google/devtools/build/lib/vfs/PathFragment.java @@ -379,6 +379,9 @@ public final class PathFragment implements Comparable, Serializabl * with no path normalization or I/O performed. */ public PathFragment getRelative(PathFragment otherFragment) { + if (otherFragment == EMPTY_FRAGMENT) { + return this; + } return otherFragment.isAbsolute() ? otherFragment : new PathFragment(this, otherFragment); -- cgit v1.2.3