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-BUILD(1) General Commands Manual GO-BUILD(1)NAME
go - tool for managing Go source code
SYNOPSIS
go build [-o output] [ build flags ] [ packages ]
DESCRIPTION
Build compiles the packages named by the import paths, along with their dependencies, but it does not install the results.
If the arguments are a list of .go files, build treats them as a list of source files specifying a single package.
When the command line specifies a single main package, build writes the resulting executable to output. Otherwise build compiles the pack-
ages but discards the results, serving only as a check that the packages can be built.
The -o flag specifies the output file name. If not specified, the name is packagename.a (for a non-main package) or the base name of the
first source file (for a main package).
OPTIONS
The build flags are shared by the build, install, run, and test commands:
-a force rebuilding of packages that are already up-to-date.
-n print the commands but do not run them.
-p n the number of builds that can be run in parallel. The default is the number of CPUs available.
-v print the names of packages as they are compiled.
-work print the name of the temporary work directory and do not delete it when exiting.
-x print the commands.
-compiler name
name of compiler to use, as in runtime.Compiler (gccgo or gc)
-gccgoflags 'arg list'
arguments to pass on each gccgo compiler/linker invocation
-gcflags 'arg list'
arguments to pass on each 5g, 6g, or 8g compiler invocation
-ldflags 'flag list'
arguments to pass on each 5l, 6l, or 8l linker invocation
-tags 'tag list'
a list of build tags to consider satisfied during the build. See the documentation for the go/build package for more information
about build tags.
For more about specifying packages, see go-packages(7).
For more about where packages and binaries are installed, see go-gopath(1).
SEE ALSO go-install(1), go-get(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-05-13 GO-BUILD(1)