On Mon, Oct 8, 2012 at 8:15 AM, Pavel Koshevoy <pkoshevoy@xxxxxxxxx> wrote: > I am not proposing to switch to cmake for any platforms. I am only > proposing to make it available for native win32/win64 builds. If someone > decides to extend it later to more platforms -- great, but that was not my > focus this time. I know. that would be obvious what is the target to build for if one is proposing to add Makefile.win32. but just adding CMakeLists.txt may implies to work on all of platforms and you just tested it on Win32 (or MSVC) only. it's the problem. or if you can rename it to something containing win32, that may be good. > Well, if it goes out of date then the next time someone needs to use it -- > it will be their responsibility to bring it up to date. I am not proposing > to burden a predominantly Linux based project to support native compilation > on Windows. I am just trying to make it easier for Windows developers to > use fontconfig on their platform. BTW, one of the projects required by > fontconfig also provides CMakeLists.txt in addition to autotools > configuration -- expat-2.1.0. So, this isn't unprecedented. Is it not maintained by anyone else? I guess it is. the point is non-maintained files/architectures may be obsoleted in the future, to avoid any trouble. -- Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
