I think if you wanted to create a non-module version, that would be
and I'm sure others would be interested in it as well. Might be nice to
have an OpenPlay that completely linked into the application code,
instead of being a library (that's the only advantage I could see in
creating a non-module approach, as with Bundles end-users never even
As for the license, as long as you contribute your changes back to the
community you can do what you like :)
That I'll do.
My first step is to recreate the XCode project, I have no idea why the
included one refuses to acknowledge the existence of carbon.framework.
I'm remade it, and for now, instead of making a framework or old style
lib, I've made a BSD dynamic library. So far, so good. Except it
freezes up in "refresh_protocols". Now I'm tracking that :)
One questions: DEBUG_PRINT -- it doesn't seem to be defined anywhere.
I guessed what it was a re-defined it, but I assume that means I missed
a file somewhere, but it doesn't seem to be part of the files
(DL_DEBUG_PRINT is defined, though.)
One side note: Combining all the libraries, especially openplay.h and
netmanager.h into a single header, and referencing that header, would
really help speed up compilation as it could be pre-compiled. Right
now it's really slow ...
Do not post admin requests to the list. They will be ignored.
Openplay-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden