kudu-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From a...@apache.org
Subject [kudu] 02/02: [docs] Kudu source code indexing in Eclipse
Date Fri, 13 Sep 2019 22:57:19 GMT
This is an automated email from the ASF dual-hosted git repository.

adar pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git

commit 36d7e909539e5f0f70a9460dde31d0bba58089c8
Author: Volodymyr Verovkin <verjovkin@cloudera.com>
AuthorDate: Fri Sep 6 15:28:15 2019 -0700

    [docs] Kudu source code indexing in Eclipse
    Added alternative recommendation to deal with Kudu source code indexing in Eclipse.
    Change-Id: Ia214e536ff3a7ddafb3ab969b50ed5f97f4c725a
    Reviewed-on: http://gerrit.cloudera.org:8080/14193
    Tested-by: Kudu Jenkins
    Reviewed-by: Adar Dembo <adar@cloudera.com>
 README.adoc | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/README.adoc b/README.adoc
index 1c3352f..bad43b2 100644
--- a/README.adoc
+++ b/README.adoc
@@ -429,6 +429,18 @@ With this exclusion, the only false positives (shown as "red squigglies")
 CDT presents appear to be in atomicops functions (`NoBarrier_CompareAndSwap` for
+Another way to approach enormous source code indexing in Ecplise is to get rid of
+unnecessary source code in "thirdparty/src" directory right after building code
+and before opening project in Eclipse. You can remove all source code except
+hadoop, hive and sentry directories.
+Additionally, if you encounter red squigglies in code editor due to
+Eclipse's poor macro discovery, you may need to provide Eclipse with preprocessor
+macros values, which it could not extract during auto-discovery.
+Go to "Project Explorer" -> "Properties" -> "C/C++ General" ->
+"Preprocessor Include Paths, Macros, etc" -> "Entries" tab -> Language "GNU C++" ->
+Setting Entries "CDT User Setting Entries" -> button "Add"
+-> choose "Preprocessor Macro" [3]
 Another Eclipse annoyance stems from the "[Targets]" linked resource that Eclipse
 generates for each unit test. These are probably used for building within Eclipse,
 but one side effect is that nearly every source file appears in the indexer twice:
@@ -438,6 +450,7 @@ on writing code, though it may affect your ability to build from within
 1. https://cmake.org/pipermail/cmake-developers/2011-November/014153.html
 2. https://public.kitware.com/Bug/view.php?id=15102
+3. https://www.eclipse.org/community/eclipse_newsletter/2013/october/article4.php
 == Export Control Notice

View raw message