| *** tpb <[email protected]> has joined #yosys | 00:00 | |
| *** jn <jn!~quassel@user/jn/x-3390946> has quit IRC (Ping timeout: 246 seconds) | 00:04 | |
| *** jn <jn!~quassel@2a0a-a541-d142-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de> has joined #yosys | 00:04 | |
| *** lumo_e <[email protected]> has quit IRC (Quit: Quit) | 00:12 | |
| *** citypw <citypw!~citypw@gateway/tor-sasl/citypw> has joined #yosys | 02:21 | |
| *** chaoticryptidz <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 02:37 | |
| *** chaoticryptidz <[email protected]> has joined #yosys | 02:38 | |
| *** chaoticryptidz <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 02:43 | |
| *** chaoticryptidz <[email protected]> has joined #yosys | 02:44 | |
| *** kristianpaul <kristianpaul!~paul@user/kristianpaul> has quit IRC (Ping timeout: 252 seconds) | 05:20 | |
| *** strobo <[email protected]> has quit IRC (Read error: Connection reset by peer) | 06:09 | |
| *** strobo <[email protected]> has joined #yosys | 06:15 | |
| *** FabM <FabM!~FabM@armadeus/team/FabM> has joined #yosys | 06:51 | |
| *** citypw <citypw!~citypw@gateway/tor-sasl/citypw> has quit IRC (Ping timeout: 246 seconds) | 07:15 | |
| *** notgull <notgull!~notgull@ec2-50-112-148-23.us-west-2.compute.amazonaws.com> has quit IRC (Ping timeout: 240 seconds) | 07:41 | |
| *** notgull <notgull!~notgull@ec2-50-112-148-23.us-west-2.compute.amazonaws.com> has joined #yosys | 07:49 | |
| *** citypw <citypw!~citypw@gateway/tor-sasl/citypw> has joined #yosys | 08:40 | |
| *** schaeg <schaeg!~anabrid@2001:638:904:ffc8:a469:760:53ab:b0fd> has joined #yosys | 09:18 | |
| *** kristianpaul <kristianpaul!~paul@user/kristianpaul> has joined #yosys | 10:24 | |
| *** unkraut <[email protected]> has joined #yosys | 10:35 | |
| *** schaeg <schaeg!~anabrid@2001:638:904:ffc8:a469:760:53ab:b0fd> has quit IRC (Ping timeout: 240 seconds) | 10:53 | |
| *** marex <[email protected]> has quit IRC (Server closed connection) | 11:09 | |
| *** marex <[email protected]> has joined #yosys | 11:09 | |
| *** nonchip <[email protected]> has quit IRC (Read error: Connection reset by peer) | 11:33 | |
| *** nonchip <[email protected]> has joined #yosys | 11:33 | |
| *** lexano <[email protected]> has joined #yosys | 11:39 | |
| *** unkraut <[email protected]> has quit IRC (Remote host closed the connection) | 12:07 | |
| *** unkraut <[email protected]> has joined #yosys | 12:08 | |
| *** citypw <citypw!~citypw@gateway/tor-sasl/citypw> has quit IRC (Ping timeout: 246 seconds) | 13:23 | |
| dxld | I'm looking at packaging sby for Debian. Looking at the tags I'm wondering if the release cycle is syncronized to yosys like YosysHQ/abc is or would it make sense to run an older sby against a newer yosys (or the other way around)? | 14:27 |
|---|---|---|
| dxld | depending on that I may package it along with the main yosys source but then the two will always be tied to each other release wise and a build problem in one will block both etc | 14:28 |
| *** chaoticryptidz <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 14:39 | |
| *** chaoticryptidz <[email protected]> has joined #yosys | 14:40 | |
| jix | dxld: they're essentially synchronized, older sby against newer yosys should mostly work but older sby against newer yosys often doesn't. | 14:50 |
| jix | eh, older sby against newer yosys should work but older yosys with newer sby doesn't... as in adding functionality to SBY often requires adding supporting functionality in yosys | 15:04 |
| jix | dxld: and as a heads-up, we plan to eventually move all python frontend tools including SBY and EQY to depend on https://github.com/YosysHQ/mau and be more structured like https://github.com/YosysHQ-GmbH/ivy (IVY depends on verific for now, so not something relevant for packaging, just the only example fully developed starting with mau) but there's no concrete timeline for this for SBY yet | 15:07 |
| jix | so that'd also be a move from no python native packaging to relatively modern pyproject.toml based packaging, which might be relevant | 15:09 |
| jix | dxld: in any case I can ping you when actual work on migrating SBY to use mau starts | 15:09 |
| *** whitequark[cis] <whitequark[cis]!whitequark@2a01:4f8:c012:5b7:0:1:0:4> has joined #yosys | 15:11 | |
| whitequark[cis] | oh finally, will they be released on pypi too? | 15:12 |
| jix | would make sense if we can automate that whenever we tag a version corresponding to a yosys release | 15:13 |
| jix | (which is "just" an issue of someone needs to find time to figure out the details to do that for the projects that are already having a pyproject.toml) | 15:14 |
| jix | for EQY (which will probably be moved to mau before SBY) there would also be the question of how to handle the yosys plugins it uses, compiling them against whatever yosys-config is in path while building the python package might not be the right approach in every scenario | 15:27 |
| jix | I guess it could optionally support that and also support compiling and caching the plugins on-demand which would only leave the question of what to do when as default | 15:28 |
| *** bjork1intosh <bjork1intosh!~bjork@2600:1700:5400:c80:3b32:93d5:8bc9:ba90> has quit IRC (Quit: Leaving) | 16:05 | |
| *** bjorkintosh <bjorkintosh!~bjork@user/bjorkintosh> has joined #yosys | 16:12 | |
| *** sauce <[email protected]> has quit IRC (Ping timeout: 264 seconds) | 16:51 | |
| *** sauce <[email protected]> has joined #yosys | 17:05 | |
| *** strobo <[email protected]> has quit IRC (Read error: Connection reset by peer) | 18:10 | |
| *** strobo <[email protected]> has joined #yosys | 18:16 | |
| *** FabM <FabM!~FabM@armadeus/team/FabM> has quit IRC (Ping timeout: 246 seconds) | 19:27 | |
| *** Lord_Nightmare <Lord_Nightmare!Lord_Night@user/lord-nightmare/x-3657113> has quit IRC (Quit: ZNC - http://znc.in) | 19:34 | |
| *** Lord_Nightmare <Lord_Nightmare!Lord_Night@user/lord-nightmare/x-3657113> has joined #yosys | 19:37 | |
| dxld | jix: thanks. I think I'll go the separate package route then. and yeah ping would be appreciated | 21:18 |
| *** skipwich <skipwich!~skipwich@user/skipwich> has quit IRC (Ping timeout: 258 seconds) | 21:24 | |
| *** skipwich <skipwich!~skipwich@user/skipwich> has joined #yosys | 21:30 | |
| *** strobo <[email protected]> has quit IRC (Ping timeout: 260 seconds) | 21:44 | |
| cr1901 | >how to handle the yosys plugins | 21:54 |
| cr1901 | Did Windows support for plugins ever get merged in? I know someone did the work | 21:54 |
| *** skipwich <skipwich!~skipwich@user/skipwich> has quit IRC (Ping timeout: 260 seconds) | 21:54 | |
| jix | https://github.com/YosysHQ/yosys/pull/3534 was merged | 21:55 |
| *** skipwich <skipwich!~skipwich@user/skipwich> has joined #yosys | 21:55 | |
| *** skipwich <skipwich!~skipwich@user/skipwich> has quit IRC (Ping timeout: 260 seconds) | 22:03 | |
| *** skipwich <skipwich!~skipwich@user/skipwich> has joined #yosys | 22:08 | |
| *** nonchip <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 22:17 | |
| *** nonchip <[email protected]> has joined #yosys | 22:17 | |
| *** skipwich <skipwich!~skipwich@user/skipwich> has quit IRC (Ping timeout: 240 seconds) | 22:24 | |
| *** strobo <[email protected]> has joined #yosys | 22:26 | |
| *** skipwich <skipwich!~skipwich@user/skipwich> has joined #yosys | 22:26 | |
| cr1901 | Huh, I must've missed that. I'll have to try and see if the ghdl plugin works and update my build scripts accordingly | 22:31 |
| *** skipwich <skipwich!~skipwich@user/skipwich> has quit IRC (Ping timeout: 264 seconds) | 22:35 | |
| *** skipwich <skipwich!~skipwich@user/skipwich> has joined #yosys | 22:36 | |
| *** skipwich <skipwich!~skipwich@user/skipwich> has quit IRC (Ping timeout: 244 seconds) | 22:45 | |
| *** skipwich <skipwich!~skipwich@user/skipwich> has joined #yosys | 22:48 | |
| *** strobo <[email protected]> has quit IRC (Ping timeout: 264 seconds) | 23:54 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!