-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Cygwin only]: Configuration error: Output not specified #43
Comments
Huh, maybe a cygwin-specific thing... @LarsHaack are you able to look into that? |
Command line argument parsing has a general issue in the cygwin build. For the current cygwin build it means you have to give the input filename as the last command line argument.
Unfortunately I have no idea how to get the expected behavior into the cygwin world. |
Thanks for your insight! Maybe the variant we use is a GNU variant, different from POSIX. |
I've successfully switched to Windows Subsystem for Linux, so I close this issue as I'm no more interested in Cygwin. It works like a charm in WSL2. I can create RAW-files from ETI-Files and do not need to reboot to Linux. |
Although I don't expect to get it fixed by Matthias, I'll report this issue anyway. Maybe another person has an idea what goes wrong here.
Under Cygwin the syntax
$ odr-dabmod.exe foo.eti -f /dev/null
is not working. Of course, I tried other names or paths or other parameters (like format, etc.)I only get
I also tried
cat foo.eti | odr-dabmod.exe /dev/stdin -F /dev/stdout
without any luck.The same syntax in Linux is ok.
Seems this is in DabMod.cpp#300ff
Well, it only works in Cygwin when you are using a config file (
odr-dabmod.exe [configfile.ini] > /dev/null
)The text was updated successfully, but these errors were encountered: