Re: [ft-devel] Continuous Integration is Live
>> 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 :) We are perhaps miscommunicating. The issue is not whether you call the script directly with a shell or indirectly via the shebang (IMHO, it doesn't matter). The issue is rather that `bash' supports a bunch of extensions that other shells don't have. For this reason, `configure.ac' shouldn't contain any bashisms. A bare-minimum POSIX shell implementation like `dash' might catch them. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Continuous Integration is Live
I have set up appveyor for freetype-py, they have a few msvcs available I think. Testing with the newest and oldest available one should be good enough for now. A basic smoke test would be e.g. loading a font and rendering all glyphs (and throwing the bitmaps away) or something. That would catch build system mistakes for static and shared versions. One day. ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] commit #84eebf4802 breaks compilation with older version of MSVC
On 21/05/2018 09:33, Nikolaus Waxweiler wrote: Everything you got ;) Gosh, this is embarrassing... I just tried a CMake build for you and it's now working perfectly. It generates the VC project files with no errors at all !! Regarding the MSVC build though, I mentioned previously that I don't see any errors when building freetype itself. It's only later that the error occurs - when I try to use the (statically built) library in some other project. In that case (if I built without enabling Intrinsic Functions), the linker will then complain that it can't find '_BitScanReverse()' John ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Continuous Integration is Live
> 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 :) > Ooh! 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 Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] commit #84eebf4802 breaks compilation with older version of MSVC
Everything you got ;) ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] commit #84eebf4802 breaks compilation with older version of MSVC
On 21/05/2018 08:20, Nikolaus Waxweiler wrote: I actually use the very latest MSVC to build freetype 2.9.1 for freetype-py and didn't have any problems. Can you post the error log? Hi Nikolaus - do you mean the error log from CMake or the error from MSVC ? John ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] commit #84eebf4802 breaks compilation with older version of MSVC
I actually use the very latest MSVC to build freetype 2.9.1 for freetype-py and didn't have any problems. Can you post the error log? ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
