It is possible to make wxCLIPS load your application and start it up without the development window appearing. You need to define a function called app-on-init, which takes no arguments but must return the identifier of the top-level frame.
Now start your application as follows:
wxclips -clips load.clp -startThe file after the -clips switch is 'batched', which can be slow for a large file. Make the file small, with one or more calls to load definition files, followed by any function calls necessary (for example to register event handlers). If the file contains no CLIPS commands which should be executed immediately, use the -load switch instead.
The -start switch tells wxCLIPS to call the function app-on-init, and use the returned frame identifier as the top level window. The development window will not be displayed.
If you want wxCLIPS to start in a particular directory, you can use the -dir switch to chdir to a directory. This is useful to avoid the need for specifying absolute pathnames in your CLIPS code.
See also Running wxCLIPS.