libftdi Archives
|
From: | Richard Shaw <hobbes1069@xxxxxxxxx> |
---|---|
To: | Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx> |
Cc: | libftdi@xxxxxxxxxxxxxxxxxxxxxxx |
Date: | Mon, 18 Feb 2019 13:42:12 -0600 |
On Mon, Feb 18, 2019 at 1:24 PM Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx> wrote: Hello Richard, Yeah, I figured it might, I was just going for a quick and dirty version to get it building again on Rawhide. > option ( PYTHON_BINDINGS "Build python bindings via swig" ON ) Yeah, I saw the new release. I'm not the main package maintainer but I did look at what it would take to update, there's a fair number of packages affected so I plan to look at that over the next couple of weeks. I've spotted this in there: That might work with older cmake but part of the new method is the dependency has to be set *before* the swig_add_module/library call. "Source file properties on module files must be set before the invocation of the swig_add_library command to specify special behavior of SWIG and ensure generated files will receive the required settings." At least I couldn't get it to work until I did that because ftdi1.i kept trying to link before ftdi1_doc.i was generated. The updated patch can be found on the "cmake-swig-updates" branch. Will do and will let you know. I should have time tonight after $DAYJOB. I was about to cut a release for libftdi 1.5, so it would be You can always try out mock, that what I use, lets you build in a chroot from EL 6->7 to Fedora 28->Rawhide from your F29 machine. After I check the patch I'll probably wait for 1.5 so I only have to rebuild all the dependent packages once. Hopefully no major API changes? Thanks, Richard libftdi - see http://www.intra2net.com/en/developer/libftdi for details. |
Current Thread |
---|
|