Re: [mp3encoder] OS X LAME Framework

[Lynn Pye]

It still compiles just fine. And strictly speaking, there is no 
particular advantage to having it in an Xcode project per se. However, 
the standard "./configure;make" mode of compilation results in a 
standard dynamically linked library. What I put together is simply a 
manner of composing things into a Framework for OS X. The only 
advantage being ease of use by developers on OS X. Xcode/ProjectBuilder 
(and possibly other tools) allow a developer to add a Framework to 
their project which does two things:

	- dynamically links against the library
	- provides access to any "published" headers (lame.h in this case) 
which the Framework contains

It is simply a means of making development for OS X a bit easier and a 
little more "standard".

Regards,

Lynn Pye

On Feb 12, 2004, at 11:21 PM, Eric Dannewitz wrote:

The lame source used to compile just fine with GCC under OS X 10.2. I 
haven't tried it recently with 10.3, but I'm assuming it would 
work.............

What is the advantage of having an Xcode project?

Lynn Pye wrote:

I have not found anywhere that this was done, and so have taken the 
LAME sources and created an OS X Framework of them. I would like to 
contribute the Xcode project and related materials back to the LAME 
maintainers but am not sure who, if anyone, would like the job. It 
was made from a recent snapshot of the LAME sources.

If anyone is interested, please advise.

Thanks,

Lynn Pye

_______________________________________________
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder


_______________________________________________
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder
_______________________________________________
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder