Yann Papouin wrote:
inkscape.exe can be used in command line, for a .bat file for example
Yes, but that's not what this discussion was about (and you don't even
have to compile it as a console application for that). The problem is
that Inkscape prints debug messages to stdout. On Linux you can easily
see these by starting Inkscape from a shell, but on Windows you won't
see them, even if you start Inkscape from the commandline. This prevents
most Windows users from using this potentially valuable debugging resource.
There are two things you can do to remedy the situation. One is to
compile Inkscape as a console application. This doesn't change it's
behaviour at all, except that Windows does attach a console to its
stdout. The other is to run it through inkscapec.exe. The latter is much
easier for non-developers.