c. wrote:
>
> On 27 Mar 2012, at 20:10, Philip Nienhuis wrote:
>
>>> b = a (cellfun(@(x) ismember (x.name, pkg_names), a, "unif", true));
>>
>> ...which has many variations. One probably could even make this into a
>> two-liner.
>>
>> But how does this help to get the full path to the arch-dependent .oct
>> installation dir?
>
> I might be mistaken, but isn't that in
>
> b{2}.archprefix
>
> ?
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.
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.
P.
------------------------------------------------------------------------------
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
