14 May 2013 10:28
How the includes statements in a cpp project are analyzed by semantic
Pamela Carreño <carrenopamela <at> gmail.com>
2013-05-14 08:28:28 GMT
2013-05-14 08:28:28 GMT
Hi,
last week I had some problems with semantic and the include statements in my .cpp and .h files, many of the includes were not being found and analyzed by semantics
After several tries I noticed that after changing from #include <statement> to the respective #include "statement", everything started to work as expected. Is this a normal behavior? Or maybe is it related to how I defined the project using ede-cpp-root-project?
My definition is:
(ede-cpp-root-project "FLANN"
:name "Flann1.8"
:file "/home/carrenom/Documents/PhD/Code/Kd-Trees_NNS/Flann/CMakeLists.txt"
:include-path '("/test"
"/examples"
"/src/cpp/flann"
"/src/cpp/flann/algorithms"
"/src/cpp/flann/io"
"/src/cpp/flann/mpi"
"/src/cpp/flann/nn"
"/src/cpp/flann/util"
)
:system-include-path '("/usr/include/" "/usr/include/c++/4.7/")
:spp-table '(("isUnix" . "")
("BOOST_TEST_DYN_LINK" . "")))
An example of the behaviour I am talking about
//#include <flann/flann.h> NOT OK TO SEMANTIC
//#include <flann/io/hdf5.h> NOT OK TO SEMANTIC
#include "../src/cpp/flann/flann.h" OK TO SEMANTIC
#include "../src/cpp/flann/io/hdf5.h" OK TO SEMANTIC
Also I would like to know how semantic visits and analyze all the includes in the source code.
Regards,
Pamela Carreno
------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d
_______________________________________________ cedet-semantic mailing list cedet-semantic <at> lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cedet-semantic
RSS Feed