sfeMovie (video & audio playback library with many codecs)

[Ceylo]

Hey Ceylo 
I tried with the latest v1.0
I' m on windows 7 64-bit with MinGW 4.8.2

Several things you can do:
- rebuild sfeMovie from the latest Git sources, 51_MSYS branch (this branch contains fixes for MinGW)
- provide a minimal self-contained project that I can try to use to reproduce the problem

And a question: I suppose you built sfeMovie within MinGW's shell. Did you then create your application with MinGW or with Code::Blocks?

[AlexxanderX]

Thanks for fixing that bug I will try to come back with an example.

Could you implement an setPlayingOffset ? I really need the function and now I noticed the is not exist...

[JohnGreek]

Hey Ceylo 
I tried with the latest v1.0
I' m on windows 7 64-bit with MinGW 4.8.2

Several things you can do:
- rebuild sfeMovie from the latest Git sources, 51_MSYS branch (this branch contains fixes for MinGW)
- provide a minimal self-contained project that I can try to use to reproduce the problem

And a question: I suppose you built sfeMovie within MinGW's shell. Did you then create your application with MinGW or with Code::Blocks?

Ok but the MinGW version shipped with QtCreator does not contain MSYS, can i download it separately, place it on the directory of my MinGW and use it on the branch?

Yes, i used mingw32-make inside the cmake directory. I use Qt Creator as my IDE.

[Ceylo]

Thanks for fixing that bug I will try to come back with an example.

Could you implement an setPlayingOffset ? I really need the function and now I noticed the is not exist...

setPlayingOffset() is one of the biggest pending work even if requested since a long time ago, see Seeking in the movie #6 if you're interested

[Ceylo]

Ok but the MinGW version shipped with QtCreator does not contain MSYS, can i download it separately, place it on the directory of my MinGW and use it on the branch?

Yes, i used mingw32-make inside the cmake directory. I use Qt Creator as my IDE.

I don't know if MSYS can be installed separately. It may but it's probably easier to install the full MinGW+MSYS package to have your environment already properly set up.

mingw32-make is not supported: in any case the operations triggered by make will require a MSYS environment. You should use the make executable shipped with MSYS (if your target build system is MinGW, whatever the IDE you use afterward).

Also I forgot to tell you an important point: the instructions for building from the latest Git sources are really not the same as for sfeMovie 1.0. You can find the steps to follow there: http://sfemovie.yalir.org/start.php

I hope this will help

[bluekirby0]

Ok but the MinGW version shipped with QtCreator does not contain MSYS, can i download it separately, place it on the directory of my MinGW and use it on the branch?

Yes, i used mingw32-make inside the cmake directory. I use Qt Creator as my IDE.

MSYS can be set up to work with ANY mingw installation, as long as you add your mingw bin directory (the one with gcc.exe etc...) to your PATH environmental variable BEFORE starting your MSYS shell.  You could even use the same MSYS environment with several different compilers as long as you were careful about prefixes for any libraries you "install"

Using GNU make inside an MSYS environment should work fine, and is much more flexible than mingw32-make in many regards. FFmpeg uses a completely custom build system (it is NOT autotools no matter how much it may look like it) and mingw32-make was not designed with this in mind.

[JohnGreek]

Thank you for your replies but i have never used MSYS and i' m not familiar at all with command line tools.. 
So i set the MSYS PATH variable, it's set, then what? I open msys.bat from cmd? Open msys.bat? I really have no idea with these build systems, on other libraries i generated with cmake then used mingw32-make on the generated directory.

"Build

Once the project has been generated by CMake, just build the ALL_BUILD target, or use "make" if you chose this build system. Then be patient! "  What is the ALL_BUILD target? Please give me some direction to get familiar with this 


When i use "make install" the msys interface changes to windows cmd..

[bluekirby0]

You would open a command prompt and navigate to where msys.bat is. Then you would use:

Code: [Select]

PATH=d:\path\to\mingw\bin;%PATH%
msys.bat
You could also edit msys.bat to do this for you when you run it.

If you just run "make" then you don't need to select a specific target, so you can disregard ALL_BUILD. If you really want to know what ALL_BUILD is, it is just a target that cmake generates that ensures that every other target is built...but the default for "make" without any parameters is to build all targets.

I haven't worked much with Ceylo's build system before I started tweaking it on my own so I don't know why your bash shell would be switching to a cmd shell in the middle of "make install"

[Ceylo]

I don't know which part you already know so I'll go into details

If you have set the PATH to include MinGW bin dir permanently, just open msys.bat. Then type

Code: [Select]

cd "full path to the build directory you chose in CMake"
and enter.
You must get no error with this command. Then use the 'make' command with no parameter. As bluekirby0 said, ALL_BUILD is the default target that is used by default when using make, and it'll just build everything

I'm interested in seeing what happens with screenshots when you run make install because it should NOT go back to a classic cmd shell.

[JohnGreek]

Hey, thanks for your replies.
I did as you said but my msys changes to cmd...

Before make command: http://snag.gy/KDuO3.jpg
After make command: http://snag.gy/WacB9.jpg

[Ceylo]

What do you get if you do the same after opening msys.bat from the explorer rather than running msys.bat from the Windows cmd?

[JohnGreek]

It's the same even if i run it from windows explorer.
The fact that it changes means msys has terminated?

[Ceylo]

Yes, or it did run a Windows cmd inside itself. After running make, can you check if you have sh.exe still running among your processes in the task manager?

[JohnGreek]

Yes it's still open. This is good i guess? 

[Ceylo]

Well at least this means you're still in the build script, which is good

But what's happening is really odd. I remember having a similar issue a long long time ago though. I'm not sure about how I had fixed this, the only bits of memories I still have about this is I had to reinstall MSYS properly… it's really a guess but it could mean that the execution of the program by sh.exe failed in some way. What happen if you use the "exit" comment at this point? Does it continue one step forward, does it go back to MSYS or does it close the window?