DBI consists of both Perl code and XS code, as do most of the DBD::*
drivers.
As such, you will either need to compile the source when you install your
app
or build DBI and DBD::* for each target architecture and install the built
version
of DBI when you install your app.

Not exactly hopeless, but annoying.

-- 
j.
 
James FitzGibbon                     
Consultant, Ajilon Services, TTS-3D@TPN4H 
[EMAIL PROTECTED] 
voice/fax 612-761-6121/4277
 


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 20, 2002 5:17 PM
> To: Kokarski, Anton
> Cc: [EMAIL PROTECTED]
> Subject: Re[2]: Use Lib
> 
> 
> DBI is just being untarred and put in the modules dir.  No make or
> anything like that.  It's for a program that will run on
> Linux/Unix/Windows and I don't want to have to require the compiling
> or installation of DBI with the program.
> 
> It may be hopeless...
> 
> 
>  
> Nick Hendler
> [EMAIL PROTECTED]
> 
> _________________________________________
> 
> From:    Kokarski, Anton <[EMAIL PROTECTED]>
> Date:    Wednesday, March 20, 2002 
> Time:    6:10:48 PM
> Subject: Use Lib
> 
> It would probably be best to give some detail on your 
> problem. Such as how
> you are installing dbi or other dbd modules and location
> 
> Thank you,
> Anton Kokarski
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 20, 2002 3:02 PM
> To: [EMAIL PROTECTED]
> Subject: Use Lib
> 
> 
> Is it possible to load DBI using the 'use lib' function such as:
> 
> use lib "./modules";
> use DBI;
> 
> I want to write a program that will utilize DBI but the program will
> be installed on various machines where DBI is not available in the
> server install (not in @INC).  For those servers where DBI is not in
> @INC, I would be using DBD::CSV and where it is available the db of
> choice will be MySQL (if installed).
> 
> I have had luck using the 'use lib' with the various DBDs, but no luck
> with DBI itself.  Any thoughts/mods?
> 
> 
>  
> Nick Hendler
> [EMAIL PROTECTED]
> 

Reply via email to