[Maf] 0.6.2 Release - MacOS X Support
Christopher Ottley
xknight at users.sourceforge.net
Wed Aug 3 19:53:02 EDT 2005
Marco De Vitis wrote:
> What should be needed to compile the code?
GCC c compiler and c++ compiler (for statically compiled Zlib and the
C++ XPCOM)
Gecko SDK for MacOS X
GNU make
> Do you expect it to need modifications before compiling on Mac can
> succeed?
As it's now BSD based, the Linux (unix ifdef) stuff should be good
enough for a clean compile.
> I could try for you if you like; the problem is that I only have a
> vague idea of what XPCOM is. :-/
The compiling part is only half the battle. There may be memory
allocation issues (turned up during stress testing on Windows),
permission problems and the list can go on. This is why I need a machine
just for that part of it.
MAF on Firefox / Mozilla on OS X has also been troublesome before this
because of the way mime issues are handled and various other things that
seem to work fine in Linux and Windows but die on OS X.
> I can understand your concerns. The general idea people have about
> extensions is that they should be free, so I suppose it will still
> take some time before some money can be earned with a Firefox extension.
Technically I got a donation. Does that make me the first? ;).
I found a site that would let me sell software for 10% of my earnings.
Accepts credit cards, international (important as I'm outside the US)
and easy to setup. Still don't know if I'd go that route at all though.
I guess I could eMail Apple. Heh. Dear Apple, I'm an OSS developer and
have no access to a Mac here in the Caribbean. Could you please donate
one to me so I can cross compile, debug and test my MAF extension.
You'll get it back when I'm done. Promise. ;).
I appreciate the offer for help (hey I can always use some) but remote
debugging is hard enough, much less remote development. ;). If one day I
develop a plan to solve this problem, you'd be among the first to know.
Regards,
Christopher.
More information about the Maf
mailing list