Re: Path treatment issue Octave on mingw : pkg.m

[Tatsuro MATSUOKA]

Dear Michael and Benjamin

I have imported your 'MSYS path to EXEC_PATH at startup'
and newly defined and used fullfilepkg.m
in pkg.m. In fullfilepkg.m, filesep='/' not but '\'.
All 'fullfile's in pkg.m are replaced by fullfilepkg.
After that pkg works well but mkoctfile --mex is not still
working yet.

Thank you to Michael and Benjamin Lindner for your
helpful advices.

The metis is now unrequired for octave buliding.
I still am now struggling with building hdf5 on  mingw. 
Pherhaps the bug of the configure script of 
--without-Stream-VFD does not work. So in H5FDstream.c
I wrote 
#undef H5_HAVE_STREAM

I have builded libhdf5.a but perhaps it seem to be not
enough.

Sincerely,

T. Matsuoka    

> You should have a look at how this is handled under
> MSVC, problems
> are the same. To run pkg.m, you need a POSIX shell.
> That's why pkg.m
> has been modified to use "shell" instead of "system"
> to run system calls.
> This acts as a wrapper around MSYS shell (using C
> system doesn't run
> the command in a shell). What I do then is to add
> MSYS path to EXEC_PATH
> at startup (see
> octave-forge/admin/Windows/msvc/octaverc.win); then
> everything runs fine.
> 
> Michael.


--------------------------------------
Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar
http://pr.mail.yahoo.co.jp/toolbar/