5 More Discussions You Might Find Interesting
1. UNIX and Linux Applications
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
2. Programming
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
3. UNIX for Dummies Questions & Answers
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. Linux
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
5. Programming
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
WINEGCC(1) Wine Developers Manual WINEGCC(1)
NAME
winegcc - Wine C and C++ MinGW Compatible Compiler
SYNOPSIS
winegcc [options] infile...
DESCRIPTION
winegcc is a gcc wrapper which tries to provide a MinGW compatible compiler under Linux. This is most useful to Win32 developers who can
simply take their MinGW code from Windows, and recompile it without modifications under Winelib on Linux. wineg++ accepts mostly the same
options as winegcc.
The goal of winegcc is to be able to simply replace gcc/g++/windres with winegcc/wineg++/wrc in a MinGW Makefile, and just recompile the
application using Winelib under Wine. While typically there are small adjustments that must be made to the application source code and/or
Makefile, it is quite easy to do them in a fashion that is compatible between the MinGW and Wine environments.
This manual will document only the differences from gcc; please consult the gcc manual for more information on those options.
OPTIONS
gcc options: All gcc options are supported, and are passed along to the backend compiler.
-Bprefix
This option specifies where to find the executables, libraries, include files, and data files of the compiler itself. This is a
standard gcc option that has been extended to recognize a prefix ending with '/tools/winebuild', in which case winegcc enters a spe-
cial mode for building Wine itself. Developers should avoid prefixes ending with the magic suffix, or if that is not possible, sim-
ply express it differently, such as '/tools/winebuild/', to avoid the special behaviour.
-fno-short-wchar
Override the underlying type for wchar_t to be the default for the target, instead of using short unsigned int, which is the default
for Win32.
-mconsole
This option passes '--subsystem console' to winebuild, to build console applications. It is the default.
-mno-cygwin
Use Wine's implementation of MSVCRT, instead of linking against the host system's libc. This is necessary for the vast majority of
Win32 applications, as they typically depend on various features of MSVCRT. This switch is also used by the MinGW compiler to link
against MSVCRT on Windows, instead of linking against Cygwin's libc. Sharing the syntax with MinGW makes it very easy to write Make-
files that work under Wine, MinGW+MSYS, or MinGW+Cygwin.
-municode
Set the default entry point of the application to be the Unicode wmain() instead of the standard main().
-mwindows
This option adds -lgdi32, -lcomdlg32, and -lshell32 to the list of default libraries, and passes '--subsystem windows' to winebuild
to build graphical applications.
-nodefaultlibs
Do not use the standard system libraries when linking. These include at a minimum -lkernel32, -luser32, -ladvapi32, and any default
libraries used by the backend compiler. The -mwindows option augments the list of default libraries as described above.
-nostartfiles
Do not add the winecrt0 library when linking.
-Wb,option
Pass option as an option to winebuild. If option contains commas, it is split into multiple options at the commas.
DEFINES
winegcc defines __WINE__, for code that needs to know when it is being compiled under Wine. It also defines WIN32, _WIN32, __WIN32,
__WIN32__, __WINNT, and __WINNT__ for compatibility with MinGW.
BUGS
The dllimport/dllexport attributes are not supported at the moment, due to lack of support for these features in the ELF version of gcc.
Static linking is not currently supported against Wine's DLL. As a result, the -static, --static, and -Wl,-static options will generate an
error.
AUTHORS
winegcc was written by Dimitrie O. Paun.
SEE ALSO
gcc(1), winebuild(1), wrc(1), wine(1), Winelib User Guide, Wine Developers Guide.
Wine 1.2-rc6 October 2005 WINEGCC(1)