Perl Oasis 0.3 released

jplindstrom on 2003-06-01T17:52:41

New version of Perl Oasis available.

New stuff: Scintilla source viewer and a couple of new supported editors: gVim, EditPlus and PFE in addition to the original UltraEdit.

The Scintilla control acted up when I tried to build a freestanding PerlApp application. Scintilla uses a SciLexer.dll file which is located in the site/lib/auto/... directory tree in the Perl installation. But adding it to the application in that relative location didn't work, nor did adding it in the current directory.

It's strange that Scintilla or Perl (I don't know which sub system does this) can't find the dll when located in the exact same place as it is in my Perl installation.

I ended up placing it outside the application, in the same dir as Oasis.exe itself. Not even adding the location to $ENV{PATH} worked. Oh, well.


Did you try to auto-extract the DLL?

jand on 2003-06-01T20:16:54

Did you try to bind it like this:
--bind SciLexer.dll[file=site\lib\auto\...\SciLexer.dll,extract]
(with the correct full /site/lib/auto path of course)?

Yups

jplindstrom on 2003-06-02T00:12:35

Yes, I made sure the extracted file was next to the Scintilla dll in site/lib/auto/Win32/Scintilla, just as it was in the Perl installation. I really think that should have worked.

I also put it in the current directory, still no dice.

I even tried setting the PATH (since there is no LD_LIBRARY_PATH on Windows) to different locations where it was, but nooo.

Maybe I made some other mistake, that's certainly possible.

Re:Yups

jand on 2003-06-02T11:17:43

The extracted file should be in the main extraction directory (which automatically gets added to the PATH etc.), and not to site/lib/auto/Win32/Scintilla directory, which is where is normally lives. The --bind option quoted in my previous reply should have done this correctly.

Could you run PerlApp again, and send me both the commandline used and the STDOUT/STDERR output via email?

Re:Yups

jplindstrom on 2003-06-02T21:15:18

Thanks, I'll try that when I find the time.

You should note that I use PerlApp 2 so the exact syntax isn't the same.

Re:Yups

jand on 2003-06-02T22:51:21

Ah, ok. I don't think PerlApp 2 supports automatic extraction of bound files. You'll have to manually write it out to a directory on the PATH in order to make it work I guess. In that case it is probably easier to just ship the DLL separately with the executable. The syntax I gave earlier requires PerlApp 4.1 or later I believe.