Re: [MacPerl-Porters] external libs within the resource

> - all modules are sucked into the binary.

that is the main point and my standalone builder does this
very job

> - all XS libraries (well, most anyways) are stuck in
>   a folder called "shared libs". the folder hierarchy
>   is the same as in the MacPerl folder.

partly
In the moment I copy all XS libraries to ":lib:shared libs:"
without creating any further structure within ":shared libs:"
(which is no problem unless two XS libraries use the same name)

But this is also the point I'd like to change in a future
version. Rather than having the XS libaries visible in this
folder I think about copying them too into the binary standalone.
I'd love to see a single application for some purposes.


> - all user libs are sucked into the binary.

In the moment I don't care.
You can copy them too into the binary to hide them
or have them accessible still so you can adjust things.

  use lib './lib';
  require "myConfig.pl";

myConfig.pl is within your lib folder an can be configured.

But the last point about user lib is still in progress...


Axel