----- Original Message -----
From: "SANDHYA PAWAR" <[EMAIL PROTECTED]>
To: "Sisyphus" <[EMAIL PROTECTED]>
Sent: Wednesday, June 28, 2006 11:50 PM
Subject: RE: Inline::java question
>
> Hey...Thanks a lot yaar!!!!! Where were you ...
>
You're welcome. Bear in mind that once you got your environment set up
correctly, Inline::Java installed flawlessly and easily - the credit for
which goes to the fellow that wrote Inline::Java and made it such a simple
installation.
> Module 'Inline::java' has been installed ...
> And I am able to use 'use JDBC'
>
> I was struggling since 3-4 days for this ..
>
> Just one question ... I used default values at the cmd ..
>
> C:\Perl\lib\Inline>perl Makefile.PL J2SDK=C:\J2SDK1.4.2
>
> Welcome to the Inline::Java installation procedure.
>
> Default J2SDK for Inline::Java will be 'C:\J2SDK1.4.2'.
> See module documentation for information on how to use a different J2SDK
> or change this default value.
>
> Checking if your kit is complete...
> Looks good
>
> Inline::Java can use a JNI extension that allows the Java Virtual
> Machine
> (JVM) to be dynamically linked with Perl instead of running as a
> separate
> process. The use of this extension is optional, and building it still
> allows Inline::Java to run the JVM in the default (separate process)
> fashion.
> Note: You need a C compiler to build the extension.
> Note: You must build the extension if you wish to use PerlNatives or
> PerlInterpreter.
> Do you wish to build the JNI extension? [y] y
>
> Building JNI extension.
>
> 1) C:\J2SDK1.4.2\jre\bin\client
> 2) C:\J2SDK1.4.2\jre\bin\server
> Please select from the above list which 'jvm.dll' to use: [1] 1
>
> Building with:
> C:\J2SDK1.4.2\include\jni.h
> C:\J2SDK1.4.2\include\win32\jni_md.h
> C:\J2SDK1.4.2\lib\jvm.lib
> C:\J2SDK1.4.2\jre\bin\client\jvm.dll
>
> Note: In order for Inline::Java to use the JNI extension, you will need
> to
> use the JNI configuration option or set the PERL_INLINE_JAVA_JNI
> environment
> variable to a true value. You will also need to add the following
> directories
> to your PATH environment variable:
> C:\J2SDK1.4.2\jre\bin
> C:\J2SDK1.4.2\jre\bin\client
> See README.JNI for more information.
>
You might need to take notice of the above advice and do as directed - if
you haven't already :-)
> The PerlNatives extension allows for callbacks to be defined as native
> Java methods. It is still EXPERIMENTAL and may not build or work
> properly
> on all platforms. See documentation for more details.
> Note: PerlNatives requires J2SDK 1.4 or greater.
> Do you wish to build the PerlNatives extension? [n] n
>
> The PerlInterpreter extension allows Inline::Java to be loaded directly
> from
> Java using an embedded Perl interpreter. It is still EXPERIMENTAL and
> may not build or work properly on all platforms. See documentation for
> more details.
> Do you wish to build the PerlInterpreter extension? [n] n
>
> Writing Makefile for Inline::Java::JNI
> Writing Makefile for Inline::Java
>
>
> Is it ok ?
Looks ok to me. I take it the other steps proceeded ok.
> Will it create me problem further ??
>
Only time will tell :-)
If it does pose problems be sure to post to the list about it.
Also be aware that *every* time you open a new console you have to run
'vcvars32.bat' if you want to use the VC6 compiler in that console.
('vcvars32.bat' sets things up *only* in the console in which it is run ...
it won't have any affect on any other open consoles, or on any consoles that
you might open in the future.)
And please - next time you build a module, do so in some place *other* than
your perl installation tree :-)
I would suggest creating a separate build directory, say 'C:\build'. Then,
if you want to build (eg) 'Inline-Java-0.51' you would extract
'Inline-Java-0.51.tar.gz' to 'C:\build'. Doing so will create the folder
'C:\build\Inline-Java-0.51'. Then you 'cd' to 'C:\build\Inline-Java-0.51'
and run 'perl Makefile.PL J2SDK=C:\J2SDK1.4.2', 'nmake java', 'nmake test',
'nmake install'.
Cheers,
Rob
