test_config.h is being generated at compile time to host the compilation PATHs used later during the testing. Currently is being include by ServerFixture.hh but it is really only used in ServerFixture.cc. I've created a branch to move the include and also do not install that file in the system, it makes no sense to install/release compilation paths.
Since from ServerFixture.cc we are generating the libgazebo_test_fixture.a static library, we are using these hardcoded compilation PATHs in there. We need to figure out how to fix this problem and allow users to specify/get their proper testing paths.
Original report (archived issue) by Jose Luis Rivero (Bitbucket: Jose Luis Rivero, GitHub: j-rivero).
test_config.h is being generated at compile time to host the compilation PATHs used later during the testing. Currently is being include by ServerFixture.hh but it is really only used in ServerFixture.cc. I've created a branch to move the include and also do not install that file in the system, it makes no sense to install/release compilation paths.
Since from ServerFixture.cc we are generating the libgazebo_test_fixture.a static library, we are using these hardcoded compilation PATHs in there. We need to figure out how to fix this problem and allow users to specify/get their proper testing paths.