From: Rabeeh Khoury <rabeeh@galileo.co.il>
To: linux-mips@oss.sgi.com
Subject: Compilers question
Date: Wed, 16 Jan 2002 21:02:19 +0200 [thread overview]
Message-ID: <3C45CE3B.6080507@galileo.co.il> (raw)
Hi All,
This is not MIPS Linux issue, but I couldn't find out a better place to
post it :)
I have an application I'v compiled with certain toolchain (for MIPS and
other targets), and I want to distribute the application in binary (no
loadable modules or dynamic linked libraries, just plain C files with
headers files that gives out certain API - sort of a low level driver
for hardware access only).
What I need to know, is how I can make sure that when another person
gets my binaries he can link them with his application and work well ?
The factors that I can identify till now are two -
1.. Distribute the binary in ELF format (are there any compilers that
don't support ELF ? )
2.. Compile the binary that it is ABI compliant
Please add more factors that should be checked, or even suggest another
approach to overcome this problem (other than I get the other person
tool chain and compile the sources myself).
Thank you a lot,
Rabeeh
next reply other threads:[~2002-01-16 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 19:02 Rabeeh Khoury [this message]
2002-01-17 13:41 ` Compilers question Alan Cox
2002-01-17 13:41 ` Alan Cox
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=3C45CE3B.6080507@galileo.co.il \
--to=rabeeh@galileo.co.il \
--cc=linux-mips@oss.sgi.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