Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
here: http://nco.sourceforge.net/#Binaries you provide 64bit Windows binary and it's nowhere stated that build is for 64bit platform.
As it is most common to provide 32bit binary and then 64bit as addition if possible, please provide 32bit too.
The Windows binaries were targeted for /MACHINE:X86, not for /MACHINE:X64, but there has been some reported problems related to the Microsoft libraries (file msvcr100d.dll in the distribution).
Are you experiencing any problems running NCO with version 4.3.1?
Yes, you are right, msvcr100d.dll is 64bit while nco executables are 32bit
It's current link - 4.3.1
Forgot to answer your question about experience:
sure, it wont run on 32bit system obviously because linked shared library is 64bit
Actually it works fine after deleting msvcr100d.dll
So I guess I already had that library
Yes, that is the solution for now, deleting the distributed 64 bit msvcr100d.dll in case you have a 32 bit system (that must have the 32 bit msvcr100d.dll ) , as reported here too
I will update the binaries to have a completely static version.
I don't know why you link debug version of library. If you compile all components in "release" mode, then you won't need this library (nor any other) but simply provide a link to MSVC 20010 Redistributable Package (http://www.microsoft.com/en-us/download/details.aspx?id=8328) for users that doesn't have 2010 C Runtime Library already.
Libraries with "d" appendix aren't redistributable, and end user would hardly need debug version.
Hope it helps
thanks for the explanation, but just providing a static build will solve all this 32/64/debug/release DLL issues :-)
I uploaded new NCO 4.3.1 Windows binaries, all static, no DLL dependencies, you can give it a try if you wish