gsch2pcb stores the list of schematics as a space-separated list, and doesn't appear to support any form of escaping.
Since gsch2pcb launches gnetlist using g_spawn_command_line_sync () which processes the command-line from a string passed to it.. it seems possible that things might "just work" with judicious placement of "" quotes around schematic filenames.
Quoting the docs for that function:
On Windows, please note the implications of g_shell_parse_argv() parsing command_line. Parsing is done according to Unix shell rules, not Windows command interpreter rules. Space is a separator, and backslashes are special. Thus you cannot simply pass a command_line containing canonical Windows paths, like "c:\\program files\\app\\app.exe", as the backslashes will be eaten, and the space will act as a separator. You need to enclose such paths with single quotes, like "'c:\\program files\\app\\app.exe' 'e:\\folder\\argument.txt'".
This is also a gsch2pcb bug...
gsch2pcb stores the list of schematics as a space-separated list, and doesn't appear to support any form of escaping.
Since gsch2pcb launches gnetlist using g_spawn_ command_ line_sync () which processes the command-line from a string passed to it.. it seems possible that things might "just work" with judicious placement of "" quotes around schematic filenames.
Quoting the docs for that function:
On Windows, please note the implications of g_shell_ parse_argv( ) parsing command_line. Parsing is done according to Unix shell rules, not Windows command interpreter rules. Space is a separator, and backslashes are special. Thus you cannot simply pass a command_line containing canonical Windows paths, like "c:\\program files\\ app\\app. exe", as the backslashes will be eaten, and the space will act as a separator. You need to enclose such paths with single quotes, like "'c:\\program files\\ app\\app. exe' 'e:\\folder\ \argument. txt'".