Conversation
I want to get this to build with MSVC, which doesn't support these.
I don't expect this to be actively maintained: I just figure that it may be useful to someone else until it eventually bitrots.
This EXE was compiled with MSVC using the Windows XP compatible v141_xp toolchain and the static runtime library. It should have no problem running on users' PCs. I also deleted a junk EXE that was lying around.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've replaced the fdp2bin Windows executable with a 32-bit version, in response to a user not being able to run the previous 64-bit executable.
I didn't want to install an entire extra MSYS2 toolchain to build 32-bit executables, so I set about getting fdp2bin to build with MSVC. I figure that I might as well contribute the changes needed for this back upstream.