Conversation
Newer Sphinx versions do not output 'Sphinx (sphinx-build) x.x.x' but only 'sphinx-build x.x.x'. This is a pretty simplistic solution, maybe someone can find a better FindSphinx.cmake module entirely. Signed-off-by: Brendan Le Foll <brendan@fridu.org>
Previously we used SWIG_MODULE_<name>_REAL_NAME to have the doc interfaces depend on. However that target is preceeded by the SWIG generation in our case gen_python2-mraa_mraa2PYTHON_wrap. Typically this is hidden because a parralel build has so many other deps this can be hidden but this is the correct path. Fixes eclipse-mraa#911 Signed-off-by: Brendan Le Foll <brendan@fridu.org>
|
@arfoll Thanks for these patches. But I am facing following cmake configuration errors after applying this patch: Not sure regarding above error. In case of FindSphinx.cmake patch, I think for latest sphinx version output of |
|
@b49020 the sphinx fix makes sense that's an easy one. You can put ERROR_VARIALE and OUTPUT_VARIABLE in the same string afaik and it'll work. However the target name is super weird, what is the equivalent target called for you? Just do a |
|
|
Uhm so your job name is python2-mraa_swig_compilation so that's why it doesn't work. I have no idea what makes these job names - more investigation is required! |
|
maybe this needs to depend on https://github.com/Kitware/CMake/blob/master/Modules/UseSWIG.cmake#L172 ? |
|
Maybe take a look at how this was done for UPM too, sounds like a similar target dependency issue. The commits are around the v1.6 tag. |
My Sphinx version finding fix is not very nice, if you have a nicer one @b49020 then I'm perfectly willing to take it.
This should fix #911