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.
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)
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)
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)
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)
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)
GO-GET(1) General Commands Manual GO-GET(1)NAME
go - tool for managing Go source code
SYNOPSIS
go get [-a] [-d] [-fix] [-n] [-p n] [-u] [-v] [-x] [ packages ]
DESCRIPTION
Get downloads and installs the packages named by the import paths, along with their dependencies.
When checking out or updating a package, get looks for a branch or tag that matches the locally installed version of Go. The most important
rule is that if the local installation is running version "go1", get searches for a branch or tag named "go1". If no such version exists it
retrieves the most recent version of the package.
OPTIONS -a, -n, -v, -x, -p
The -a, -n, -v, -x, and -p flags have the same meaning as in 'go build' and 'go install'. See go-build(1).
-d The -d flag instructs get to stop after downloading the packages; that is, it instructs get not to install the packages.
-fix The -fix flag instructs get to run the fix tool on the downloaded packages before resolving dependencies or building the code.
-u The -u flag instructs get to use the network to update the named packages and their dependencies. By default, get uses the network
to check out missing packages but does not use it to look for updates to existing packages.
For more about specifying packages, see go-packages(7).
For more about how 'go get' finds source code to download, see go-remote(7).
SEE ALSO go-build(1), go-install(1), go-clean(1).
AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).
2012-06-15 GO-GET(1)