03-23-2009
configuring packages for cross-platform build
Hi all,
I wish to build a few packages for my embedded target running linux over ARM9. It would be tough for me to compile my packages on target so I need to build on a host machine and then transfer the generated binaries. So I got the source-tarball for the packages I need. Now here are my two requirements:-
a) The host runs linux over a X86 env. So I need to pass appropriate options to the configure script to make sure the end-binaries are for ARM9.
b) While running 'make install' I wish the install to happen in a particular directory where from I can collect the binaries and put them on target. But caveat is that the target directories are not at the same path as that on intermediate build env. (e.g. on host I want the package executable binaries to be collected in /home/rakesh/package-name/bin where as on target it shall be located in /system/bin)
A little research points me that using --target=TARGET can help for point (a) but will that allow me choose CPU(arm926ej-s) and Architecture(armv5tej)?
For point (b) it seemed --prefix=PREFIX (or specifying all bindir, libdir etc) might help, which will make all installations done in specific directories on host thus making it easy to collect binaries to be placed on target but since on target files are placed at different location it will create a problem as they will refer to non-existent locations.
Can somebody suggest me way out. How I can achieve the desired results.
Thanks in advance,
Rakesh
5 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am looking to have UNIX authenticate against Active Directory in a Windows Server 2003 environment, any suggestion? I am very new to UNIX, 2 weeks worth knowledge, if that. Thanks! (3 Replies)
Discussion started by: Optik
3 Replies
2. UNIX for Advanced & Expert Users
I have know some items on cross-platform portable
byte order
alignment
I don't know if there are books or articles on this topic.
your recommendation is appreciated (1 Reply)
Discussion started by: zhongyj
1 Replies
3. UNIX for Dummies Questions & Answers
I'm looking for a really simple to use lightweight database. Ideally something open-source that stores data in a (semi-) human-readable format, in case the software isn't working.
Something cross-platform enough that I can use it on my Linux machine, my Mac, or stick it on a USB stick and... (2 Replies)
Discussion started by: emdan
2 Replies
4. Debian
Hi Ive been trying for days now and i just cannot work this out.
Can someone please tell me if im doing this right.
I've written some python3.3 code and now i want to transfer it to an embedded computer to execute.
My OS is a : Debian GNU/Linux 6.0.7 (squeezez) 32-bit kernel
... (0 Replies)
Discussion started by: RedEyedDog
0 Replies
5. UNIX for Dummies Questions & Answers
Hi Ive been trying for days now and i just cannot work this out.
Can someone please tell me if im doing this right.
I've written some python3.3 code and now i want to transfer it to an embedded computer to execute.
My OS is a : Debian GNU/Linux 6.0.7 (squeezez) 32-bit kernel
The... (1 Reply)
Discussion started by: RedEyedDog
1 Replies
LEARN ABOUT DEBIAN
dh_installmime
DH_INSTALLMIME(1) Debhelper DH_INSTALLMIME(1)
NAME
dh_installmime - install mime files into package build directories
SYNOPSIS
dh_installmime [debhelperoptions] [-n]
DESCRIPTION
dh_installmime is a debhelper program that is responsible for installing mime files into package build directories.
It also automatically generates the postinst and postrm commands needed to interface with the debian mime-support and shared-mime-info
packages. These commands are inserted into the maintainer scripts by dh_installdeb(1).
FILES
debian/package.mime
Installed into usr/lib/mime/packages/package in the package build directory.
debian/package.sharedmimeinfo
Installed into /usr/share/mime/packages/package.xml in the package build directory.
OPTIONS
-n, --noscripts
Do not modify postinst/postrm scripts.
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple
instances of the same text to be added to maintainer scripts.
SEE ALSO
debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
9.20120909 2012-09-10 DH_INSTALLMIME(1)