Update jGRASP to version 1.7.0. Changes/bug fixes since 1.6.4:
- Some compatibility issues when running under Sun Java 1.5 beta are
resolved. There probably are other problems.
- Some characters with valid font mappings, such as curly double quotes on
Windows, may show up as hex codes in the CSD and Run I/O windows.
- After doing a "find" in the Run I/O window, the cursor may move into the
output region, which will allow editing of previous output, and may lead
to other problems.
- If a "clear" or "File / Open" is done from a CSD window, settings for
the previous file will not be saved, and the file will not be added to
the "Recent Files" menu.
- If text above the screen which contains all bookmarks or breakpoints is
cut, the on-screen text will not be shifted, and the display may be
temporarily corrupted.
- In the jar and documentation generating tools, some of the files are not
stored as relative, and will become absolute when jGRASP is restarted.
- This means that if a project is move, the jar target file and
documentation target directory will not move with it, and will have to
be reset.
- Command paths for compile, run, etc. are not quoted on Windows. This can
cause "C:\Program Files\etc\etc\something.exe" to fail if the file"
C:\Program" exists, for example.
- Selecting both files and the project in the project tab and using "Open"
from the popup menu will cause a harmless crash, and some or all of the
files may not open.
- Switched default debug attacher from shared memory to socket on Windows
NT/2000/XP, since the shared memory attacher tends to lock up under Sun
Java 1.5 beta.
- In a CSD window, undoing edits on a saved file then doing an equal
number of edits will mark the file as unmodified, even though it is
modified. This may cause unexpected behavior, and lost edits.
- In the debugger and workbench, doubles and floats with NaN values will
always be shown in red text (indicating change) even when the values
were previously NaN.
- In 1.6.6, timeouts were added to kill the debugger if it did not respond
for 10 seconds. This proved to be a problem because of modal dialogs. If
jGRASP locks up while using the debugger or workbench, you should kill
the target process externally using Task Manager on Windows, "kill" on
UNIX/Linux, etc.
- Multiple projects can be open simultaneously.
- Workspaces can be saved and loaded.
- Project level run and debug commands are available on the UML window.
- Methods can be invoked while debugging from within the workbench.
- Numerous other small features were added, menus reorganized, etc.
- The default project has been eliminated, and users can now use jGRASP
"projectless".
- Expression evaluation in the Java debugger now supports varargs and
autoboxing/unboxing.
- Values in the Java debugger can now be dragged to anywhere and released
to pop up a "view by name" viewer.
- Shortcut operators -- && || ?: -- can now be used in eval expressions,
method arguments, etc. in the integrated Java debugger.
- Long lines in PostScript printouts may contain added spaces.
- UML print preview fails (display is incorrect) when the size of the
previewed pages is smaller than a certain size.
- Text can be dragged and dropped into compile messages window and jGRASP
messages window, which can result in mangled output.
- Debug "eval" gives incorrect results for == and != when applied to
Objects.
- Printing may crash when part of the text is folded.
- Closing the UML window while compiling from the UML window causes a crash
- Paste of plain text was broken in Beta 3 (rtf still worked though).
- For the Java debugger, watch markers on inaccessible fields are the same
color as the field marker instead of black, which can make them hard to
see
- CLASSPATH is passed to appletviewer commands
- Detailed messages are now given when a compiler or program fails to run
on UNIX/Linux
- A bug that was causing an occasional crash at start-up was fixed
2004-06-06 00:51:25 +02:00
|
|
|
# $NetBSD: Makefile,v 1.5 2004/06/05 22:51:25 jschauma Exp $
|
2004-01-09 20:13:03 +01:00
|
|
|
#
|
|
|
|
|
|
Update jGRASP to version 1.7.0. Changes/bug fixes since 1.6.4:
- Some compatibility issues when running under Sun Java 1.5 beta are
resolved. There probably are other problems.
- Some characters with valid font mappings, such as curly double quotes on
Windows, may show up as hex codes in the CSD and Run I/O windows.
- After doing a "find" in the Run I/O window, the cursor may move into the
output region, which will allow editing of previous output, and may lead
to other problems.
- If a "clear" or "File / Open" is done from a CSD window, settings for
the previous file will not be saved, and the file will not be added to
the "Recent Files" menu.
- If text above the screen which contains all bookmarks or breakpoints is
cut, the on-screen text will not be shifted, and the display may be
temporarily corrupted.
- In the jar and documentation generating tools, some of the files are not
stored as relative, and will become absolute when jGRASP is restarted.
- This means that if a project is move, the jar target file and
documentation target directory will not move with it, and will have to
be reset.
- Command paths for compile, run, etc. are not quoted on Windows. This can
cause "C:\Program Files\etc\etc\something.exe" to fail if the file"
C:\Program" exists, for example.
- Selecting both files and the project in the project tab and using "Open"
from the popup menu will cause a harmless crash, and some or all of the
files may not open.
- Switched default debug attacher from shared memory to socket on Windows
NT/2000/XP, since the shared memory attacher tends to lock up under Sun
Java 1.5 beta.
- In a CSD window, undoing edits on a saved file then doing an equal
number of edits will mark the file as unmodified, even though it is
modified. This may cause unexpected behavior, and lost edits.
- In the debugger and workbench, doubles and floats with NaN values will
always be shown in red text (indicating change) even when the values
were previously NaN.
- In 1.6.6, timeouts were added to kill the debugger if it did not respond
for 10 seconds. This proved to be a problem because of modal dialogs. If
jGRASP locks up while using the debugger or workbench, you should kill
the target process externally using Task Manager on Windows, "kill" on
UNIX/Linux, etc.
- Multiple projects can be open simultaneously.
- Workspaces can be saved and loaded.
- Project level run and debug commands are available on the UML window.
- Methods can be invoked while debugging from within the workbench.
- Numerous other small features were added, menus reorganized, etc.
- The default project has been eliminated, and users can now use jGRASP
"projectless".
- Expression evaluation in the Java debugger now supports varargs and
autoboxing/unboxing.
- Values in the Java debugger can now be dragged to anywhere and released
to pop up a "view by name" viewer.
- Shortcut operators -- && || ?: -- can now be used in eval expressions,
method arguments, etc. in the integrated Java debugger.
- Long lines in PostScript printouts may contain added spaces.
- UML print preview fails (display is incorrect) when the size of the
previewed pages is smaller than a certain size.
- Text can be dragged and dropped into compile messages window and jGRASP
messages window, which can result in mangled output.
- Debug "eval" gives incorrect results for == and != when applied to
Objects.
- Printing may crash when part of the text is folded.
- Closing the UML window while compiling from the UML window causes a crash
- Paste of plain text was broken in Beta 3 (rtf still worked though).
- For the Java debugger, watch markers on inaccessible fields are the same
color as the field marker instead of black, which can make them hard to
see
- CLASSPATH is passed to appletviewer commands
- Detailed messages are now given when a compiler or program fails to run
on UNIX/Linux
- A bug that was causing an occasional crash at start-up was fixed
2004-06-06 00:51:25 +02:00
|
|
|
DISTNAME= jgrasp170
|
|
|
|
|
PKGNAME= jgrasp-1.7.0
|
2004-01-09 20:13:03 +01:00
|
|
|
CATEGORIES= devel
|
|
|
|
|
MASTER_SITES= ftp://ftp.eng.auburn.edu/pub/grasp/jgrasp/
|
|
|
|
|
EXTRACT_SUFX= .zip
|
|
|
|
|
|
|
|
|
|
MAINTAINER= jschauma@NetBSD.org
|
|
|
|
|
HOMEPAGE= http://www.jgrasp.org/
|
|
|
|
|
COMMENT= IDE with support for Software Visualizations
|
|
|
|
|
|
|
|
|
|
WRKSRC= ${WRKDIR}/jgrasp
|
2004-06-03 22:13:03 +02:00
|
|
|
PKG_JVMS_ACCEPTED= sun-jdk13 sun-jdk14 jdk13 jdk14
|
2004-01-09 20:13:03 +01:00
|
|
|
|
|
|
|
|
do-configure:
|
|
|
|
|
${MKDIR} ${WRKSRC}/bin/${LOWER_OPSYS}
|
|
|
|
|
|
|
|
|
|
do-build:
|
|
|
|
|
${CC} ${CFLAGS} -lutil -o ${WRKSRC}/jbin/${LOWER_OPSYS}_run \
|
|
|
|
|
${WRKSRC}/src/linux_run.c
|
2004-05-15 02:37:08 +02:00
|
|
|
${CC} ${CFLAGS} -I${X11BASE}/include \
|
Update jGRASP to version 1.7.0. Changes/bug fixes since 1.6.4:
- Some compatibility issues when running under Sun Java 1.5 beta are
resolved. There probably are other problems.
- Some characters with valid font mappings, such as curly double quotes on
Windows, may show up as hex codes in the CSD and Run I/O windows.
- After doing a "find" in the Run I/O window, the cursor may move into the
output region, which will allow editing of previous output, and may lead
to other problems.
- If a "clear" or "File / Open" is done from a CSD window, settings for
the previous file will not be saved, and the file will not be added to
the "Recent Files" menu.
- If text above the screen which contains all bookmarks or breakpoints is
cut, the on-screen text will not be shifted, and the display may be
temporarily corrupted.
- In the jar and documentation generating tools, some of the files are not
stored as relative, and will become absolute when jGRASP is restarted.
- This means that if a project is move, the jar target file and
documentation target directory will not move with it, and will have to
be reset.
- Command paths for compile, run, etc. are not quoted on Windows. This can
cause "C:\Program Files\etc\etc\something.exe" to fail if the file"
C:\Program" exists, for example.
- Selecting both files and the project in the project tab and using "Open"
from the popup menu will cause a harmless crash, and some or all of the
files may not open.
- Switched default debug attacher from shared memory to socket on Windows
NT/2000/XP, since the shared memory attacher tends to lock up under Sun
Java 1.5 beta.
- In a CSD window, undoing edits on a saved file then doing an equal
number of edits will mark the file as unmodified, even though it is
modified. This may cause unexpected behavior, and lost edits.
- In the debugger and workbench, doubles and floats with NaN values will
always be shown in red text (indicating change) even when the values
were previously NaN.
- In 1.6.6, timeouts were added to kill the debugger if it did not respond
for 10 seconds. This proved to be a problem because of modal dialogs. If
jGRASP locks up while using the debugger or workbench, you should kill
the target process externally using Task Manager on Windows, "kill" on
UNIX/Linux, etc.
- Multiple projects can be open simultaneously.
- Workspaces can be saved and loaded.
- Project level run and debug commands are available on the UML window.
- Methods can be invoked while debugging from within the workbench.
- Numerous other small features were added, menus reorganized, etc.
- The default project has been eliminated, and users can now use jGRASP
"projectless".
- Expression evaluation in the Java debugger now supports varargs and
autoboxing/unboxing.
- Values in the Java debugger can now be dragged to anywhere and released
to pop up a "view by name" viewer.
- Shortcut operators -- && || ?: -- can now be used in eval expressions,
method arguments, etc. in the integrated Java debugger.
- Long lines in PostScript printouts may contain added spaces.
- UML print preview fails (display is incorrect) when the size of the
previewed pages is smaller than a certain size.
- Text can be dragged and dropped into compile messages window and jGRASP
messages window, which can result in mangled output.
- Debug "eval" gives incorrect results for == and != when applied to
Objects.
- Printing may crash when part of the text is folded.
- Closing the UML window while compiling from the UML window causes a crash
- Paste of plain text was broken in Beta 3 (rtf still worked though).
- For the Java debugger, watch markers on inaccessible fields are the same
color as the field marker instead of black, which can make them hard to
see
- CLASSPATH is passed to appletviewer commands
- Detailed messages are now given when a compiler or program fails to run
on UNIX/Linux
- A bug that was causing an occasional crash at start-up was fixed
2004-06-06 00:51:25 +02:00
|
|
|
-L${X11BASE}/lib -Wl,${RPATH_FLAG}${X11BASE}/lib -lX11 \
|
2004-01-09 20:13:03 +01:00
|
|
|
-o ${WRKSRC}/bin/${LOWER_OPSYS}/jgrasp \
|
|
|
|
|
${WRKSRC}/src/linux_exec.c
|
|
|
|
|
|
|
|
|
|
do-install:
|
|
|
|
|
${INSTALL_PROGRAM_DIR} ${PREFIX}/${PKGNAME}
|
|
|
|
|
${INSTALL_PROGRAM_DIR} ${PREFIX}/${PKGNAME}/bin
|
|
|
|
|
${INSTALL_PROGRAM_DIR} ${PREFIX}/${PKGNAME}/bin/${LOWER_OPSYS}
|
|
|
|
|
${INSTALL_PROGRAM_DIR} ${PREFIX}/${PKGNAME}/jbin
|
|
|
|
|
cd ${WRKSRC} && ${PAX} -s ,^./.*bin/.*,, \
|
|
|
|
|
-rw . ${PREFIX}/${PKGNAME}/
|
|
|
|
|
${INSTALL_DATA} ${WRKSRC}/jbin/JGRASP__829J_6h.class \
|
|
|
|
|
${PREFIX}/${PKGNAME}/jbin/
|
|
|
|
|
${INSTALL_PROGRAM} ${WRKSRC}/jbin/${LOWER_OPSYS}_run \
|
|
|
|
|
${PREFIX}/${PKGNAME}/jbin/
|
|
|
|
|
${INSTALL_PROGRAM} ${WRKSRC}/bin/${LOWER_OPSYS}/jgrasp \
|
|
|
|
|
${PREFIX}/${PKGNAME}/bin/${LOWER_OPSYS}/
|
|
|
|
|
${LN} -s ${PREFIX}/${PKGNAME}/bin/${LOWER_OPSYS}/jgrasp \
|
|
|
|
|
${PREFIX}/bin/jgrasp
|
|
|
|
|
|
|
|
|
|
.include "../../mk/java-vm.mk"
|
|
|
|
|
.include "../../mk/bsd.pkg.mk"
|
