14:45 <maikmerten> on Ubuntu 18.10, nextpnr doesn't want to build the GUI. It doesn't find libboost-pyhton, despite libboost-python1.67-dev being installed

14:45 <maikmerten> is 1.67 not suitable for nextpnr?

14:46 <daveshah> the naming of boost-python is dodgy

14:46 <daveshah> it's probably changed in Ubuntu 18.10

14:46 <maikmerten> ewww, exactly what the doctor ordered for dev files

14:48 <daveshah> I'm using 1.68, but on Arch Linux. I'm pretty sure I have used 1.67 in the past before Arch updated it too

14:48 <maikmerten> https://paste.debian.net/1051697/ <-- cmake output

14:48 <tpb> Title: debian Pastezone (at paste.debian.net)

14:49 <maikmerten> is there something simple people without cmake or boost experience can try?

14:50 <daveshah> I think that's a false warning that noone ever managed to supress

14:50 <daveshah> Does it build?

14:52 <maikmerten> it tries to

14:52 <maikmerten> but in the end it doesn't find a rule to build /usr/lib/x86_64-linux-gnu/libboost_python-py36.so

14:52 <maikmerten> (which exists)

14:53 <maikmerten> correction, which does *not* exist

14:53 <maikmerten> only similar named files, which would explain something

14:54 <daveshah> It seems it was renamed to python3

14:54 <daveshah> https://packages.ubuntu.com/cosmic/amd64/libboost-python1.67-dev/filelist

14:54 <tpb> Title: Ubuntu – File list of package libboost-python1.67-dev/cosmic/amd64 (at packages.ubuntu.com)

14:54 <maikmerten> yup

14:54 <maikmerten> trying a symlink

14:54 <daveshah> every distribution has their own way of naming it

14:54 <maikmerten> which is nasty

14:54 <maikmerten> but well...

14:55 <maikmerten> okay, the symlink seems to work

14:56 <maikmerten> aaaaand... the GUI works as well

14:56 <daveshah> What is strange is it claims that it does find "python-py36"

14:57 <maikmerten> well, build system madness

14:57 <maikmerten> seems to be a thing

17:17 <adamgreig> huh, I had nextpnr build OK on ubuntu 18.04 without needing to make a symlink

17:17 <adamgreig> though I did get No header defined for python-py365; skipping header check

17:17 <adamgreig> and same for -py36

17:18 <adamgreig> make proceeded OK though

20:03 <esden> I have built nextpnr-ice40 from the newest master (with the new router) and I see that the GUI is not updating the routing visualization with each router step. Is it a known missing-feature/known-bug or is it something with my setup? I know it is "just" eye candy but still... ;)