2.77.3 (faustgen 1.73) appears to have broken svg generation on Windows; it works fine with faust 2.74.3 (faustgen 1.71)

[eleses]

After updating to faustgen 1.73 (which uses faust 2.77.3) "view SVG diagram" no longer works for me, just displays some error message. And indeed the path that it complains about is non-existent. Rolling back to faustgen 1.71 (which uses faust 2.74.3) fixes it for me. I suppose it's due to this change mentioned in the changelog of faust 2.77.3.

Remove undeeded SVG generation in faustgen.

Perhaps that wasn't so unnecessary after all.

By the way, "view libraries" never really worked in the Windows version of faustgen, as far as I can tell.

[sletz]

This commit solved another issue and SVG generation still works on macOS. Can you send the screenshot of the error message you get ?

[eleses]

It's just Windows popping up an error message box that
C:\Users\%USERNAME%\AppData\Local\Temp\faustgen-%NUMBER%-svg\process.svg is not found. Where %NUMBER% is some number. This is surely in response to start being called on the svg.

And indeed the faustgen-%NUMBER%-svg folder is no longer generated on Windows in the newest version of faustgen. I manually checked from the Windows Explorer. It's not some naming error, no folder whatsoever gets created in Local\Temp by the newest version.

[sletz]

Thanks. TBH the fausgen~ Windows version would need a bit of refresh. Are you able to build the code yourself and possibly debug ?

[eleses]

Here is the Max console when it fails (on some trivial example) if it's of any help.

[sletz]

Unfortunately I don't have a ready Windows machine anymore. You can possibly:

• fork the Faust project
• put back the code from "Remove undeeded SVG generation in faustgen." commit
• build the binaries using the libfaust action: https://github.com/grame-cncm/faust/actions/workflows/libfaust.yml
• test the Windows fausgen~ version