Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] tcf-agent: bump to version 1.7.0
Date: Fri, 13 Apr 2018 09:53:39 +0200	[thread overview]
Message-ID: <20180413095339.405a1a30@windsurf> (raw)
In-Reply-To: <CADYdroOdnrNUCvq+Yd95rkwO0BCioby19QGGb0cU++Ja8Nc3gA@mail.gmail.com>

Hello,

On Fri, 13 Apr 2018 09:50:35 +0200, Norbert Lange wrote:

> @Thomas: Part of the discussion resides in
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=529417,
> Eugene is the the maintainer of tcf-agent and I advised him to put his
> mail in DEVELOPERS,
> as otherwise I have to piggyback issues and fixes around projects.
> Also there are apparently multiple (closed source) projects using
> tcf-agent, so a my fixes for linux
> might break other stuff.

OK.

> I switched from CMake to regular Makefiles for the same reason, the
> later is better supported upstream,
> and support detecting headers/functions/libraries from the system.
> Getting CMake to parity would be alot
> work.

That is rather odd. A build system like CMake normally helps a lot
resolve cross-compilation issues.

> @Eugene: buildroot allows static linking, which can come handy for
> stuff like initial ramdisks which only need a
> small set of tools (eg. only busybox without any libraries)
> 
> I will try to respond to Thomas' requests for the patch this weekend,
> but can you look at the empty ranlib call?
> My solution would be to set the makerule to
> 
> $(BINDIR)/libtcf$(EXTLIB) : $(OFILES)
>     $(AR) $(AR_FLAGS) $(AR_OUT_F)$@ $^
>     $(RANLIB) $@
> 
> (and fixup the variable definitions in Makefile.inc)

What about sticking to the CMake build system, and fixing whatever
issues you have ? This seems like a much more sensible approach than
using hand-written Makefiles.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-04-13  7:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 15:13 [Buildroot] [PATCH 1/1] tcf-agent: bump to version 1.7.0 Eugene Tarassov
2018-04-12 21:49 ` Thomas Petazzoni
2018-04-13  1:50   ` Evgueni Tarassov
2018-04-13  7:50     ` Norbert Lange
2018-04-13  7:53       ` Norbert Lange
2018-04-13  7:53       ` Thomas Petazzoni [this message]
2018-04-13  8:13 ` Thomas Petazzoni
2018-04-13  9:32   ` Norbert Lange
2018-04-13 11:18     ` Thomas Petazzoni
2018-04-13 11:33       ` Norbert Lange

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=20180413095339.405a1a30@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox