So I strongly suspect that building on macOS or Ubuntu would avoid this issue.
But assuming that isn't a route that you can follow, I think that there should be a fairly straightforward way of avoiding the issue you are having. Basically you are runnning into an issue because the Eclipse/CDT engine generates an explicit reference to each object file inside your project. And the number of files then explicitly listed causes a command line length issue as already described.
But you should be able to avoid this by modifying the command used to invoke the archiver (arm-none-eabi-ar) utility used to build your library.
First of all, open the Project Properties for your library project, and open the Archiver settings:

What you can then do is replace the use of ${INPUTS} in the "Command Line Pattern" option, which is where the list of filenames effectively gets poked in, with a wildcard definition of your object files.
In your example, all of your objects appear to be contained in a directory called "source". So delete ${INPUTS} and replace it with ./source/*.o :

Then Apply and Close.
If your source files are contained in more than one directory, you will need to specify them all on the line in a similar manner (with a space between each directory/wildcard pattern.
And remember that you will also need to make this change for all Build Configurations (so typically Debug and Release).
Anyway, please let us know if this helps you to resolves your problem.
Regards,
MCUXpresso IDE Support