diff options
| author | Mike Kaganski <mike.kaganski@collabora.com> | 2018-05-02 13:29:21 +0100 |
|---|---|---|
| committer | Mike Kaganski <mike.kaganski@collabora.com> | 2018-05-02 16:31:59 +0200 |
| commit | ea1f50894ac3e681213b874af08217ae25d0433a (patch) | |
| tree | 8e32b3e6ca12b59e842dd7b507434ed17d171c7e /officecfg/registry | |
| parent | b18953565b68e46289ad85927d79f5978a51078b (diff) | |
VS IDE integration: use full Windows include paths in VS projects
It turns out that VS IDE's "Peek definition" (and other functions that
navigate to sources) fail if the short ("DOS") path to the file is given
in project's includes: see issue at
https://developercommunity.visualstudio.com/content/problem/139659/vc-peek-definition-fails-to-navigate-to-windows-ki.html
This patch converts the include paths to full Windows paths, to avoid the
problem. Also, since IDE starts working correctly with this change, this
patch removes inclusion of "inherited" paths "$(IncludePath)", which are
the paths added by Visual Studio itself. Since we do specify all include
paths explicitly, that is not required, and avoids confusion.
Change-Id: Ide2d948f8c7b050b02f550342144fede4fcafb82
Reviewed-on: https://gerrit.libreoffice.org/53731
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
Diffstat (limited to 'officecfg/registry')
0 files changed, 0 insertions, 0 deletions