Ok I've wrapped the readme lines as requested
On Sun, Aug 30, 2020 at 4:02 PM Werner LEMBERG wrote:
>
>
> > Ok I believe I was able to commit to savannah but the message is a
> > bit cryptic:
>
> Everything's fine, thanks.
>
> > I also added a readme as requested in CI/readme.md.
>
> Thanks.
> Ok I believe I was able to commit to savannah but the message is a
> bit cryptic:
Everything's fine, thanks.
> I also added a readme as requested in CI/readme.md.
Thanks. Please reformat the file to make the lines not longer than 78
characters.
> Can anyone confirm this worked and tell me
Ok I believe I was able to commit to savannah but the message is a bit cryptic:
[greg@greg-desktop savannah-freetype2]$ git push --set-upstream origin
GSoC-2020-greg
Enumerating objects: 23, done.
Counting objects: 100% (23/23), done.
Delta compression using up to 8 threads
Compressing objects:
Ok I believe I was able to commit to savannah but the message is a bit cryptic:
[greg@greg-desktop savannah-freetype2]$ git push --set-upstream origin
GSoC-2020-greg
Enumerating objects: 23, done.
Counting objects: 100% (23/23), done.
Delta compression using up to 8 threads
Compressing objects:
Hello Greg,
sorry for the late reply.
> As, discussed with Werner I have:
> 1) added a simple config file (in CI/ft-tests.config)
> 2) split the tests into smaller chunks
> 3) changed the colors of the diff images to green / red
> 4) added the diff images to the generated comparison page
> 5)
As, discussed with Werner I have:
1) added a simple config file (in CI/ft-tests.config)
2) split the tests into smaller chunks
3) changed the colors of the diff images to green / red
4) added the diff images to the generated comparison page
5) fixed the relative paths in the generated comparison
>> This looks very good, thanks! Indeed, the archive size of almost
>> one Gigabyte is far too large for practical purposes. We have now
>> to find solutions in the next month how to refine that.
>
> Right now it runs ~12 fonts that have ~3k glyphs each; this is why
> it's so large. I think
> This looks very good, thanks! Indeed, the archive size of almost one
> Gigabyte is far too large for practical purposes. We have now to find
> solutions in the next month how to refine that.
Right now it runs ~12 fonts that have ~3k glyphs each; this is why it's so
large. I think the best
> I've finished the core of the regression tester.
Great!
> You can now run it and generate a html report but you will need a
> few tools installed: imagick, xwd, npm, pretty-diff and xvfb. This
> should all be listed in ft-regression.sh's comments.If you want to
> run it locally make sure you
I've finished the core of the regression tester. You can now run it and
generate a html report but you will need a few tools installed: imagick,
xwd, npm, pretty-diff and xvfb. This should all be listed in
ft-regression.sh's comments.If you want to run it locally make sure you
have a ~/test-fonts
Hello Greg,
> figured out the cause. I have however been working on this as much
> as time allows. I've mostly hashed out the scripts to run regression
> tests using demos here:
> https://patch-diff.githubusercontent.com/raw/fundies/freetype2/pull/1.patch
> [...]
Some comments.
* There are
Hi, sorry for lack of responses. I have been very busy with final projects
for my summer classes and to top it off, some of the ram (or slots on the
motherboard) in my computer died and my computers were super wonky until I
figured out the cause. I have however been working on this as much as time
Hello Greg,
>> Over the coming week I plan to write some functionality tests. I
>> believe my best course of action for this is just to use the
>> existing freetype demo programs in tandem with some bash scripting
>> to check for inconsistencies in various fonts between commits. I
>> will
Hello Greg,
> Over the past couple weeks I've converted the build tests to use
> autotools for the three desktop OSes. I've managed to leave the
> cmake tests intact too. I also now have demos building against the
> freetype version pulled in the CI.
Thanks!
> I wasted quite a bit of time
Over the past couple weeks I've converted the build tests to use autotools
for the three desktop OSes. I've managed to leave the cmake tests intact
too. I also now have demos building against the freetype version pulled in
the CI. I wasted quite a bit of time trying to get autotools to work with
>> 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.
All GUI programs are compiled with a GUIless batch
> 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
Le sam. 6 juin 2020 à 21:53, Greg Williamson 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
Le sam. 6 juin 2020 à 15:31, Werner LEMBERG a écrit :
>
> 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=results
>
> this
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
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=results
this looks great!
> Please let me know if there are any additional compilers,
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=results
Builds are uploaded here:
22 matches
Mail list logo
