Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wostart #345

Merged
merged 2 commits into from
Dec 19, 2012
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions Utilities/WOStart/Makefile
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
include make.config

java${EXESUFFIX}: java.o java_md.o manifest_info.o WOStart.o
${CC} ${CFLAGS} -o java${EXESUFFIX} *.o ${LIBS}


.c.o:
${CC} ${CFLAGS} -c $<

.cpp.o:
${CC} ${CFLAGS} -c $<
13 changes: 13 additions & 0 deletions Utilities/WOStart/ReadMe.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
WOStart.exe

This is a modified java.exe for Windows that behaves identically like
the <Appname>.cmd startup script.

Using this has some advandages

- Only one process per App (no sub processes from cmd startup script)
- ProcessName is the name of your app (rather than java.exe)
- No problems due to classpath length

As with java.exe the current VM is read from registry. For now, this works
up to Java6.
Loading