From: "H. J. Lu" <hjl@lucon.org>
To: Kai Tietz <Kai.Tietz@onevision.com>, binutils@sources.redhat.com
Subject: Re: PATCH: windres
Date: Mon, 16 Apr 2007 22:20:00 -0000 [thread overview]
Message-ID: <20070416215849.GA23226@lucon.org> (raw)
In-Reply-To: <20070416210710.GB16652@ednor.casa.cgf.cx>
On Mon, Apr 16, 2007 at 05:07:10PM -0400, Christopher Faylor wrote:
> On Mon, Apr 16, 2007 at 11:20:49AM +0200, Kai Tietz wrote:
> >"H. J. Lu" <hjl@lucon.org> wrote on 13.04.2007 16:41:06:
> >
> >> > Nightmares, ... 8| I begun to modify structure using character arrays
> >...
> >> > I come to the point, that this means for big parts of windres better a
> >
> >> > complete rewrite. Structures with internal/external scope and data
> >> > modifications are really wired.
> >> > May we should first use my last patch, so that the problem is solved,
> >and
> >> > then I will begin to reorganize the windres tool to be host
> >idependent. By
> >> > this I can add some missing resource types to it.
> >> >
> >> > What do you think about my suggestion to continue ?
> >> >
> >>
> >> That is fine with me. If you do this, you don't need to handle
> >> endian and just replace long with int since you will rewrite it
> >> later anyway.
> >
> >This is the patch changing the windres source using int instead of long. I
> >bootstrap it on cygwin 32 and for x86_64-mingw.
> >This patch does not solve the endian problem, reasoned by the use of
> >fwrite/fread.
> >ChangeLog for binutils/:
>
> If you are assuming that int means 32 bits, wouldn't it make sense to
> use a type like u_int32_t which explicitly spells that out?
u_int32_t is a good idea if it doesn't require extra change since
this is a temporary patch until windres can be rewritten properly.
H.J.
next prev parent reply other threads:[~2007-04-16 21:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 13:43 PATCH: w64 native support Kai Tietz
2007-04-11 13:58 ` H. J. Lu
2007-04-11 14:07 ` H. J. Lu
2007-04-11 18:22 ` PATCH: windres Kai Tietz
2007-04-12 15:55 ` H. J. Lu
2007-04-12 16:51 ` Kai Tietz
2007-04-12 18:03 ` H. J. Lu
2007-04-13 14:41 ` Kai Tietz
2007-04-13 14:49 ` H. J. Lu
2007-04-16 10:05 ` Kai Tietz
2007-04-16 21:59 ` Christopher Faylor
2007-04-16 22:20 ` H. J. Lu [this message]
2007-04-17 10:59 ` Kai Tietz
2007-04-18 4:34 ` Christopher Faylor
2007-04-18 9:49 ` H. J. Lu
2007-04-20 13:34 ` Kai Tietz
2007-04-20 13:35 ` H. J. Lu
2007-04-20 13:54 ` Kai Tietz
2007-04-20 14:03 ` H. J. Lu
2007-04-20 13:40 ` Dave Korn
2007-04-20 13:51 ` Kai Tietz
2007-04-20 13:58 ` Dave Korn
2007-04-23 12:26 ` Kai Tietz
2007-04-23 12:44 ` Christopher Faylor
2007-04-23 13:51 ` Kai Tietz
2007-04-23 14:23 ` Christopher Faylor
2007-04-23 14:36 ` Dave Korn
2007-04-23 14:46 ` Kai Tietz
2007-04-23 14:50 ` Christopher Faylor
2007-04-18 11:59 ` PATCH: w64 native support Kai Tietz
2007-06-29 5:37 ` NightStrike
2007-07-12 7:30 ` Nick Clifton
2007-07-24 8:00 ` NightStrike
2007-04-11 14:57 ` Kai Tietz
2007-04-11 15:17 ` Daniel Jacobowitz
2007-04-11 15:24 ` Kai Tietz
2007-04-11 15:43 ` Daniel Jacobowitz
2007-04-11 15:49 ` Kai Tietz
2007-04-11 17:34 ` Daniel Jacobowitz
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=20070416215849.GA23226@lucon.org \
--to=hjl@lucon.org \
--cc=Kai.Tietz@onevision.com \
--cc=binutils@sources.redhat.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 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).