Hi Lysander,
the enum patch looks good... I will apply it, and also update
parser.patch (which gets applied after regenerating the parser), so
this fix doesn't get wiped out next time the parser is regenerated.
as far as the properties patch, I will need to re-work the build
scripts a bit too, since classpathlist is also used to figure out
which files to copy to the dest directory as part of the build, and
just taking this patch as-is will result in jawin.dll not being
copied to the destination directory.. I guess I should have used a
separate variable for DLL's.
On Nov 23, 2005, at 5:55 PM, Lysander David wrote:
> Hi,
>
> When building objectscript 1.9.2 using sun java
> 1.5.0_05,
>
> I initially get this error:
>
> [javac]
> C:\home\ldavid\explore\os\regexp\orig\oscript-2.9.2\oscript\oscript
> \parser\OscriptParser.java:4765:
> as of release 1.5, 'enum' is a keyword, and may not be
> used as an identifier
> [javac] (try -source 1.4 or lower to use 'enum' as
> an identifier)
> [javac] for (java.util.Enumeration enum =
> jj_expentries.elements(); enum.hasMoreElements();) {
>
>
> After applying the attached enum.pat to
> oscript/oscript/parser/OscriptParser.java
> ( e.g. patch -p0 < enum.pat from the parent of
> oscript and oscom )
> the build can proceed past that error however
> it then fails with this error:
>
> [javac] error: error reading
> C:\home\ldavid\explore\os\regexp\orig\oscript-2.9.2\lib\jawin.dll;
> error in opening zip file
> [javac] 1 error
>
> After applying the attached properties.pat to
> oscom/build.properties
> ( e.g. patch -p0 < properties.pat from the parent of
> oscript and oscom )
> the build can complete successfully.
>
> Lysander
> <enum.pat>
> <properties.pat>
-- Rob
____________________
CONTACT INFORMATION:
email: ro...@ti...
IM: rob@sandjabber
desk: 1 858 552 2946
cell: 1 619 300 9661
|
