Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState: Missing FileEntry for some header

ROOT
1

Hi,
I have a project that generates some libs. In my project the structure of folders looks like this:

/project/libA/A/headerA.h
..
/project/libB/B/headerB.h // libB depends on libA
...

Now, I would like to use this project in an external project. When I install my software, all the headers are copied to the common install directory. So it’s look like:

superproject/include/ "some project headers"
superproject/include/my_project/ "my project haders"

As long as I keep my build directory intact it works, however when I remove my build and try to call:
gInterpreter->AutoParse(“libB”);
I get this error . Missing FileEntry for A.h
Now the question is why It can load libA that require superproject/project/A.h but cannot load the same file when call libB?
Is it possible to use “flat” hierarchy of headers in my superproject?

ROOT Version: Not Provided
Platform: Not Provided
Compiler: Not Provided

2

Hi,

are the headers you need to autoparse in the ROOT_INCLUDE_PATH?

Cheers,
D

3

Hi,
I tried but it didn’t help. I think the problems are caused by the fact that in this project, I install all headers in a single directory, e.g. include/A.h include/B.h, whereas during compilation, those files are in subdirectories, e.g. libA/AA.h. In my dictionary the include contains “include A/A.h” not “include A.h” - and this generates the problems.
I’m curious if there is some workaround to keep the flat hierarchy of headers after installation even if folder for single library have more complicated structure.
For example if its possible to generate dictionary that only contains name of the header file without any names of directories.

4

cd include ; ln -s . A ; ln -s . B

5

Do you suggest that I should make symbolic links before the generation of the dictionary?
Basically this is what I would like o avoid. I can simple create all headers in my library folder, but this would create a quite messy directory.

Edit: I forced to build dictionary with names of headers only, I also set ROOT_INCLUDE_PATH now it works.
But can somebody tell me how its possible that code use build directory that is not encoded in any environmental variable?

6

You could use ROOT — Modern CMake
combined with ROOT_GENERATE_DICTIONARY, that way you do not need environmental variables, just passing -DROOT_DIR to cmake.