> All those scripts should run with plain `sh' ... Totally, sorry, I overlooked that! However, I would use `sh` to invoke the script to keep the setup independent of Debian. It might be more future-proof to use `chmod +x foo.sh; ./foo.sh` but I generally try to me rather explicit when writing code. Please let me know if you have any preferences there (`chmod ...` vs. `sh ...`) -- I'm happy to follow these guidelines :)
> Ooooooh! You beat me to it. Since ft is supposed to compile with every deity > damn compiler that supports fPIC, I wanted to set up a win/Lin/macOS compiler > ci thing that compiled everything on every commit. We'd need some basic tests > for that though. Hehe -- I'm glad I could spark something there :D So far, Travis CI is somewhat limited when it comes to customised setups. Current limitations seem to: no Windows, no 32bit and no native ARM. Workarounds in the form of docker images exist for some things but I'm not sure if they cover all issues that could arise when working "natively" on these platforms. As for Windows, AppVeyor might be an alternative. In general, however, I think that only self-hosted solutions (Azure + Jenkins etc) could really guarantee a proper setup to test builds on all thinkable platforms. All that being said, Travis CI is amazing for what it is: there are (almost) no limitations to what they let you compute on Debian Machines and Macs -- no matter what space, time, or bandwidth. _______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
