All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Atharva Raykar <raykar.ath@gmail.com>, git <git@vger.kernel.org>
Cc: Christian Couder <christian.couder@gmail.com>,
	Shourya Shukla <shouryashukla.oo@gmail.com>
Subject: Re: [GSoC] My Git Dev Blog
Date: Sat, 22 May 2021 15:39:22 -0400	[thread overview]
Message-ID: <ee246d04-4ae3-1697-0f63-13012c95ed49@gmail.com> (raw)
In-Reply-To: <35493133-2504-4CAE-B700-79EAB990DD17@gmail.com>

Hi Atharva,

Le 2021-05-22 à 12:42, Atharva Raykar a écrit :
> Hi all,
> 
> As is tradition, I have started my weekly GSoC blog :)
> 
> Here is week 1: https://atharvaraykar.me/gitnotes/week1
>

I enjoyed reading your first post. About gettext, note that
if you do not want to hardcode a specific version of gettext
in your LDFLAGS/CFLAGS, you could use '/usr/local/opt/gettext/{include,lib}',
or rather, the equivalent for M1 Macs, which I guess would be
'/opt/homebrew/opt/gettext' ? Can't test as I'm on Intel...

On a second note, for your information
the 'configure' build approach is not as well maintained as
the Makefile-only approach, so it's good to make it work with the plain Makefile.

Cheers and good luck for your internship,

Philippe.


  reply	other threads:[~2021-05-22 19:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 16:42 [GSoC] My Git Dev Blog Atharva Raykar
2021-05-22 19:39 ` Philippe Blain [this message]
2021-05-23 11:50   ` Atharva Raykar
2021-05-23  8:10 ` Bagas Sanjaya
2021-05-23 11:50   ` Atharva Raykar
2021-05-30 16:41   ` Felipe Contreras
2021-05-24 20:18 ` Christian Couder
2021-05-30  7:07 ` Atharva Raykar
2021-05-30 17:30   ` Kaartic Sivaraam
2021-05-31  5:41     ` Atharva Raykar
2021-05-31  6:55   ` Bagas Sanjaya
2021-05-31  7:43     ` Atharva Raykar
2021-05-31  8:32       ` Christian Couder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ee246d04-4ae3-1697-0f63-13012c95ed49@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=raykar.ath@gmail.com \
    --cc=shouryashukla.oo@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.