[Cygwin only]: Configuration error: Output not specified about odr-dabmod HOT 4 CLOSED

Huh, maybe a cygwin-specific thing... @LarsHaack are you able to look into that?

from odr-dabmod.

Command line argument parsing has a general issue in the cygwin build.
The call to getopt() does not detect any valid arguments if you start the command line with the input filename.
cygwin's getopt() implementation stops parsing after the first 'non-option' argument. From what I read this seemed to be the standard behavior of getopt() in all initial implementations.
To allow non-option arguments not only at the and of the arguments is an extension that is available in Linux but not in cygwin.

For the current cygwin build it means you have to give the input filename as the last command line argument.

$ ./odr-dabmod.exe -f /dev/null test.eti
Works for me.

   Input
 Type: file
 Source: test.eti
Output
 Name: /dev/null
 Sampling rate: 2.0480 MHz
Configuration parsed. Starting up version v2.4.1-3-gb977837
ERROR Could not set priority for modulator:134
     Setting up timestamp decoder with 0 offset
     Input file format: raw, length: 30720000, nb frames: 5000
     End of file reached.
     modulator stopped.

Unfortunately I have no idea how to get the expected behavior into the cygwin world.

from odr-dabmod.

Thanks for your insight! Maybe the variant we use is a GNU variant, different from POSIX.
We could "fix" this by updating the help screen and documentation, I don't think it's worth investing a lot of time into this.

from odr-dabmod.

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.

from odr-dabmod.