public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Oron Peled <oron@actcom.co.il>
Cc: crossgcc@sourceware.org
Subject: Re: crosstool-NG 1.14.0 is out
Date: Thu, 02 Feb 2012 18:40:00 -0000	[thread overview]
Message-ID: <201202021940.15988.yann.morin.1998@free.fr> (raw)
In-Reply-To: <201202021035.01636.oron@actcom.co.il>

Oron, All,

On Thursday 02 February 2012 09:35:01 Oron Peled wrote:
> On Wednesday, 1 בFebruary 2012 22:44:49 Yann E. MORIN wrote:
> > I don't know what happened with the release script: I did replay the exact
> > same commands as yesterday, on the same machine right now, and this time,
> > it worked... Sigh.
> 
> Since you already moved to autoconf, I'll just mention that automake
> generates 'make dist' and 'make distcheck' targets exactly to ease
> and test the release process. Obviously, this in itself does not
> justify moving over to automake, but it still nice to know it solves
> many common nasty problems as this one.

Yes, I'm aware of automake and its usage. It's just that I wanted to do it
incrementally, as I am not totally fluent with the autotools peculiarities.

I only very recently started using them, and doing things properly is not
very easy. Especially for the kconfig stuff, because it does weird things.
For example the parser #include-s the lexer, rather than compiling the two
into different .o files, so it's not possible to use the standard automake
rules for the lexer, or there are issues at link time.

Also, because ct-ng is based on (shell and Makefile) scripts, it does not
fit well into the automake framework (although there is provision for
handling scripts in automake, it's not that straightforward).

Thanks for the tip, though!

BTW, if you want to see what I've been playing on wrt the autotools, you
can have a look at ( note: this is WIP! ;-) ):
    http://ymorin.is-a-geek.org/hg/kconfig-frontends/

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2012-02-02 18:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01  0:01 Yann E. MORIN
2012-02-01  2:53 ` Trevor Woerner
2012-02-01  4:15   ` Trevor Woerner
2012-02-01 14:05   ` Per Arnold Blaasmo
2012-02-01 14:11     ` Yann E. MORIN - FT/OLNC/RD/MAPS/SHINE/HDMI
2012-02-01 20:45   ` Yann E. MORIN
2012-02-02  8:35     ` Oron Peled
2012-02-02 18:40       ` Yann E. MORIN [this message]
2012-02-02 15:13 ` Johannes Stezenbach
2012-03-07 13:12 ` Michael Zintakis
2012-03-08 14:47   ` Johannes Stezenbach
2012-03-08 19:09     ` Michael Zintakis

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=201202021940.15988.yann.morin.1998@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=crossgcc@sourceware.org \
    --cc=oron@actcom.co.il \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).