Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package: add jimtcl support
Date: Mon, 2 May 2011 07:41:15 +0200	[thread overview]
Message-ID: <20110502054115.GH1212@game.jcrosoft.org> (raw)
In-Reply-To: <87ei4iux8y.fsf@macbook.be.48ers.dk>

On 19:49 Sun 01 May     , Peter Korsgaard wrote:
> >>>>> "Jean-Christophe" == Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> writes:
> 
> Hi,
> 
>  >> Is there really a need to support anything else than 0.70? We prefer to
>  >> only have 1 version as that simplified implementation and testing.
> 
>  Jean-Christophe> I do use the the HEAD personally
> 
>  Jean-Christophe> but the 0.70 is the last release I see project still
>  Jean-Christophe> using the previous one
> 
> What does openocd need? I would prefer to only have 0.70.
0.70 but openocd use the HEAD usualy
> 
>  Jean-Christophe> I do not known yet how to implement it but, I get in
>  Jean-Christophe> my mind the idea to add for the scm the same idea as
>  Jean-Christophe> for http download, the mirror mecanism When you work
>  Jean-Christophe> offline or on slow internet network it's really good
> 
> That should work today - E.G. the git support creates a tarball which
> will be reused next time you build or can be put on a mirror server.
The idea is to use the tree directly and not everytime create a tarball

> 
>  Jean-Christophe> +JIMTCL_INSTALL_STAGING = YES
>  Jean-Christophe> +JIMTCL_INSTALL_TARGET = NO
>  >> 
>  >> Why no installation on target?
>  Jean-Christophe> no need of it for openocd we just link link to it staticly
> 
> Ok, but we want a generic package. What does it install? Just a
> shared/static library or also some tools?
shared, tools and static
so I can make the them optional as no need for openocd
> 
>  >> Does it really use autotools and have broken DESTDIR support?
> 
>  Jean-Christophe> yeah the --prefix is ignore, even if you pass
>  Jean-Christopha> --prefix=/usr it will install in /include
> 
> That sound like something to fix upstream then.
All the version are affected

Best Regards,
J.

  reply	other threads:[~2011-05-02  5:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-30 13:42 [Buildroot] [PATCH 1/2] package: add jimtcl support Jean-Christophe PLAGNIOL-VILLARD
2011-04-30 13:42 ` [Buildroot] [PATCH 2/2] package: add openocd support Jean-Christophe PLAGNIOL-VILLARD
2011-05-01 16:20   ` Peter Korsgaard
2011-05-01 16:45     ` Jean-Christophe PLAGNIOL-VILLARD
2011-05-01 12:35 ` [Buildroot] [PATCH 1/2] package: add jimtcl support Jean-Christophe PLAGNIOL-VILLARD
2011-05-01 15:59 ` Peter Korsgaard
2011-05-01 16:43   ` Jean-Christophe PLAGNIOL-VILLARD
2011-05-01 17:49     ` Peter Korsgaard
2011-05-02  5:41       ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2011-05-02  6:44         ` Thomas Petazzoni
2011-05-02 15:47           ` Jean-Christophe PLAGNIOL-VILLARD

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=20110502054115.GH1212@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.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