I'm have been trying to debug FFmpeg to help somebody with another discussion. But no luck until now:
- I have installed MSYS2, VSCode, ... following this tutorial. Btw if anybody ever wants to reproduce it, you will to install other tools also (gcc compiler ...): I have logged an issue for that.
- This way I was able to build a debug version of FFmpeg on my Windows 10 portable. And that part is ok, since I can start FFmpeg from Visual Studio Code and launch the Main method in the debugger.
- But to be able to debug the stdin/stdout/stderr streams I need to spawn an FFmegg process from a NodeJs application (i.e. Node-RED) and attach Visual Studio to that running FFmpeg process.
- So I had to install NodeJs (and Npm) extra on my MSYS2. Have done (on my 64 bit environment) that using:
And NodeJs seems to be installed correctly, because I can ask NodeJs which version it has:
pacman -S mingw-w64-x86_64-nodejs
- Then I have installed Node-RED using:
Which installs all the files I would expect (remark: the entire filesystem is available under c:\msys64):
cd ~ npm install node-red
- But then I try to run Node-RED but nothing happens (i.e. it logs nothing and the prompt just appears again):
This also doesn't work:
cd ~/node_modules/node-red node node-red/red.js
Remark 1: I had done the same yesterday and then Node-RED started normally (after adding
--userDir /home/admin/node_modules/node-red because Node-RED seems not to be installed in the correct directory). But then I had issues (with shared libraries?) so I have uninstalled Msys2 and done everything all over again. And now it doesn't respond...
Remark 2: when I change e.g. red.js to redxx.js then NodeJs detects that the file doesn't exist:
So I assume I'm always there ...