Le sam. 6 juin 2020 à 21:53, Greg Williamson <greg.g...@gmail.com> a écrit :
> So autotools is the current build system but that will only work on linux > and mingw correct? I can certainly check freetype builds with autotools on > those platforms but I don't think it's compatible with msvc & xcode. I > can't really check meson if it hasn't been checked in yet afaict. I'm not > the biggest fan of cmake and your cmakelists does seem to have a few issues > but I think it's far more widely used than meson. I see many projects and > even IDEs such as visual studio / qtrceator / codelite and more have > built-in cmake support whereas meson is more of a niche. I don't mind > adding build tests for meson if that's the route you choose but I think > fixing your cmake issues is more practical. As for demos, I only mean to > check that they compile against the current freetype. I assume however > these demos will not build on iOS so I won't try testing demos there. If > I'm incorrect on that let me know and I'll adjust the tests accordingly. As > I go forward and start functionality tests I will likely write a standalone > program that links freetype and google test using cmake and as I am most > familiar with cmake but it shouldn't be much work to convert it to whatever > build system you decide on later. > > I agree there is little point in building the demos for iOS. I would also avoid Android, because you won't be able to run the GUI programs anyway (programming model is too different). Technically, you can run command-line programs on Android, but this involves pushing the executables and test data files with "adb", which is rather involved. Given how portable the library is, there is no good reason to support that in our testing scheme. > Thanks for instructions on git. I typically use github with my login > directly and not ssh keys so I wasn't familiar with that process. I'll get > that setup asap and push my commits there. > > On Sat, Jun 6, 2020 at 9:31 AM Werner LEMBERG <w...@gnu.org> wrote: > >> >> Hello Greg, >> >> >> > So over the week I started writing continuous integration build >> > tests for several platforms. You can preview them here: >> > >> https://dev.azure.com/fundies/freetype2/_build/results?buildId=146&view=results >> >> this looks great! >> >> > Please let me know if there are any additional compilers, operating >> > systems or configurations you would like tested. >> >> Maybe Android? I'm not sure whether this is necessary, given that it >> is basically a Unix system. >> >> > Also, if you would like any other build system tested other than >> > cmake tested. >> >> Actually, the 'official' build system is >> >> ./configure <options> >> make >> make install >> >> The cmake stuff is contributed code not maintained by the FreeType >> team. We probably will migrate to another build system like Meson in >> the near future; you can find some discussion in this thread: >> >> >> https://lists.nongnu.org/archive/html/freetype-devel/2020-05/msg00103.html >> >> > I would also like to test freetype-demos but I'm not sure if those >> > are only valid on desktop configurations. >> >> Yes, it might be problematic to test the demo programs that uses a >> GUI. Maybe (some of) the command line tools will work. >> >> > I did have some issues with Mac/iOS builds as your repo seems to >> > have an iOS.cmake that is 6 years old and incompatible with modern >> > xcode and I had so set a blank signing key for OS X. I found a >> > newer iOS.cmake to replace your current one and it seems to work >> > however it does not currently bundle the binaries in the packaging >> > stage. Please let me know if you have better solution for either of >> > these. >> >> Maybe other people can chime in who have more experience with cmake. >> >> > Lastly, I'm not familiar with how to commit to your repo I only get >> > "fatal: remote error: access denied or repository not exported: >> > /freetype/freetype2.git" without ever being prompted for a login. >> >> This is an issue that must be fixed. Have you registered your SSH >> public key? >> >> https://savannah.gnu.org/maintenance/SshAccess/ >> >> (be careful not to add a final, additional newline if you submit the >> key). >> >> After doing the above, you should be able to check out read/write >> versions of the FreeType git repositories as >> >> git clone fund...@git.sv.gnu.org/srv/git/freetype/freetype2.git >> git clone fund...@git.sv.gnu.org/srv/git/freetype/freetype2-demos.git >> >> > So instead here is a patch: >> > >> https://github.com/fundies/freetype2/commit/564f8d163fbed71cccd1a9ea5733e28da82b7d7e.patch >> >> I hope you will be able to check this into your personal branch by >> yourself soon :-) >> >> >> Werner >> >
