[XviD-devel] vfw Makefile

[Edouard Gomez]

suxen_drol (suxen_drol at hotmail.com) wrote:
> hello,
> 
> has anyone used xvidcore/vfw/bin/Makefile recently?
> it appears broken to me (patch below):
> 
> * the output file is written to a "=build" directory
> 	(there is an additional equal sign in the BUILD_DIR macro.)

This is intentional, the "=" prefix helps arch/tla skipping changes in
the build dir easily.

> * -lxvidcore is used. this is no longer required.

I wonder why it would not be required. Could you explain what happens ?

> +++ C:\xvidcore\vfw\bin\Makefile        Tue Jan 27 22:17:55 2004
> @@ -16,7 +16,7 @@
> 
>  MAKEFILE_PWD:=$(shell pwd)
>  LOCAL_XVID_SRCTREE:=$(MAKEFILE_PWD)/../../src
> -LOCAL_XVID_BUILDTREE:=$(MAKEFILE_PWD)/../../build/generic/=build
> +LOCAL_XVID_BUILDTREE:=$(MAKEFILE_PWD)/../../build

I still  don't get why  it would work  this way, as the  makefile builds
xvidcore.dll  in ${xvidcore}/build/generic/=build  by default.  The only
problem i can  see is a missing pwd utility  would cause trouble because
these vars would be wrong.

MAKEFILE_PWD:=$(shell pwd) (== "")
LOCAL_XVID_SRCTREE:=$(MAKEFILE_PWD)/../../src (== /../../src)
LOCAL_XVID_BUILDTREE:=$(MAKEFILE_PWD)/../../build/generic/=build
(== /../../build/generic/=build)

Does msys provide a pwd utility ?

>  RM = rm -rf
>  WINDRES=windres
> @@ -54,7 +54,7 @@
> 
>  .SUFFIXES: .obj .rc .c
> 
> -BUILD_DIR = =build
> +BUILD_DIR = build

I'd like not to change this, as this is really intentional.

> -                       -lxvidcore -lgdi32 -lwinmm -lcomdlg32 -lcomctl32
> +                       -lgdi32 -lwinmm -lcomdlg32 -lcomctl32

How does ld find out where xvid_xxxx symbols are if you remove this ?
Or is xvidvfw linking at runtime with Dll loading Win32 API ?

-- 
Edouard Gomez