Eclipse compiles successfully but still gives semantic errors

Question

NOTE: it apparently is a recurrent question on StackOverflow, but - for what I have seen - either people never find a way or their solution does not work for me

The problem:

I am using Eclipse Juno ADT. Everything was working fine until I tried to update the NDK. I replaced my ndk folder (that was the ndk-r8d) by the new version (i.e. ndk-r8e) and, in my Paths and Symbols configuration, I changed the includes to go from g++ 4.6 to 4.7.

It seemed to break my index: I could compile my code, but Eclipse was giving semantic errors, exactly like in [1] and [2]. The errors mainly come from symbol used by OpenCV4Android, such as distance, pt, queryIdx and trainIdx.

When I tried to backup to my old configuration, the index was still broken! I cannot find a way to change this.

What I have tried

Clean up the project
Rebuild, refresh, and all the other options in the "Index" submenu (when "right-clicking" on the project)
Disable / enable the indexer in the preferences
Verify that symbols such as trainIdx only appear in my OpenCV4Android include in the Paths and Symbols section.
Change the order of my includes in the Paths and Symbols section. I basically tried to put the OpenCV include in the beginning and in the end.

Some observations

What is not working

I assume that it is the CDT index because of the following:

In command line, I can build my project using ndk-build clean and ndk-build.
When I start Eclipse, I have no error until I open a C++ file (from the jni folder).
I can always build the project, but as long as I have opened a C++ file, I can't run the application anymore because of a lot of Field '<name>' could not be resolved.
If I don't open the C++ files, Eclipse doesn't report any error and can build and deploy the Android application successfully.

Interesting fact

The following code reports errors on line, queryIdx, pt:

cv::line(mRgb, keypointsA[matches[i].queryIdx].pt, keypointsB[matches[i].trainIdx].pt, cv::Scalar(255, 0, 0, 255), 1, 8, 0);

If I write it as follows, it works:

cv::DMatch tmpMatch = matches[i];
cv::KeyPoint queryKp = keypointsA[tmpMatch.queryIdx];
cv::KeyPoint trainKp = keypointsB[tmpMatch.trainIdx];
cv::line(mRgb, queryKp.pt, trainKp.pt, cv::Scalar(255, 0, 0, 255), 1, 8, 0);

It is not that all of the OpenCV functions are unresolved: only pt, queryIdx and trainIdx are.

Any comment will be really appreciated.

open the problems perspective of eclipse. It should shows tons of error (entries with a red markers next to each entry). Delete all the entries and rebuild your app. I had the same issue and it is really boring — Blackbelt, Jun 02 '13 at 10:14
@blackbelt Blackbelt has provided a quick resolution to the problem if it occurs to you once more (and there is a single entry or two that are just bothering you). — Jay Snayder, Sep 03 '14 at 14:02
This is perfect example of what a S.O question should be like. Nicely sectioned into "The problem", "What is not working", "What I have tried", etc. Perhaps we should refer new sign-ups to it, as an example. — Mawg says reinstate Monica, Dec 03 '14 at 09:04

score 33 · Accepted Answer · edited Jul 19 '16 at 10:42

33

In your selected project preferences within the Eclipse environment, go to C/C++ General -> Code Analysis -> Launching. Make sure that both check boxes are unchecked. Close and reopen the project or restart eclipse and rebuild the project.

edited Jul 19 '16 at 10:42

Jeet

1,006
1
14
25

answered Jun 03 '13 at 07:14

Alex Cohn

56,089
9
113
307

Yes, the on-the-fly code analyzer for Android gcc in Eclipse seems to be not mature yet. – Alex Cohn Jun 03 '13 at 09:29
2

That's not a solution _per se_, but I had to do this eventually. – JonasVautherin Jun 24 '13 at 07:04
its a solution "for now" – M. Usman Khan Jul 22 '14 at 08:15
2

@AlexCohn +1 may God bless you, this issue drove me crazy for a complete day – Shmil The Cat Nov 18 '14 at 11:02

score 10 · Answer 2 · answered Apr 08 '14 at 11:19

Since indexing for Android native code on Eclipse is incomplete, I managed to enable indexing in my NDK projects the following unintuitive way, it should work whether you use ndk-build or plain make or even cmake. I'm using Kepler but it should work on older versions too.

Get your toolchain right

Right click on project -> Properties -> C/C++ Build -> Tool Chain Editor -> Uncheck Display compatible toolchains only.
In the same window, set Current toolchain to Linux GCC.
In the same window, set Current builder to Android Builder if you're using ndk-build, set it to Gnu Make Builder otherwise (this step may be wrong, sorry in advance if it is).
Right click on project -> Properties -> C/C++ Build -> Build Variables -> Make sure Build command reads the correct command for your project; if it's not, uncheck Use default build command and correct it (it may be ndk-build or make -j5 that you want). If you build the native code in a separate terminal, you can skip this step.

Make a standalone toolchain, it's probably the cleanest way to get STL sources in one place

Go to the NDK root directory.

Run the following (tweak the settings according to your liking). Add sudo if you don't have write permissions to the --install-dir because the script fails silently.

    ./build/tools/make-standalone-toolchain.sh \
        --platform=android-14 \
        --install-dir=/opt/android-toolchain \
        --toolchain=arm-linux-androideabi-4.8

This is assuming that you use GNU-STL. If you use another C/C++ library, you will need to tweak the above command, and probably also the include paths in the next command.

Add the necessary include paths to your project

Right click on project -> Properties -> C/C++ General -> Paths and Symbols -> Go to the Includes tab -> Select GNU C++ from Languages -> Click Add and add the following paths (assuming you installed the standalone toolchain to /opt/android-toolchain):
- /opt/android-toolchain/include/
- /opt/android-toolchain/include/c++/4.8/
- /opt/android-toolchain/include/c++/4.8/arm-linux-androideabi/
- /opt/android-toolchain/lib/gcc/arm-linux-androideabi/4.8/include/
- /opt/android-toolchain/include/c++/4.8/backward/
- /opt/android-toolchain/lib/gcc/arm-linux-androideabi/4.8/include-fixed/
- /opt/android-toolchain/sysroot/usr/include/
Here, you can add every include path you want. In fact, I have my OpenCV built for Android and installed in the standalone toolchain, so I have the following include there:
- /opt/android-toolchain/sysroot/usr/share/opencv/sdk/native/jni/include/

Now, the indexing should work. You should also be able to run ndk-build (or make if that's your build method) and then deploy your project to your device inside Eclipse.

Why?

Android native development on Eclipse is incomplete since the indexing doesn't work out of the box. This is due to having to support multiple architectures (ARMv7, Intel etc.), multiple STL options, multiple Android versions etc. This is why you have the bare make based ndk-build and the whole NDK structure, and this is also why NDK development is very unclean and few large volume native Android projects exist.

A big Android project is OpenCV where they had to develop a 1500 odd line CMake script to get it to compile for Android properly. At some point, they tried to export that script as a CMake based build system for Android but it couldn't keep up with the changes in the NDK system and was abandoned. This support should have been inside NDK itself.

The default NDK build system should have been standalone toolchain only, with all different architectures/C++ libraries having their own toolchains at the cost of storage space but with the advantage of cleanness, intuitiveness and good practice. Then you can incorporate any standard cross-compilation system that is also used elsewhere, is tested and is well-known, e.g CMake. You can, and in my opinion you should, do that with the NDK's make-standalone-toolchain command as shown above. But in the end, this is only my opinion. If you feel comfortable enough with ndk-build then go ahead.

I guess that the main _raison d'etre_ of Android.mk and the whole ndk-build system was that it was cut out of the Android system tree. At first, Google didn't think people would need C/C++ for their apps at all, only as system libraries. Later, they provided NDK, but it's still contaminated with tools that are only relevant for system tree build. — Alex Cohn, Apr 08 '14 at 20:27
That makes sense. However, I find that seeing C++ support non-essential in the beginning is just naive. Take games for example, it is obvious that they are a big part of the mobile application world and they are practically %99 native code. There are probably other applications out there (e.g that is into image processing or uses visual effects) that are similar. So in the end, they should have provided robust and easy support for native development. — Ayberk Özgür, Apr 09 '14 at 07:18
Well, NDK circa '14 is much, much more robust, feature-rich, and easy than 3 years ago. I should say that I cannot agree with your preference to standalone toolchain. It's perfect to port huge existing make-based projects, but it does not answer the need to compile for arm/mips/x86, etc. I find that for homegrown projects, it pays off to set up the `Android.mk` files hierarchy and enable quick and easy `ndk-build`. BTW, there is a very helpful [CMake adaptation for Android NDK](https://code.google.com/p/android-cmake/). It does use standalone toolchain. — Alex Cohn, Apr 09 '14 at 08:24
I can understand the desire to build simultaneously for multiple architectures, but the great majority of Android devices are ARMv7 with Intel entering the field just recently. In the worst case, I would rather use two standalone toolchains for ARMv7 and x86 along with my already CMake enabled project (that I can compile for the host or any other cross-platform target I want without changing a single line in my code/scripts) and neglect all other architectures (e.g MIPS or ARMv5 which is practically obsolete now) than using `ndk-build` and its Makefiles that is ancient technology by itself. — Ayberk Özgür, Apr 09 '14 at 10:36
Not to mention that I will prevent my APK from bloating with MIPS native libraries that will eventually run on 5 devices total when deployed. That is what most app developers are doing (http://forum.xda-developers.com/showthread.php?t=1385493) and I completely understand and support their decision. — Ayberk Özgür, Apr 09 '14 at 10:37
On the other topic, that CMake adaptation is the one I talked about in the original answer: It is exported from the OpenCV Android CMake script and the last commit was on 2012. The original script (can be found in the OpenCV repo) has evolved and developed much since that time. But a similar (but much simpler) functionality can be achieved with a 5 line CMake toolchain script that sets your sysroot. — Ayberk Özgür, Apr 09 '14 at 10:38
Great reason to simultaneously build is ARM, x86 for simulator and device. You could use ARM for both, but then the emulator is so slow you end up always on device. — Cameron Lowell Palmer, Oct 31 '14 at 13:42
By the way, on an unrelated topic, do yourselves a favor and switch to vim+YCM for c/c++ development. Eclipse is really not a good tool for that. — Ayberk Özgür, Nov 25 '14 at 08:20

score 6 · Answer 3 · edited May 23 '17 at 12:26

6

It's actually quite hard to say what is the problem. Here are some advices:

Try to import and build hello-jni (it is located in jni's samples folder). If it runs without problems than problem is with linking OpenCV to your project.
It seems that you forgot to update android-ndk location in project properties -> c/c++ build -> environment. Here's link to problem Issue with build Android NDK project.
Build from console your project (ndk-build -B), delete all errors in Eclipse manually (in Problems view select all errors and just click delete) and try to run project now. Sometimes this "hack" helps me to run project.
Close Eclipse and delete folder path-to-your-workspace/.metadata/.plugins/org.eclipse.cdt.core (backup it first).

edited May 23 '17 at 12:26

Community

1
1

answered Jun 02 '13 at 10:28

ArtemStorozhuk

8,715
4
35
53

Thanks for your help. I'll try `1.` tomorrow. For `2.`, I have already updated it. I am currently using `3.` to run the project, but I need to do this every time because the same errors come back. I think I have already tried `4.`, but I will try again tomorrow! – JonasVautherin Jun 02 '13 at 10:52
`4.` did not work. For `1.`, I have an error in `hello-jni.c`: `Method 'NewStringUTF' could not be resolved`. Any new idea? – JonasVautherin Jun 03 '13 at 07:00
More interestingly, I installed a new version of Eclipse-ADT to import my project and it had the same errors. I then tried to import `hello-jni` in this new Eclipse and it has the very same error. Is it possible that my problem is linked to my Ubuntu? Everything was working fine during the last few months though... – JonasVautherin Jun 03 '13 at 07:05
Does compiler find `jni.h`? If yes, does it contain `NewStringUTF` function? – ArtemStorozhuk Jun 03 '13 at 16:00
The project compiles successfully. When I `Ctrl + Click` on `jni.h` in the includes, I go to the file and it contains the `NewStringUTF` function. – JonasVautherin Jun 04 '13 at 06:14
I see only one possible solution: re-installation of Eclipse. I recommend you to download it directly from [Android site](http://developer.android.com/sdk/index.html). – ArtemStorozhuk Jun 04 '13 at 18:01
That's another interesting point: by re-installing Eclipse and importing my project again, I came with the exact same problem... – JonasVautherin Jun 05 '13 at 05:14
Even `hello-jni` doesn't run? – ArtemStorozhuk Jun 05 '13 at 08:24
Precisely. Is there therefore something common between my old Eclipse and the freshly-installed one that might have been altered? – JonasVautherin Jun 05 '13 at 08:52
I gave you the bounty to thank you for the time you spent on my problem. But any more comment would be greatly appreciated =). – JonasVautherin Jun 07 '13 at 05:21
@JonesV thanks for that :) I think that Android Studio won't have such problems. – ArtemStorozhuk Jun 07 '13 at 18:19
1

I hasn't indeed, since there's no NDK integration yet... =) – JonasVautherin Jun 08 '13 at 06:55
1

@JonesV, yes I said "won't have". This is Android IDE from Google at it will obviously have it. [Read this](http://blog.jetbrains.com/blog/2013/05/15/intellij-idea-is-the-base-for-android-studio-the-new-ide-for-android-developers/). – ArtemStorozhuk Jun 08 '13 at 07:32

score 0 · Answer 4 · answered Jan 05 '14 at 21:32

0

Go to Preferences > C/C++ > Language Mapping > ADD (Source C File and select GNU C) Do the same for C++

answered Jan 05 '14 at 21:32

user3163532

1

score 0 · Answer 5 · answered Oct 21 '14 at 06:02

I had the same issue. I had all the proper include paths setup but after opening the .c/.cpp or .h file and it would start marking everything as "Unresolved."
This worked for me...
Go to:
PREFERENCES -> C/C++ -> INDEXER
Check Index Source And Header Files Open in Editor.

xdaimon · Answer 6 · 2015-02-25T17:01:42.673

I had the same issue, like many people.

I followed the steps in Ayberk Özgür post, which make good sense. Although I also had to make sure to put includes under all three languages: GNU C, GNU C++, and Assembly. Probably because I'm not using a stand alone tool chain.

I at first had my includes only under GNU C and GNU C++ languages. Which left me still with the unresolved includes error. Not until I assigned my includes under the Assembler language as well did my errors go away.

I do not know why eclipse is only searching through the Assembler includes in my project. I also do not know how this part of the solution will work for bigger more complicated projects.

Hope this helps.

score 0 · Answer 7 · edited Sep 26 '15 at 03:03

0

I had the similar situation with Eclipse CDT working with the OpenCV library. I got several error messages while the program compiled correctly. I changed the indexer setting in "window->preferences->Indexer" "build configuration for indexer" box to "Use Active Configuration" which solved my issue.

edited Sep 26 '15 at 03:03

Blackwood

4,504
16
32
41

answered Sep 26 '15 at 02:44

Pejman Habashi

104
5

score 0 · Answer 8 · answered Mar 16 '16 at 13:09

I just spent about 3h banging my head against this Eclipse NDK indexing issue!..

What made it work: make sure that you have only ONE cpu architecture specified in Your Application.mk file.

Otherwise the .metadata/.plugins/com.android.ide.eclipse.ndk/*.pathInfo file will not be generated by the NDK build. This file contains built-in values from Project -> Properties -> C/C++ General -> Paths and Symbols -> Includes (just making .pathInfo file does not fix the problem)