On 27 Mar 2012, at 20:40, Philip Nienhuis wrote:
> Only partly, that goes only to the <package_name> subdir. Inside, there's
> another one. To get there you'll need to get info from octave_config_info, as
> outlined in my post from yesterday.
I might be confused by the name but I think archprefix was intended to point to
the directory with the architecture dependent files rather than just the
package subdir ...
that is handled by the files
scripts/pkg/private/getarchdir.m
scripts/pkg/private/getarch.m
scripts/pkg/private/getarchprefix.m
>
> Would you have any hints along the lines of
>
> b{:}.archprefix ## doesn't work
>
> i.e., how to get that info for multiple pkgs?
> I don't see how to avoid some for loop here.
cellfun (@(x) x.prefix, b, "unif", false)
>
> P.
c.
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev
