Fix compilation of downstream bindings that include yarp.i #3148
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #3146 there was a regression, as a new file
swig_python_windows_preable.i
was included in theyarp.i
and it was generated by CMake in its binary directory. However, that file is not supposed to be included (and it is not even availble in the include path) when a downstream project (likeicub-main
) includes the file in its own.i
swig binding file.This PR fixes the issue by only including the file when
yarp.i
is used to generate the yarp bindings, and not when theyarp.i
is included in a downstream project, by checking if theSWIG_GENERATING_YARP_BINDINGS
preprocessor macro (that is only defined in the CMake build of YARP bindings) is defined.Fix robotology/icub-main#992 .