T
Torsten Mohr
Hi,
i managed to compile a static version of perl, now
i have a perl58.lib that i can link with own programs.
i did this by compiling perl from the sources with the
"dmake" utility and adding an error command just after
the DLL is created.
I then took that command and changed some parameters
(e.g. from -dll to -lib).
There are lots of warnings, but it seems to work.
The problem is, that when i let the LIB execute
a perl script, it works ok.
What i'd now also like to do is to let the script
use the "use" command.
But as there are no *.pm files anywhere, this fails.
Can i somehow either:
- add the perl modules i need to the LIB somehow and change
the "use" command to not load the modules from the
file system, but from internal memory
or
- break up the hierarchy of "use" and generate ONE large
script that includes everything.
Is something like this possible?
Thanks for any hints,
Torsten.
i managed to compile a static version of perl, now
i have a perl58.lib that i can link with own programs.
i did this by compiling perl from the sources with the
"dmake" utility and adding an error command just after
the DLL is created.
I then took that command and changed some parameters
(e.g. from -dll to -lib).
There are lots of warnings, but it seems to work.
The problem is, that when i let the LIB execute
a perl script, it works ok.
What i'd now also like to do is to let the script
use the "use" command.
But as there are no *.pm files anywhere, this fails.
Can i somehow either:
- add the perl modules i need to the LIB somehow and change
the "use" command to not load the modules from the
file system, but from internal memory
or
- break up the hierarchy of "use" and generate ONE large
script that includes everything.
Is something like this possible?
Thanks for any hints,
Torsten.