From: Alfred Perlstein <bright@hotjobs.com>
To: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
Cc: kauer@pheno.physics.wisc.edu, egcs@egcs.cygnus.com
Subject: Re: UNIX resource compiler???
Date: Sun, 31 Jan 1999 23:58:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.05.9901011720520.37756-100000@bright.fx.genx.net> (raw)
In-Reply-To: <199901012158.WAA01589@mira.isdn.cs.tu-berlin.de>
On Fri, 1 Jan 1999, Martin v. Loewis wrote:
> > Do you know of somebody who has written something like a
> > resource compiler for Unix executables (NOT Win32 or Mac)?
>
> Wine (Wine Is Not an Emulator) has a resource compiler for Windows
> resources, which works on Unix. This is probably not what you want,
> though.
>
> If you just want to link the text files into the executable, why not
> just convert them into character array and link them in?
>
> If you want to modify the executable after it has been linked, you
> need to deal with specific executable format. For ELF, there is an
> established interface (libelf) for reading and writing sections.
>
> Please note that it is typically non-trivial to get a file handle for
> the executable that is just being executed, at least in a way that
> works 100%. For example, the file being executed might already be
> unlinked from the file system.
most systems will allows this via /proc your milage may vary.
-Alfred
>
> Regards,
> Martin
>
next prev parent reply other threads:[~1999-01-31 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-31 23:58 Nikolas Kauer
1999-01-31 23:58 ` Alfred Perlstein
1999-01-31 23:58 ` Martin v. Loewis
1999-01-31 23:58 ` Alfred Perlstein [this message]
1999-01-31 23:58 ` Todd Vierling
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=Pine.BSF.4.05.9901011720520.37756-100000@bright.fx.genx.net \
--to=bright@hotjobs.com \
--cc=egcs@egcs.cygnus.com \
--cc=kauer@pheno.physics.wisc.edu \
--cc=martin@mira.isdn.cs.tu-berlin.de \
/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).