Me: Dan, are you sure your build instruction is complete?
Dan: I don’t know. What’s your problem?
Me: I followed the instructions in your email, but can’t find the executable.
Dan: Did you download IIOP.NET and build it?
Me: Yes.
Dan: Did you run vcvars32.bat to setup the environment variables?
Me: Yes.
Dan: (walks over and saw my xterms (I used to run Cygwin bashes in CMD consoles, I run Cygwin xterms now)) Could you open a Windows command prompt?
Me: Sure! (Opened one) Redo everything, ... No. Still have the problem.
Dan: OK. Let’s move on. Have you updated your MPC recently?
Me: I don’t remember when I last did that. It won’t hurt to run cvs up now. (Did it.)
Dan: Now rerun MPC...
Me: (mpc.pl -type vc71 foo.mwc)... redo the build... (devenv foo.sln /build Debug)... Yes. That fixed it. Thanks.
Forget about the cool stuff that I mentioned for a moment, and let’s talk about the abuse that Cygwin users take in situations like this. I’m used to it and usually go with the flow when it comes to opening a CMD prompt. However in all these years of opening up a CMD window and redoing stuff, not once had the problem been traced back to Cygwin.
I don’t mean to pick on Dan. (Others do the same.) I just want to point out the not so obvious fact that Cygwin is rarely the cause of any problems on my machine.
Previous Topic
