Hi
your patch does not work with the iOS modules. I also did a short rust 
search, and it seems include path is supported:
https://stackoverflow.com/questions/42741815/setting-the-include-path-with-bindgen
I recommend not to activate this patch.
RGDS
Jan I
On Sun, 11 Feb 2018 at 18:04, Sander Maijers <s.n.maijers@gmail.com 
<mailto:s.n.maijers@gmail.com>> wrote:
    At this revision
    
(https://github.com/LibreOffice/online/tree/341c9dcc96dcf84cadfabcce2c3eabc09c1bf8d1/bundled/include/LibreOfficeKit),
    I can’t generate bindings for Rust from LibreOfficeKit header
    files. The
    reason is that I have no way to specify include paths while the
    LibreOfficeKit header files assume their sibling header files are
    to be
    found in the system include paths, based on the `< >` include
    directive
    syntax. I think that’s incorrect since LibreOfficeKit is a unit
    itself;
    all header files are supposed to be adjacent in the same directory
    tree.
    I found support for my view in this previous discussion
    (https://lists.freedesktop.org/archives/libreoffice/2017-October/078601.html).
    I propose the attached patch. With it, generating Rust bindings for
    LibreOfficeKit has been tested to succeed.
    _______________________________________________
    LibreOffice mailing list
    LibreOffice@lists.freedesktop.org
    <mailto:LibreOffice@lists.freedesktop.org>
    https://lists.freedesktop.org/mailman/listinfo/libreoffice
--
Sent from My iPad, sorry for any misspellings.
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.