Mark Hammond wrote:
>  
>  I don't quite understand *why* you created your own.  This community would
>  be best served by people rallying behind a "single way to do it", rather
>  than fragmenting into every man-and-his-dog having their own unsupported way
>  of doing things?  I've no objection to your scheme become that one way, but
>  I've never heard what you are trying to solve that mine doesn't - in fact,
>  I've never heard anything about it at all.
>  
>  Mark

Hi Mark,

Why I've created my own PyXPCOM extension? Well quite simply because 
nobody else has provided a prebuilt PyXPCOM extension (or one that 
works). Or, why I've created my own build scripts? Because I wanted a 
non-hacky simple way to produce the PyXPCOM extension on multiple 
platforms with the following issues resolved...

The extension produced by the script MarkH has here:
http://osdir.com/ml/mozilla.devel.xpcom.python/2006-06/msg00013.html
has several major flaws which pyxpcomext solves, that being MarkH's script:
* uses install.js hackiness (is not supported in Firefox 3)
* requires installation into the Firefox main components directory, 
which the user may not have access to (pyxpcomext does not require this)
* shows a 'bad' sys.path - manually setting PYTHONHOME before starting 
firefox makes it good (pyxpcomext does not require this)

Cheers,
Todd
_______________________________________________
pyxpcom mailing list
pyxpcom@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs