Compiling xvid running, already, simple, follow, should

andy

. Thanks in advanced.

oh and I already tried   thanks.

VS7 should be fine as should cygwin. I have successfully compiled with MSVC7.1 and mingw. VfW should be as simple as running make in /vfw/bin. dshow there are instructions that you need to follow. Once you have done that though just run make in /dshow.


Originally Posted by celtic_druidVS7 should be fine as should cygwin. I have successfully compiled with MSVC7.1 and mingw. VfW should be as simple as running make in /vfw/bin. dshow there are instructions that you need to follow. Once you have done that though just run make in /dshow.

When trying to run each of them in Visual C 7 it always has a large amound of warnings and throws nasm errors quot;unspecifed  pathquot;  that was also discussed on a solution to solve however that process takes a long time to manaull change each of the pathnames in the .asm files. Do you have a simple way of doing this or is there some sort of special setting your using? are you even using nasm?  Thanks.

Yes I use nasm. Generally I use MSVC6 with ICL7 though and it compiles fine. From recollection once it has converted the dsp file you have to manually edit the nasm lines as it screws them up.

If you have already compiled xvidcore.dll with cygwin you should be able to get xvidvfw.dll easily and xvid.ax with a little bit of effort.

yeha I been working on it for the last 2 hours. got xvidcore and the vfw. working on the dshow filter now. You said it had instructions? I'm working on patching the directshow SDK atm.  Then I'll try quot;makequot; and see if still throws the same error.

yes you are right about VC 7.0 screwing up the pathnames. it does it for all files ending in .asm if I remember from my adventures in getting it to work the last time. there used to be a hosted file on the forum that had it done already but that file is gone and was out of date.

you need to  add several directories to your visual c settings. go to Tools/Options/Projects/VC++ Directories use the dropdown box in the right corner to switch to quot;include Filesquot;. Add the Following Directories

C:\lt;SDK9DIRgt;\Include
C:\lt;SDK9DIRgt;\Samples\C++\DirectShow\BaseClasses

where lt;SDK9DIRgt; is your Direct X 9 SDK install Directory.

then use the dropdown box to switch to quot;library filesquot; you need to add the following:

C:\lt;SDK9DIRgt;\Lib  

Now comes the fun part. You need to go into  
C:\lt;SDK9DIRgt;\Samples\C++\DirectShow\BaseClasses and open the VS 7 project file. Compile it and you will get a file called strmbase.lib. copy that file and paste it in   C:\lt;SDK9DIRgt;\Lib

Now try compiling the dshow project and everything should go fine. you now have the third part of xvid. xvid.ax

Turn it into an installer or install it manually. Hopefully this helps others who are interested in compiling xvid.

I'll see if I can work out some solutions for the problems seen in compiling xvidcore and vfw in VS 7.0.

Here ya go celtic_druid...dcoremsvc71.7z XviD compiled with MSVC7.1.

VfW should just compile, although if you don't have xvidcore.dll compiled you will get an error when it tries to copy it.

Compiled from current cvs.

For xvidcore, I just got rid of all the amp;quot;'s.

I tried removing all the amp;quot; this morning and it solved the first problem. Now nasm instead of saying there is no input file it's saying there are more than one specified. after taking a look at libxvidcore.vcproject it seems like it's all phrased right. is there something else that has to be changed that I'm not seeing? Thanks. I can also post buildlogs or projectfiles if need be. I'd like to work out the issue as this has been quite an informative attempt thus far.

That was all I did and it compiled fine.

Make sure you don't have any spaces in the directory names leading to where the source code is stored.


Originally Posted by squid_80Make sure you don't have any spaces in the directory names leading to where the source code is stored.

doh, you were right. did you know this from experience?

Nope. Guessed from the nasm error message you gave.