> > Looks good, thanks. What's still missing is my suggested fourth mode > (not present in the support for other libraries needed by FreeType), > namely the `no-default' option to have compiled-in SVG code without > providing a default library. >
Oh yes, I am aware of that, I was just starting the work on that one. > > I would want to allow the user to plug in a different library as the > > default one while building the library. > I think we shouldn't do this; it's getting too complicated. I believe > that my suggested `no-default' mode is a simpler solution; the user > registers the library hooks at run-time, and that's it. Everything > else has to be done on the user side (this is, providing any necessary > wrapper and/or port files and setting up correct linking). > Okay, so if I have understood this correctly. In case of `auto' or `yes', we see if our default is available, and if yes, we use that, if the user chose `no-default' then the user would need to plug the hooks in and the user MUST link his program (the client program) to the actual SVG rendering library. Have I understood you correctly? This is also how I do in my `tester' program that you can find in all of the different ports I wrote. > > What should be the user interface to do that? To plug in a default, > > the following things are needed: > > If we are following my route, all of your suggestions are not > necessary, I think. > Yea, if we don't wanna let the user switch the default library, none of that is necessary. :)
_______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
