I was suggesting that the actual *config.cmake files go in the python framework to avoid a conflict. Not all projects provide find*.cmake files (freecad being one of them). Otherwise you have to create one as a patch file.
Sent from my iPhone > On Jul 6, 2014, at 2:01 PM, Ryan Schmidt <[email protected]> wrote: > > >> On Jul 5, 2014, at 8:58 AM, Mark Brethen <[email protected]> wrote: >> >> >>> On Jul 5, 2014, at 8:30 AM, Mark Brethen <[email protected]> wrote: >>> >>> The port py-shiboken purposefully deletes the all of the *config.cmake >>> files: >>> >>> post-destroot { >>> move ${destroot}${prefix}/bin/shiboken >>> ${destroot}${prefix}/bin/shiboken-${python.branch} >>> move ${destroot}${prefix}/include/shiboken >>> ${destroot}${prefix}/include/shiboken-${python.branch} >>> move ${destroot}${prefix}/share/man/man1/shiboken.1 >>> ${destroot}${prefix}/share/man/man1/shiboken-${python.branch}.1 >>> if {${python.version} < 30} { >>> move >>> ${destroot}${prefix}/lib/cmake/Shiboken-${version}/ShibokenConfig-python${python.branch}.cmake >>> } else { >>> file delete >>> ${destroot}${prefix}/lib/cmake/Shiboken-${version}/ShibokenConfig.cpython-${python.version}m.cmake >>> } >>> file delete >>> ${destroot}${prefix}/lib/cmake/Shiboken-${version}/ShibokenConfig.cmake >>> file delete >>> ${destroot}${prefix}/lib/cmake/Shiboken-${version}/ShibokenConfigVersion.cmake >>> file delete ${destroot}${prefix}/lib/pkgconfig/shiboken.pc >>> } >>> >>> freecad requires them to build. I did not find ${prefix}/lib/cmake/ in my >>> macports tree. Should the files go there or is there another location they >>> should reside? >>> >>> >>> Mark >> >> Would it make more sense to put: >> >> ${destroot}${prefix}/lib/pkgconfig/shiboken.pc --> >> ${destroot}${prefix}/Library/Frameworks/Python.framework/Versions/2.7/lib/pkgconfig/shiboken.pc >> ${destroot}${prefix}/lib/cmake/Shiboken-${version}/ShibokenConfig*.cmake --> >> ${destroot}${prefix}/Library/Frameworks/Python.framework/Versions/2.7/lib/cmake/Shiboken-${version}/ShibokenConfig*.cmake > > If you're asking if it would make sense to have the port make such symlinks, > then no; that would effectively undo the fix that was committed for #40587 to > avoid the conflicts between subports. > _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
