| *** tpb <[email protected]> has joined #f4pga | 00:00 | |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 00:20 | |
| *** TMM_ <[email protected]> has joined #f4pga | 00:20 | |
| *** lopsided98 <lopsided98!~quassel@2601:18c:8380:79f0:ba27:ebff:fe5e:6b6e> has quit IRC (Ping timeout: 244 seconds) | 02:38 | |
| *** lopsided98 <lopsided98!~quassel@2601:18c:8380:74b0:ba27:ebff:fe5e:6b6e> has joined #f4pga | 02:55 | |
| *** lopsided98 <lopsided98!~quassel@2601:18c:8380:74b0:ba27:ebff:fe5e:6b6e> has quit IRC (Ping timeout: 244 seconds) | 04:39 | |
| *** indy <[email protected]> has quit IRC (Ping timeout: 252 seconds) | 05:25 | |
| *** lopsided98 <lopsided98!~quassel@2601:18c:8380:74b0:ba27:ebff:fe5e:6b6e> has joined #f4pga | 05:48 | |
| *** indy <[email protected]> has joined #f4pga | 06:03 | |
| *** indy <[email protected]> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in) | 06:33 | |
| *** indy <[email protected]> has joined #f4pga | 06:34 | |
| *** indy <[email protected]> has quit IRC (Ping timeout: 248 seconds) | 07:07 | |
| *** indy <[email protected]> has joined #f4pga | 07:09 | |
| *** lopsided98 <lopsided98!~quassel@2601:18c:8380:74b0:ba27:ebff:fe5e:6b6e> has quit IRC (Ping timeout: 244 seconds) | 10:02 | |
| *** lopsided98 <lopsided98!~quassel@2601:18c:8380:74b0:ba27:ebff:fe5e:6b6e> has joined #f4pga | 10:02 | |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 12:59 | |
| *** TMM_ <[email protected]> has joined #f4pga | 12:59 | |
| *** lopsided98 <lopsided98!~quassel@2601:18c:8380:74b0:ba27:ebff:fe5e:6b6e> has quit IRC (Ping timeout: 244 seconds) | 14:37 | |
| *** lopsided98 <lopsided98!~quassel@2601:18c:8380:74b0:ba27:ebff:fe5e:6b6e> has joined #f4pga | 14:52 | |
| *** lopsided98 <lopsided98!~quassel@2601:18c:8380:74b0:ba27:ebff:fe5e:6b6e> has quit IRC (Quit: Disconnected) | 15:46 | |
| cr1901 | Is there a way to squelch the "YOSYS_*_SCRIPT is..." messages that appear recently when running cmake to reconfigure f4pga-arch-defs? | 17:27 |
|---|---|---|
| josuah | cr1901: does it flood the terminal and prevent you to see the meaningful warnings? | 17:35 |
| cr1901 | josuah: I can see warnings fine (they are marked in yellow). It's just that I thought CMake got stuck in an infinite loop because it took a while before the message changed to another directory/path :P | 17:40 |
| cr1901 | The CMake stuff for f4pga breaks easily IME. To the extent that after each pull from main I delete CMakeCache.txt and reconf | 17:49 |
| F4PGASlackBridge | <umartinezcorral> @cr1901 you mean https://github.com/SymbiFlow/f4pga-arch-defs/blob/main/common/cmake/devices.cmake#L1452 and https://github.com/SymbiFlow/f4pga-arch-defs/blob/main/common/cmake/devices.cmake#L1463 ? | 18:03 |
| cr1901 | yes those | 18:04 |
| cr1901 | are they new? | 18:04 |
| cr1901 | (ahh yes they are) | 18:04 |
| F4PGASlackBridge | <umartinezcorral> Yes. | 18:04 |
| cr1901 | well, it's more "cmake is <redacted> that breaks if you stare at it wrong" than "lots of info messages are bad" | 18:05 |
| cr1901 | I just genuinely thought it was a cmake infinite loop | 18:05 |
| F4PGASlackBridge | <umartinezcorral> Previously, those paths were hardcoded in the CMake files, because they were located in the same repo. Now, the scripts were moved to the f4pga package, so the cmake files need to query the package about the location of the TCL files for the arch. The reason it's shown so many times is because cmake traverses the whole repo, and creates all the targets, even though you only need/want to run one of them. | 18:06 |
| F4PGASlackBridge | <umartinezcorral> So, it's not an infinite loop, but the messages being printed dozens/hundreds of times, due to how cmake works/is used in the arch-defs repo. | 18:07 |
| F4PGASlackBridge | <umartinezcorral> We can remove those messages or make them for debugging only, should it be annoying. | 18:07 |
| F4PGASlackBridge | <umartinezcorral> On the big picture, we would like to improve how cmake is used in the arch-defs repo, to better separate the tasks/duties. | 18:08 |
| * cr1901 nods | 18:09 | |
| F4PGASlackBridge | <umartinezcorral> Currently, the cmake files in arch-defs are used for three main tasks: generating assets, running tests and creating packages. We have separated CI jobs for each of them, but the cmake files need to be rethought accordingly. | 18:10 |
| cr1901 | I'm just make sure things still build after I update | 18:10 |
| cr1901 | /home/william/Projects/FPGA/yosys/share/plugins/xdc.so: undefined symbol: _ZN5Yosys5RTLIL4Cell8setParamENS0_8IdStringENS0_5ConstE | 18:11 |
| cr1901 | hmmm, wonder what yosys commit I need | 18:11 |
| * cr1901 uses an external yosys, but doesn't bother building the plugins b/c they're too difficult to build locally | 18:11 | |
| F4PGASlackBridge | <umartinezcorral> With a recent (main) version of f4pga, the arch-defs CI is working ok. So, just bootstrap the conda env in arch-defs and install main f4pga there. If you use an older version of the arch-defs repo, you might need an older version of the f4pga package. We keep track of "combinations that we tested" in https://f4pga.readthedocs.io/en/latest/development/changes.html. | 18:12 |
| F4PGASlackBridge | <umartinezcorral> See https://github.com/chipsalliance/f4pga/pull/621 | 18:13 |
| F4PGASlackBridge | <umartinezcorral> E.g. arch-defs 24e8f73 and f4pga 2d8d857 are known to work. | 18:13 |
| F4PGASlackBridge | <umartinezcorral> > _uses an external yosys, but doesn't bother building the plugins b/c they're too difficult to build locally_ Is this a rethoric statement about yourself or an actual problem in some of the repos? | 18:15 |
| cr1901 | actual problem, tho I guess I could try again | 18:25 |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has quit IRC (Quit: No Ping reply in 180 seconds.) | 20:03 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has joined #f4pga | 20:06 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!