freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GSOC Build tests


From: Greg Williamson
Subject: Re: GSOC Build tests
Date: Sun, 30 Aug 2020 13:09:27 -0400

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: 100% (19/19), done.
Writing objects: 100% (19/19), 21.39 KiB | 10.69 MiB/s, done.
Total 19 (delta 5), reused 0 (delta 0), pack-reused 0
remote: *** no recipients configured so no email will be sent
remote: *** for 'refs/heads/GSoC-2020-greg' update
None->3f82a109c0f16458b05110beeb2ad443ba0274bd
To git.savannah.nongnu.org:/srv/git/freetype/freetype2.git
 * [new branch]          GSoC-2020-greg -> GSoC-2020-greg
Branch 'GSoC-2020-greg' set up to track remote branch 'GSoC-2020-greg'
from 'origin'.

I also added a readme as requested in CI/readme.md.

Can anyone confirm this worked and tell me how I can link to it in my
final evaluation?

I was also able to fix a few msys build errors but I still cannot
build demos in msys due it trying to include termios.h which is not
available. For now, I've temporarily disabled building demos for that
platform.

On Sat, Aug 29, 2020 at 10:23 AM Werner LEMBERG <wl@gnu.org> wrote:
>
>
> 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) fixed the relative paths in the generated comparison page
>
> This looks good, thanks.  However, I miss a README document that
> explains where to start...
>
> > I have also made an attempt to add a fix for the MinGW builds but it
> > appears your make install script can't handle window paths so we'll
> > need to sed the \ to / or something to fix that build test.
>
> Please show an error log.  Maybe it's easy to fix.
>
> > If you have any issues or questions about my code I will still be
> > checking this email even after GSoC so let me know and I will do my
> > best to fix whatever is wrong.
>
> Great, thanks!
>
> > In the gitlab migration listing I can talk about integrating this
> > before or after you move but I am more familiar with github and can
> > only really answer questions on my azure config file and scripts or
> > integrating it with github.
>
> We would be indeed glad if you could assits with CI stuff since my
> knowledge is essentially zero.
>
> > As for my side of the GSoC evaluation, Where do your students
> > typically link to for the "showcase" of their project?
>
> You should put your code into a branch named 'GSoC-2020-greg' (or
> something similar) of the FreeType repository.
>
> > I was never able to successfully push to your repo
>
> This we have to fix right now.  What exactly is the problem?  Have you
> uploaded an SSH key to Savannah for your account?
>
>   https://savannah.gnu.org/maintenance/SshAccess/
>
> Be careful not to add a final newline character that some editors
> automatically insert.  After this, you should be able to checkout the
> FreeType repositories with
>
>   git clone fundies@git.savannah.nongnu.org:/srv/git/freetype/freetype2.git
>   git clone 
> fundies@git.savannah.nongnu.org:/srv/git/freetype/freetype2-demos.git
>
>
>     Werner



reply via email to

[Prev in Thread] Current Thread [Next in Thread]