So the 32 vs. 64 bit only come into play during the runtime, right??? Dave
David B. Crain Consultant Software Engineer Editorial & Conversion Systems Lexis-Nexis Phone: 937-865-6800 ext. 56303 -----Original Message----- From: Michael Glavassevich [mailto:[EMAIL PROTECTED] Sent: Friday, September 29, 2006 9:46 AM To: [email protected] Cc: Crain, David B. (LNG-DAY) Subject: Re: Xerces compilation questions Hi Dave, Java compilers generate platform neutral bytecode. If the compilers in both the 32 bit and 64 bit versions are the same I wouldn't expect the bytecode they produce to be different. xjavac wouldn't affect that. Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] "Crain, David B. \(LNG-DAY\)" <[EMAIL PROTECTED]> wrote on 09/29/2006 06:56:36 AM: > > Michael, > > First of all, thanks for your input. This is helpful. > > Please feel free to forward this to the Xerces mailing list. > > One last question; LexisNexis is now has Sun's 1.5.0 build 06 of the > JDK/JRE, in both 32 and 64 bit versions. This is for Linux. I was > building the Xerces 2.6.0 source for both OS's. I am a little surprised > to see the Xerces' jar files come out the exact same size. Would this be > what you would expect??? This is part of the reason I asked about > xjavac. > > Dave > > David B. Crain > Consultant Software Engineer > Editorial & Conversion Systems > Lexis-Nexis > Phone: 937-865-6800 ext. 56303 > > > -----Original Message----- > From: Michael Glavassevich [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 28, 2006 5:51 PM > To: Crain, David B. (LNG-DAY) > Subject: RE: I got a really stupid question.... > > JDK 1.4+ contains the JAXP APIs and a parser implementation (Crimson, > Xerces, etc...). Usually these will conflict with the JAXP APIs > currently > used by Xerces and also Xerces itself if some other version of it is in > the JDK. Fiddling with the bootclasspath is necessary to keep them from > colliding during the build. When this isn't being done often the build > will fail [1]. > > Would you mind if I forwarded this to the mailing list? I'm sure others > wonder about this as well. > > [1] http://issues.apache.org/jira/browse/XERCESJ-1167 > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [EMAIL PROTECTED] > E-mail: [EMAIL PROTECTED] > > "Crain, David B. \(LNG-DAY\)" <[EMAIL PROTECTED]> wrote on > 09/28/2006 03:43:06 PM: > > > > > I went to the link that you provided and I can see that xjavac is > trying > > to determine what version of javac is being used. Why the bootstrap > > declaration??? > > > > Dave > > > > David B. Crain > > Consultant Software Engineer > > Editorial & Conversion Systems > > Lexis-Nexis > > Phone: 937-865-6800 ext. 56303 > > > > > > -----Original Message----- > > From: Michael Glavassevich [mailto:[EMAIL PROTECTED] > > Sent: Thursday, September 28, 2006 11:47 AM > > To: Crain, David B. (LNG-DAY) > > Subject: Re: I got a really stupid question.... > > > > Hi Dave, > > > > xjavac [1] is an extension to the javac task. Xerces needs this to > > compile > > on JDK 1.4 and above. > > > > [1] > > > http://svn.apache.org/viewvc/xerces/java/trunk/tools/src/XJavac.java?rev > > ision=447706&view=markup > > > > Michael Glavassevich > > XML Parser Development > > IBM Toronto Lab > > E-mail: [EMAIL PROTECTED] > > E-mail: [EMAIL PROTECTED] > > > > "Crain, David B. \(LNG-DAY\)" <[EMAIL PROTECTED]> wrote on > > 09/28/2006 10:38:32 AM: > > > > > > > > Michael, > > > > > > I have been building a couple of older versions of the Xerces source > > > code with various version of the JDK/SDK. > > > > > > The question is, ?what is xjavac???? I did pull it down and have it > > > set-up in a tools directory, but I really do not know what it does. > > > I get the feeling that it some how interacts with ?javac? since we > > > have to define where the JDK/SDK are installed, but I am not sure. > > > > > > Dave > > > > > > David B. Crain > > > Consultant Software Engineer > > > Editorial & Conversion Systems > > > Lexis-Nexis > > > Phone: 937-865-6800 ext. 56303 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
