Re: Octave Video Package

[JohnD]

> Message: 2
> Date: Mon, 14 Sep 2015 05:25:11 -0700 (PDT)
> From: PhilipNienhuis <address@hidden>
> To: address@hidden
> Subject: Re: Octave Video Package
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=UTF-8
> 
> PrasannaKumar Muralidharan wrote
> > Hi Renat,
> >
> > Somehow missed to copy octave mailing list, adding it.
> >
> >
> > On 11 September 2015 at 19:07, ??????? ????? &lt;
> 
> > renat-nasyrov@
> 
> > &gt; wrote:
> >> Hi PrasannaKumar,
> >>
> >> Really good idea! Nevertheless, inside that shell binary I should use
> >> "/usr/bin/grep.exe" instead of plain "grep", so when I run
> >> ./configure, I get the following:
> >>
> >> configure: line 419: which: command not found
> >> configure: line 2895: uname: command not found
> >> configure: line 476: tr: command not found
> >> configure: line 2903: uname: command not found
> >> configure: line 3001: sed: command not found ...
> >> And so on. How can I make bash.exe to execute utils from its bin
> >> directory?
> >
> > Adding the folder to PATH enivronment variable will do.
> >
> > I did try that out. Compiled and installed ffmpeg but still the
> > configure script could not locate ffmpeg. Please give it a try and see
> > what happens. Don't have any idea whether it will work for you.
> >
> > Regards,
> > PrasannaKumar
> >
> >>
> >>
> >>
> >> 11.09.2015, 15:25, "PrasannaKumar Muralidharan"
> >> &lt;
> 
> > prasannatsmkumar@
> 
> > &gt;:
> >>
> >> Hi Renat,
> >>
> >>  I see that package "video" needs FFMpeg for Windows, so I have
> >> downloaded  the package for Windows from ffmpeg.org . Anyway, Octave
> >> still cannot find  it on my system. As you can see in pkg log I sent
> >> before, pkg tries to find  *.pc files which are surely cannot be
> >> found in Windows ? all I have is a  bunch of FFMped DLLs. The
> >> question is: how can I make the package "video"
> >>  use these DLLs? Maybe you know where to find a tutorial about
> >> porting Octave  packages under Windows?
> >>
> >>
> >> Compile FFMpeg from source. Inside Octave installation folder there
> >> is bash shell binary (bash.exe). In that shell navigate to FFMpeg
> >> source code, run ./configure, make and make install. Once that is
> >> complete
> 
> Inside the Octave installation I think this will only be useful if the
Octave binary
> installer for Windows was built with the --enable-dev-tools option.
> Even then, I doubt your suggestion will work as autotools and m4 etc are
> lacking. AFAIU the bash shell is merely meant to be able to run Octave in
gdb on
> the Windows side.
> It could be that it is fairly easy to augment the bash shell with the
required
> development tools; on the mingw site compiled build tools are available.
> 
> 
> >> install the video package. In Ubuntu 14.04 video package did not
> >> compile. So please use a older version of FFMpeg (no idea which
> >> version of FFMpeg is required by the video package).
> 
> Although libavformat.dll, libavcodec.dd, etc aren't present in my
> OCTAVE_HOME/bin folder, it seems that ffmpeg *IS* (or rather: should be)
> included in the mxe-octave build:
> - http://hg.octave.org/mxe-octave/file/c8c394328c54/src
> - http://hg.octave.org/mxe-octave/rev/28fa86d2cf21
> - http://hg.octave.org/mxe-octave/log/c8c394328c54/src/ffmpeg.mk
> 
> Maybe it is related to having Octave for 64-bit windows running, I don't
know.
> As I'm also interested in the video package I'll have a look one of these
days, but
> not now as I have several other priorities.
> 
> Philip
> 

Ffmpeg is in the mxe sources, but doesn't get built or installed at the
moment.

I pushed some changes up on the weekend to allow it to compile in windows
and linux - it still  doesn't get built by default though, only by doing a
"make ffmpeg" prior to building the nsis installer.

I also took a quick look also at the video package, and it doesn't work for
octave 4.0.0 or for changes in ffmpeg.
I have made some changes to it that compile under linux and _should_ work in
windows as well assuming ffmpeg and devel files are installed, but havent
tried it yet. 

If it does work, for a few other packages, what I have done is make the
depending libs dependancies of forge package when adding it to the list of
packages in mxe. That will then tie it all together and ffmpeg will get
built automatically.

JD