<HTML dir=ltr><HEAD><TITLE>Re: R: R: [GRASS-dev] GRASS FFMPEG support</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6001.18063" name=GENERATOR><BASE href=http://mailstore.rossoalice.alice.it/exchange/Alice000000001264700/Bozze/R:%20R:%20R:%20[GRASS-dev]%20GRASS%20FFMPEG%20support.EML/1_text.htm></HEAD>
<BODY>
<DIV id=idOWAReplyText78083 dir=ltr>
<DIV dir=ltr><CODE><FONT face=Arial size=2>Hi Glynn,</FONT></CODE></DIV>
<DIV dir=ltr><CODE><FONT face=Arial size=2></FONT></CODE> </DIV>
<DIV dir=ltr><CODE><FONT face=Arial size=2>>I know building GRASS on Windows is slower than Linux, but that's<BR>>crazy. On my Linux system, it takes around 4 minutes:</FONT></CODE></DIV>
<DIV dir=ltr><CODE><FONT face=Arial size=2></FONT></CODE> </DIV>
<DIV dir=ltr><CODE><FONT face=Arial size=2>Consider that I'm on an Intel Core2 Duo 2.5GHz (T9300, with 6MB of L2 cache!) with 4Gb of RAM DDR2 (even if Vista actually uses only 3)!<BR>When compiling the processors don't run at full speed, while on my old machine (AMD Athlon64 3000+, 1.8Gh and 1.25GB RAM DDR) the CPU ran at full throttle for 3 hours, with the fan sounding like a Boeing taking off! The whole MSYS environment + GRASS compiling took more than 10 hours with the CPU at its 100%...</FONT></CODE></DIV>
<DIV dir=ltr><CODE><FONT face=Arial size=2></FONT></CODE> </DIV>
<DIV dir=ltr><CODE><FONT face=Arial size=2>>When posting error messages, please include the command which<BR>>generated the error.</FONT></CODE></DIV>
<DIV dir=ltr><CODE><FONT face=Arial size=2></FONT></CODE> </DIV>
<DIV dir=ltr><CODE><FONT face=Arial size=2>Sorry, I thought it was clear that it was simply the make command</FONT></CODE></DIV>
<DIV dir=ltr><CODE><FONT face=Arial size=2></FONT></CODE> </DIV>
<DIV dir=ltr><CODE><FONT face=Arial size=2>>However, as OGSF uses av_free directly, configure should really be<BR>>testing explicitly for libavutil. It isn't necessary on Linux, but<BR>>Windows handles DLLs differently.</FONT></CODE></DIV>
<DIV dir=ltr><CODE><FONT face=Arial size=2></FONT></CODE> </DIV>
<DIV dir=ltr><CODE><FONT face=Arial size=2>mmm... probably I need to make things more clear than they actually are now for me!<BR>avutil.dll is in the same place where the other ffmpegs DLLs are!<BR>but there's another thing that I don't undestand: when I create a ddl with gcc on MinGW I usually do as follows:</FONT></CODE></DIV><CODE><FONT face=Arial size=2>
<DIV dir=ltr><BR><FONT face="Courier New">gcc -shared -s -o libname.dll -Wl,--out-implib,libname.a $LIBOBJECTS</FONT></DIV>
<DIV dir=ltr><BR>where libname.dll and libname.a are usually installed in /usr/local/bin and /usr/local/lib respectively; and when I create an executable that uses that library I do:</DIV>
<DIV dir=ltr><BR><FONT face="Courier New">gcc -s -g -O2 -o exename.exe $EXEOBJECTS -L./ -lname</FONT></DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>I'm mainly referring to those articles:</DIV>
<DIV dir=ltr><A href="http://www.mingw.org/docs.shtml#compilingandbuilding">http://www.mingw.org/docs.shtml#compilingandbuilding</A></DIV>
<DIV dir=ltr><A href="http://gcc.gnu.org/onlinedocs/gcc/Link-Options.html#Link-Options">http://gcc.gnu.org/onlinedocs/gcc/Link-Options.html#Link-Options</A></DIV>
<DIV dir=ltr><BR>The strange thing is that there are no *.a import library files created by FFMPEG, while I always have them for each library I compiled!</DIV>
<DIV dir=ltr>Last thing: the FFMPEG make script installed the DLLs in /ffmpeg/bin, while the /ffmpeg/lib dir is empty, except for the pkgconfig folder, that contains the libav*.pc files; I googled for them, but I didn't find relevant information on what they exaclty are. Do you know some useful articles about that, please?</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Thanks for your help,</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Marco</FONT></CODE></DIV></DIV></BODY></HTML>