Why dependency is missing when trying to compile the 32 bits bear?

[JadenLiu0103]

I want to build the bear by both 32 bits and 64 bits on my redhat machine.

I clone the master, create folders "build32" and "build64" in the repo and do the cmake in both folders.

As is shown above, the action to build 32 bits reports missing dependency, while actually the missing dependency is installed well in the machine. It is proved because no issue reported when building the 64 bits.

Can you tell me what is the reason of these situation and how to fix it?

[rizsotto]

Sorry @JadenLiu0103 , I don't know the reason for that... you can try to run CMake in a verbose mode to see which directories it scans for the dependencies?

[JadenLiu0103]

@rizsotto , thanks for your response.
I defined the gcc and g++ path when doing cmake, it passed without dependency issue.

However, the libexec.so generated is a 64 bits file.

Do you have any comments about this case?

[JadenLiu0103]

Actually, the reason why I want to create a 32-bits libexec.so is that I met an issue when using Bear to generate the compile_commands.json. I thought it could be the reason

Then I find a similar ticket is raised before in #236, I will check the ticket firstly.

[rizsotto]

Hey @JadenLiu0103 , I've just released a new version of Bear.

In this release there are a few changes which addressing the CMake external flag propagation to sub-projects. Could you test it, if it fixes the problem you had previously?

[JadenLiu0103]

@rizsotto , sorry not updating the status. What I found is to create a 32-bits libexec.so, all the dependency must also be 32-bits. Because the computer I worked on cannot access the internet, so the automatic download of the dependency cannot work. What I did is to install the 32-bit dependencies one by one manually, and it solve the problem.

[JadenLiu0103]

Hey @JadenLiu0103 , I've just released a new version of Bear.

In this release there are a few changes which addressing the CMake external flag propagation to sub-projects. Could you test it, if it fixes the problem you had previously?

Because now I am using the bear without problems, so I am afraid I will not try the new version recently. Sorry for that.