Ciro Cattuto schrieb:
On 8/20/07, Ulrich von Zadow <[EMAIL PROTECTED]> wrote:
Yeah - sorry there's no instructions for building on mac os x.
if you think it could be useful, feel free to add my notes to the wiki.
So people building on OSX will have something to guide them.
There's a
BuildMacDeps.sh script in the main libavg directory which I use to build
all the dependencies from tarballs - no fink, no darwinports. Using
those dependencies and gcc 4.0.1 build 5341 (xcode 2.3), nothing needs
to be patched.
good, but I'm not really willing to install all those libraries from tarballs
just for the purpose of building libavg ...I'd rather use fink and/or
darwinports as a reference,
I can see that you might be reluctant to compile everything from
scratch. Still, the release is distributed as a dmg and should install
without dependencies, so it links most libraries statically. I need a
source tarball build for that and I'm reluctant to support two build
strategies. (I'll accept paches that don't break the tarball build, of
course.)
I really need to put up a page describing how to build from source on a
mac soon. It's not that difficult, because the build script should take
care of everything. All libraries are installed into private
directories, so nothing is messed up in the rest of the system.
> and I think that a good build strategy
should be robust with respect to those choices.
In theory, yes. In practice, there are libraries that change APIs way
too often (most notably ffmpeg and libdc1394) for libavg to support all
versions. I always welcome patches that increase robustness wrt
different library versions, though.
The patch takes care of three things:
* problems with gcc's alwaysinline attribute. These can be fixed
by including <math.h> before other headers, so that the proper
macros are in place when needed. This is probably worth committing
anyway, because if makes the build behavior more robust.
That does sound like it should be applied. Can you elaborate on what
'problems with gcc's alwaysinline attribute' were?
* changes in the API of ffmpeg. I did build against the latest SVN version
of ffmpeg and that didn't change things: the patch was still needed.
The build system should probably require a recent enough version
of the ffmpeg libs (and then the patch should be committed).
We'll need #ifdefs for that (at least for a transition period), because
different distros use different versions of ffmpeg. Can you give me an
approximate version number for the api change? Or better yet, a patch
that includes an #ifdef?
* removing hardcoded paths to autotools in the bootstrap script.
The BuildMacDeps script might depend on this, but I don't think
it's good to hardcode paths there.
Right. I'll see what I can do to fix that :-).
Since your remaining errors are video-related: I'm using ffmpeg svn
revision 6002 for the mac build. See if using that changes anything.
it doesn't unfortunately... I'll look better into it
and see whether I can come up with more information. Thanks.
Have a look at src/test/resultimages, where the images that changed from
the baseline (+the baseline images and a diff image) are stored.
Cheers & thanks for you help,
Uli
--
Ulrich von Zadow | +49-172-7872715 | [EMAIL PROTECTED]
_______________________________________________
libavg-users mailing list
[email protected]
https://mail.datenhain.de/mailman/listinfo/libavg-users
