SOLVED compiler "unresolved inclusion" is not an error ?
-
SOLVED case closed As expected - pkg-config DOES NOT integrate with just any Eclipse version / release. I got it working as expected in 2018-09! Sorry for wasting everybody time. Cheers This is really driving me nuts. The verbose output form complier and project GUI will show same /usr/include.... However only full path include file passes test #include /usr/include/gtkmm-3.0/gtkmm.h Including gtkmm.h by itself , will show "unresolved inclusion" #include "gtkmm.h" On top of this - build is successful, no errors and it runs. So "unresolved inclusion" error is no error ?
-
SOLVED case closed As expected - pkg-config DOES NOT integrate with just any Eclipse version / release. I got it working as expected in 2018-09! Sorry for wasting everybody time. Cheers This is really driving me nuts. The verbose output form complier and project GUI will show same /usr/include.... However only full path include file passes test #include /usr/include/gtkmm-3.0/gtkmm.h Including gtkmm.h by itself , will show "unresolved inclusion" #include "gtkmm.h" On top of this - build is successful, no errors and it runs. So "unresolved inclusion" error is no error ?
I can only assume that eclipse is doing something. Normally, a header file that can't be found results in a fatal error. If you really are using
#include "gtkmm.h", maybe eclipse is searching the project directory for the include file and that is what is generating the warning message. GCC/G++ on the other hand, searches the project directory and then the normal system directories for""delimited include files [Include Syntax (The C Preprocessor)](https://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html) If it is the case that you're using#include "gtkmm.h"try changing to#include, and see if that removes the warning.Keep Calm and Carry On
-
I can only assume that eclipse is doing something. Normally, a header file that can't be found results in a fatal error. If you really are using
#include "gtkmm.h", maybe eclipse is searching the project directory for the include file and that is what is generating the warning message. GCC/G++ on the other hand, searches the project directory and then the normal system directories for""delimited include files [Include Syntax (The C Preprocessor)](https://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html) If it is the case that you're using#include "gtkmm.h"try changing to#include, and see if that removes the warning.Keep Calm and Carry On
If it is the case that you're using #include "gtkmm.h" try changing to #include , and see if that removes the warning. I do not know how to enter greater / less then charactere here. I did try #include ( i just cut and paste your text ) with same result. If you czech my next post you will find the answer - I am inclined to believe it is IDE problem. After I did "new project" from scratch the build fails as expected when the file cannot be found. Addendum This is just to keep the discussion going. I did not verify this , but it looks as every time backtick string is added the build process has no error but the includes which cannot be satisfied are flagged as such in source file. I am begging to question WHERE does the backtick string belong - as an option to complier or elsewhere? ( See the other discussion about backtick.)
-
SOLVED case closed As expected - pkg-config DOES NOT integrate with just any Eclipse version / release. I got it working as expected in 2018-09! Sorry for wasting everybody time. Cheers This is really driving me nuts. The verbose output form complier and project GUI will show same /usr/include.... However only full path include file passes test #include /usr/include/gtkmm-3.0/gtkmm.h Including gtkmm.h by itself , will show "unresolved inclusion" #include "gtkmm.h" On top of this - build is successful, no errors and it runs. So "unresolved inclusion" error is no error ?
Nice post here ii want to say that, to get any instant support for this, or any other then they can go here....Lenovo Telefoonnummer +32-63681637 | Klantenservice Belgie[^]
-
If it is the case that you're using #include "gtkmm.h" try changing to #include , and see if that removes the warning. I do not know how to enter greater / less then charactere here. I did try #include ( i just cut and paste your text ) with same result. If you czech my next post you will find the answer - I am inclined to believe it is IDE problem. After I did "new project" from scratch the build fails as expected when the file cannot be found. Addendum This is just to keep the discussion going. I did not verify this , but it looks as every time backtick string is added the build process has no error but the includes which cannot be satisfied are flagged as such in source file. I am begging to question WHERE does the backtick string belong - as an option to complier or elsewhere? ( See the other discussion about backtick.)
It's official - adding `pkg-config gtkmm-3.0 --cflags --libs` to either complier or linker options generates this problem. If there is #include file in source WHICH cannot be found, it is flagged , but the build is without an error and runs. As far as build goes there are NO errors! Is it possible I am putting the backtick string in wrong place ?
-
I can only assume that eclipse is doing something. Normally, a header file that can't be found results in a fatal error. If you really are using
#include "gtkmm.h", maybe eclipse is searching the project directory for the include file and that is what is generating the warning message. GCC/G++ on the other hand, searches the project directory and then the normal system directories for""delimited include files [Include Syntax (The C Preprocessor)](https://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html) If it is the case that you're using#include "gtkmm.h"try changing to#include, and see if that removes the warning.Keep Calm and Carry On
-
It's official - adding `pkg-config gtkmm-3.0 --cflags --libs` to either complier or linker options generates this problem. If there is #include file in source WHICH cannot be found, it is flagged , but the build is without an error and runs. As far as build goes there are NO errors! Is it possible I am putting the backtick string in wrong place ?
In Eclipse, you open the Properties of your project -> expand "C/C++ General" -> "Paths and Symbols". include dir is not right add the directory to it or fix what is there It throws that warning then goes down the search path set in enviroment and then finds it. So you end up compiling fine with a stupid warning in between.
In vino veritas