Re: Compile of M breaks on MInterface files (m4.bat)
Vadim Zeitlin <[email protected]>
| Newsgroups | gmane.mail.mahogany.user |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 23 Sep 2004 15:53:51 -0600 (Mountain Daylight Time) Ed Vazquez <[email protected]> wrote: EV> With VS .NET 2003, there seems to be an issue in the M portion EV> of the build that deletes the MInterface.h and MInterface.cpp EV> files, leaving zero byte files in their place. Although I didn't see it myself, I did have some reports about problems with m4.bat from other people but never really investigated it because it was simple to fix by just copying the files around... EV> I tested this by running the m4.bat script on the command line, EV> which created the files, and then monitoring the size of the EV> file manually with DIR. As soon as the M build starts, the two EV> files get zeroed out. Which causes the entire build to fail. Two questions: do you have m4 on your system? What is your COMSPEC environment variable value? EV> My manual workaround was to run the command line, copy the .cpp EV> file to the modules sub-directory and then as soon as the M EV> section started, re-run the command line to generate the .h EV> file. If you copy MInterface.{h|cpp}.m4 to MInterface.{h.cpp} and touch the latter files, they shouldn't be erased any longer as VS shouldn't rebuild them if they're more recent than their sources, so this must fix the problem. I still don't understand why did it arise in the first place however... Regards, VZ ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php