Sponsored Content
Special Forums News, Links, Events and Announcements Software Releases - RSS News MinGW cross compiling environment 2.0 (Default branch) Post 302256933 by Linux Bot on Monday 10th of November 2008 11:00:07 PM
Old 11-11-2008
MinGW cross compiling environment 2.0 (Default branch)

MinGW cross compiling environment is a script that compiles a MinGW cross compiler and cross compiles many free libraries such as GD and SDL. Thus, it provides a nice MinGW cross compiling environment. All necessary source packages are downloaded automatically. License: MIT/X Consortium License Changes:
The shell script has been rewritten as a Makefile and supports partial builds and parallel builds. As usual, this release also supports some new packages and some newer versions of the already supported packages. Image

Image

More...
 

5 More Discussions You Might Find Interesting

1. Programming

Cross compiling under Windows for Linux

I have two headless servers I am writing code for, and a Windows box networked with them. I want to compile my code within an IDE on the Windows box (eclipse most likely) and run the compiled binarys on the Linux boxes. Will this work? Using Cygwin (or MinGW)? Thoughts? Cheers, Ian (8 Replies)
Discussion started by: IanVaughan
8 Replies

2. Linux

Help Cross compiling a kernel for an HP Jornada 728

Hello, I just bought an old Jornada 728 and, as you may know, it comes with Windows CE 3.0. I do not use Windows, so i wanted to create my own linux system for the Jornada. I know there are projects like Jlime, Familiar Linux, 720 Degrees, etc. But i want something based on the distribution i... (1 Reply)
Discussion started by: semash!
1 Replies

3. UNIX for Dummies Questions & Answers

Cross-compiling libiconv for uclinux

Hi everyone, I want to cross-compile libiconv for uclinux to create a static library. I use the following command : ./configure --enable-static --disable-shared --build=i686-pc-linux-gnu --host=nios2-unknown-linux-gnu --prefix=/home/captain/Programs/nios2-linux/uClinux-dist/staging/usr... (2 Replies)
Discussion started by: moganesh
2 Replies

4. Programming

MinGW - Trouble Compiling Guile

This question is not about programming but compiling with GNU GCC/Make. I am not on a UNIX machine but am using the UNIX-like environment MSYS with MinGW for compiling. The problem that I am having is that I cannot get guile to compile. For some reason it cannot find libltdl which is part of... (3 Replies)
Discussion started by: Deluge
3 Replies

5. UNIX and Linux Applications

Cross Compiling Issue of udev-151 for MIPS Little Endain Architecture

Hi All, I am trying to cross compile udev-151 for MIPS little endian architecture. I am configuring like this: ./configure --prefix=$PWD/sree --host=mips-linux-gnu configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then... (3 Replies)
Discussion started by: bsreeram
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)
All times are GMT -4. The time now is 08:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy