Hi Atharva,

On 22/05/21 23.42, Atharva Raykar wrote:

Hi all,

As is tradition, I have started my weekly GSoC blog :)

Here is week 1: https://atharvaraykar.me/gitnotes/week1

I shall be sharing my progress, thoughts, experiences and any
information that might help future contributors in my blog.

After my GSoC period, I hope to convert it into a blog that
will help pull in and guide new contributors to Git development.

Any kind of feedback will be appreciated!

You said on your blog that you switched your development environment
from Linux (what the distro you used previously?) to macOS. Why did
you make the switch?

Next, you mentioned that you set up emacs config for Git developers
(ones that contribute code to git.git). Since I use (r)vim instead
of emacs as my editor, what are similar configs for vim?

And finally, you said that you had to deal with "header not found"
errors. I asked these questions:

   1. You mentioned that in order to link against gettext on non-standard
      path, you did:

./configure "LDFLAGS=$LDFLAGS -L/opt/homebrew/Cellar/gettext/0.21/lib" \
     "CFLAGS=-I/opt/homebrew/Cellar/gettext/0.21/include"

      Why did you use full path to gettext? I suspect that you can instead
      use `LDFLAGS= $LDFLAGS -L/opt/homebrew/lib \
      CFLAGS=-I/opt/homebrew/include`, because when you install a library
      using homebrew, it will symlink the library location from homebrew
      standard hierarchy (/opt/homebrew/{lib,include}) to actual location
      (/opt/homebrew/<User>/<package>/<version>/{lib,include}).
   2. Can these procedure above for linking Git against libraries at
      non-standard locations (such as /opt) be applicable also to Linux
      systems? Try to adapt that procedure on your Linux system (if
      available), with custom-compiled newer version of any of Git
      dependencies (such as gettext).

Thanks.

-- 
An old man doll... just what I always wanted! - Clara