Re: [GSoC] My Git Dev Blog

[Atharva Raykar <raykar.ath@gmail.com>]

On 23-May-2021, at 13:40, Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> 
> 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?

No special reason for this. My old Linux machine was due for
an upgrade, and a new M1 Macbook has since taken its place.

> 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?

I don't really use Vim that much and I am not that familiar
with how to configure it. Sorry, I don't think I can be of
much help here. I also don't want to share tips on my blog
that I won't be making use of.

> 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}).

Thanks a lot! This was helpful and did work out for me. Since
I am new to macOS (and homebrew), I did not know about this
hierarchy. I finally decided I would update my post to use
this along with a Makefile-only approach recommended by Philippe.

>  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).

I'm not too sure, and unfortunately I don't have my old Linux
system to verify this.

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