Re^2: Bundling Sybase dll using perl2exe

Dear Monks, Thanks for your reply, I really don't want to make the Sybase Open Client as a requirement and if possible bundle the required dll/obj files with my appplication. The error which I get when I bundle most of the dll's is The context allocation routine failed when it tried to load localization files!! One or more following problems may caused the failure Your sybase home directory is c:\sql10. Your sybase home directory is c:\sql10. Check the environment variable SYBASE if it is not the one you want! Check the environment variable SYBASE if it is not the one you want! Cannot access file c:\sql10\ini\objectid.dat I have bundled the objectid.dat file also in my application exe, I still get this error as well DBD_alloc method fails. Thanks, Mansi

Comment on Re^2: Bundling Sybase dll using perl2exe

Replies are listed 'Best First'.
Re^3: Bundling Sybase dll using perl2exe by jfroebe (Parson) on Dec 10, 2013 at 13:47 UTC
The official method is to install OpenClient. If you want a self contained binary, you're basically out of luck. Another option is to use Sybase's JDBC driver (jConnect) with DBD::JDBC. However, using DBD::JDBC will require you to have Java installed somewhere... then it comes down to, if you require Java, why are you using Perl? Catch-22 Jason L. Froebe Blog, Tech Blog	[reply]
Re^3: Bundling Sybase dll using perl2exe by Anonymous Monk on Dec 10, 2013 at 06:44 UTC
Just an update, the exact error for alloc method is: DBD::Sybase initialize :cx_ctx_alloc(112) failed at PERL2EXE/STORAGE/Dynaloader.pm line 214.	[reply]
Re^4: Bundling Sybase dll using perl2exe by mpeppler (Vicar) on Dec 10, 2013 at 16:21 UTC
As jfroebe says - a Sybase client app requires a whole slew of files, locale files, charset files, you name it. There's no way to run a C-based client without them. Michael	[reply]