Apologies, but in the rush to get a master CD out for the Ptolemy
Miniconference Tutorial, there are three small errors that prevent
rebuilding the Ptolemy II 1.0.
These errors primarily affect Windows users who use the Installshield
Windows installer to install Ptolemy II in a directory that has a
space in the pathname, such as
c:\Program Files\Ptolemy\Ptolemy II 1.0
and who want to rebuild Ptolemy II.
I've created new installers and bumped the version number up
to 1.0.1.
I considered creating a patch, but decided that building a patch
would probably cause more trouble on user systems than it is worth.
Users who do not want to rebuild can stick with Ptolemy II 1.0,
there is no need to upgrade to Ptolemy II 1.0.1
People attending the Ptolemy II Miniconference tutorial should
either make the fixes below or install Ptolemy II 1.0.1.
configure.in and configure
--------------------------
Running configure fails if the pathname to the Ptolemy II
installation directory contains one or or more spaces.
To replicate the bug, run the following commands inside bash:
PTII=c:\\Program\ Files\\Ptolemy\\Ptolemy\ II\ 1.0
export PTII
cd "$PTII"
./configure
The following messages will appear in the configure output:
checking for Java 3D... cd: can't cd to ./config
cd: can't cd to /cygdrive/c/Program
checking for javax.sound... cd: can't cd to ./config
sed: can't read confdefs.h: No such file or directory
creating ./config.status
creating mk/ptII.mk
sed: can't read ./mk/ptII.mk.in: No such file or directory
creating bin/ptinvoke
sed: can't read ./bin/ptinvoke.in: No such file or directory
Workaround:
One workaround is to install Ptolemy II in a directory that
does not contain a space. Another workaround might be to
to mount the Ptolemy II home directory as a separate
network drive.
Fix:
Edit $PTII/configure and search for 'cd $' and place double
quotes around the argument to the cd command.
The first couple of 'cd $' commands at lines 670
PTJAVA_DIR=`cd $DEFAULT_JDK; pwd`
and 676
PTJAVA_DIR=`cd $DEFAULT_JDK; pwd`
do not need to be fixed, $DEFAULT_JDK will never have a space in it.
At line 830, change:
cd $srcdir/config
To:
cd "$srcdir/config"
At line 847, change:
cd $startdir
To:
cd "$startdir"
At line 1182, change:
cd $srcdir/config
To:
cd "$srcdir/config"
At line 1195, change:
cd $startdir
To:
cd "$startdir"
At line 1209, change:
cd $srcdir/config
To:
cd "$srcdir/config"
At line 1220, change:
cd $startdir
To:
cd "$startdir"
In theory, similar changes should be made to configure.in,
but most since most developers will not be otherwise modifying
the configuration environment by editing configure.in
running autoconf and generating a new $PTII/configure file,
then editing only $PTII/configure will be sufficient
bin/ptinvoke.in
---------------
There is a similar problem in with space names in
bin/ptinvoke.in
If you run
$PTII/bin/ptjacl
Then you may see:
basename: too many arguments
Try `basename --help' for more information.
The fix is to edit line 129 and change
case "`basename $0`" in
To:
case `basename "$0"` in
and to edit line 228 and change
if [ ! -f $PTJACL_JAR ]; then
To
if [ ! -f "$PTJACL_JAR" ]; then
and then to run
cd "$PTII"/bin
make
ptolemy/configs/makefile
------------------------
Here, the problem is that the Windows installer
does not include introPtiny.htm and vergilConfigurationPtiny.xml.
This problem is not in the ptII1.0.src.tar.gz file, only
in the Windows installer.
The fix is to edit $PTII/ptolemy/configs/makefile and remove these
lines:
introPtiny.htm \
vergilConfigurationPtiny.xml \
An alternative fix is to run these two commands:
touch $PTII/ptolemy/configs/introPtiny.htm
touch $PTII/ptolemy/configs/vergilConfigurationPtiny.xml
-Christopher
----------------------------------------------------------------------------
Posted to the ptolemy-hackers mailing list. Please send administrative
mail for this list to: [EMAIL PROTECTED]
