Community
Participate
Working Groups
I want to build a plain command line app. Setting this up with 'PDE - Product Configuration' and then building using 'Eclipse Product Export Wizard', the normal eclipse.exe is copied (and renamed if desired - for this example to foo.exe). The expectation is now to be able to use foo.exe as any commandline app - piping in/out of stdout/err etc, checking the exit code etc etc. Currently I have identified a few issues: 1) Starting the exe, it is not synchronous to my shell. This is because the exe file is linked to the 'windows' subsystem rather than the 'console' subsystem. This can be worked around by using a tool such as 'dumpbin'. 2) Exit code processing is not transparent. a) exit codes 23 and 24 are specially recognized, and b) any exit code other than those and 0 will pop up a messagebox. Whatever the exit code, the final exit code to the calling app will be 0. A suggestion is to make it possible to indicate in the product configuration wizard that the intended use is as a 'normal' console app, so that the copied launcher has correct console subsystem linking, as well as becoming completely exit code transparent.
It seems that you might be better off writing your own executable, or simply directly start java with -jar startup.jar.
Support for this is currently being investigated. Andrew, is there another bug report tracking this?
1) See bug 173962 2) Propagation of the exit code has been fixed, see bug 173900 *** This bug has been marked as a duplicate of bug 173962 ***