What is the reason to build an executable every night? IMO, the building of an exe should not be something that is done automatically and unattended.


>In an attempt to automate compilation of our foxpro project, we tried
>to compile from a script that runs nightly unattended.
>
>We looked into several possibilities,
>
>1. Command line: “vfp8 …” that will take a project and compiles to an
>.exe or .app.
> Nope, foxpro command line does not allow compilation switches.
>
>2. Command line calls “vfp8.exe build.prg” and put all building logic
>inside build.prg:
>-------------------
>BUILD EXE (ProjectPathName + ".exe") FROM (ProjectPathName + ".pjx") RECOMPILE
>quit
>-------------------
>
>It works. But one more issue:
>
>If there are errors in the compilations, such as a missed function
>definition, Foxpro will popup a dialog “Unable to Find such and such…”
>"Locate, ignore, ignore all, cancel".
>
>
>This is quite annoying because we would love to parse the log
>afterwards automatically. Having to have some one staying there clicking
>ignoring is not quite automation.
>
>Suggestions will be appreciated.
>
>Yun