[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

OpenDivX digest, Vol 1 #85 - 3 msgs



Send OpenDivX mailing list submissions to
	[email protected]

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.projectmayo.com/mailman/listinfo/opendivx
or, via email, send a message with subject or body 'help' to
	[email protected]

You can reach the person managing the list at
	[email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of OpenDivX digest..."


Today's Topics:

   1. Unsubscribe (atecky)
   2. Re: How to make an open-source project fail (Lionel Ulmer)
   3. Re: How to make an open-source project fail (Christoph H. Lampert)

--__--__--

Message: 1
From: "atecky" <[email protected]>
To: <[email protected]>
Subject: [OpenDivX] Unsubscribe
Date: Sat, 2 Jun 2001 18:32:00 +0800

This is a multi-part message in MIME format.

------=_NextPart_000_004E_01C0EB92.4FD537E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



------=_NextPart_000_004E_01C0EB92.4FD537E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_004E_01C0EB92.4FD537E0--



--__--__--

Message: 2
Date: Sat, 2 Jun 2001 16:50:54 +0200
From: Lionel Ulmer <[email protected]>
To: [email protected]
Subject: Re: [OpenDivX] How to make an open-source project fail

>  Do not use divxcore/decore/build/linux/Makefile, it is outdated and so
> useless that I am thinking about removing it. Instead you can use
> divxcore/decore/Makefile.am ( up-to-date automake makefile which you
> could incorporate into your own source tree ).

By the way, how can one use this Makefile.am 'stand-alone' ? I want just to
build libdivxdecore and when I try to run automake, I just get an error
message about a missing configure.in... And should a '.am' file not generate
only a '.in' that will then be converted to a real Makefile by autoconf ?

If that last sentence is true, how can one build the latest CVS tree without
having to create a complete GNU auto-shit^H^H^H^Hconf suite (I was never a
big fan of these tools :-) ) ?

By the way, another nice thing to have for improving the development process
would be a 'cvs commit' mailing list to help people keep in sync with the
current developments WITH GOOD changelogs strings (that last part is very
important :-) ).

A second point would be to have a more open process when changes are done by
the maintainers (for example, explain in advance or when done build tool
changes, API changes, changes impacting cross-platform issues, ...) to have
people feeling at least moderately involved in the whole thing and not
always have to ask for this and that.


       Lionel (just back from vacations and wanting to go back to do some
               ARM optimization / debugging of divxdecore)

-- 
		 Lionel Ulmer - http://www.bbrox.org/


--__--__--

Message: 3
From: "Christoph H. Lampert" <[email protected]>
To: [email protected]
Subject: Re: [OpenDivX] How to make an open-source project fail
Date: Sat, 2 Jun 2001 17:13:20 +0200

Am Samstag, 2. Juni 2001 16:50 schrieben Sie:
> If that last sentence is true, how can one build the latest CVS tree
> without having to create a complete GNU auto-shit^H^H^H^Hconf suite (I was
> never a big fan of these tools :-) ) ?

Forget Makefiles, they never work the way you want them to. At least not with
OpenDivX. Use the good old shell instead... :-)

Two shell lines are enough to create a static lib, shared can of course be
created the same way.

To go divxcore/encore/src and run

#!/bin/sh
cc -c *.c
ar r libdivxencore.a *.o

No, that's not three lines, since the first is a comment.  :-)
Of course you can add as many options as you like, I usually use
cc -O2 -Wall -g -D_RC_
for debugging symbols and creation of a trace.txt file.

For Solaris/IRIX you should set -DBIG_ENDIAN, for Linux you might need to
define -DLINUX as well. Solaris also needs -xCC because OpenDivx uses C++
type comments in C-source.
The compiling step creates a few errors, because there are files with
Windows-includes, but these are not needed for encoding itself, so just
ignore the errors, or exclude the files from compiling.


For the decode you need some more options: To go divxcore/decore/src

#!/bin/sh
cc -c *.c generic/*.c -D_DECORE -DO_RDONLY=00 -DO_BINARY=00
ar r libdivxdecore.a *.o

At least here these options are needed because of some strange includefiles
defining different symbols. Ignore the warning about "already defined
symbols".
For Solaris/IRIX you might have to add
-D__forceinline= -D__inline= , because the compiler doesn't know these flags.
Solaris need -xCC again. On i386 you can compile the MMX version by using
mmx/*.c instead of generic.

Hope it works,

Christoph

-------------------------------------------------------



--__--__--

_______________________________________________
OpenDivX mailing list
[email protected]
http://lists.projectmayo.com/mailman/listinfo/opendivx


End of OpenDivX Digest


Reply To Poster

Local References / HOW-TO / FAQs