|
On 5/18/2017 12:30 AM, Russell Haley wrote:
I also wonder out loud if this in all academic now with Linux Subsystem for Windows?
Everybody who wants a Linux-like environment is already on Cygwin.Even if Microsoft is completely honest this time, big corporations have a tendency to lose interest and then you're out of luck. Or a VP may want to show off his/her management skills and 'rationalize' things, 'sunset' some projects.
We'll be stuck with compiling for legacy 32-bit Win32 for a long long long... a super long time. Even after so many years of 64 bit Windows, plenty of stuff have not moved to 64 bits executables.
On Wed, May 17, 2017 at 9:25 AM, Scott Morgan wrote:On 05/17/2017 05:06 PM, KHMan wrote:Often on MSYS or MSYS2 compiled executables would run, and then on Command Prompt it will fail to start. My usual rule is that when the executable is to run outside of the MSYS or MSYS2 environment, copy it out and test it on Command Prompt to make sure it has all the DLLs it needs.Dependency Walker is handy for seeing what DLLs are required for an EXE. http://www.dependencywalker.com/ A bit like the ldd command in Linux. Scott
-- Cheers, Kein-Hong Man (esq.) Selangor, Malaysia