Give Wine apps the look and feel of GNOME or KDE


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Give Wine apps the look and feel of GNOME or KDE
# 1  
Old 01-10-2008
Give Wine apps the look and feel of GNOME or KDE

Thu, 10 Jan 2008 16:00:00 GMT
Wine allows users to run Windows programs natively under Linux without paying a dime. However, there's a tiny problem: programs running in Wine don't look so great. They don't even try to fit into your native GNOME or KDE color scheme or use your preferred fonts. You could use a Windows theme, but themes make Wine run extremely slowly. Luckily, with a little configuration editing, it's easy to make Wine applications look at lot more like the rest of the apps on your desktop.


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Linux

[FC17 x86_64]KDE/Gnome switch

Hi, I've got a Fedora 17 x64 with KDE already running. I want to switch to Gnome, which is installed. How can I do that? Cheers, Chrisdot (0 Replies)
Discussion started by: Chrisdot
0 Replies

2. Shell Programming and Scripting

Backup & restore Gnome Desktop and all settings in Gnome

Hi I'm looking for scripts to backup & restore Gnome Desktop and all settings in Gnome. (0 Replies)
Discussion started by: ccc
0 Replies

3. Shell Programming and Scripting

Actively merge kde 3.x and gnome 2.x menus

ok, here's the scoop, google has similar, but nothing that quite fits the bill. here is what I'm up against: i have a linux system that is running both kde 3.x and gnome 2.x, selectable via gdm. the kde 3.x app menu is heavily modified and i'm looking for a way to import that over to the... (0 Replies)
Discussion started by: macphail
0 Replies

4. Linux

file location for GNOME auto startup apps

I know how to add an apps to auto-start in GUI, but I'd like to know how to do it mannualy. So where is the file saved to by GUI ? (1 Reply)
Discussion started by: honglus
1 Replies

5. Linux

Help:- Just clean installed OpenSUse10 with Gnome, now want KDE

I've just done a brand new full clean install of OPenSUSE 10 and thought I'd take a look at Gnome. Having spent a day playing with it I've decided I prefer the familiarity I have with KDE. How do I now install KDE? I've tried logging off to log back on with a different envionnment but KDE... (1 Reply)
Discussion started by: Mark Ward
1 Replies

6. UNIX Desktop Questions & Answers

KDE & Gnome, wat is the difference?

i have been reading some atticles but i still do not understand the diferrence btw KDE & Gnome. Someone once told me he prefers Gnome to KDE 'coz of it's audio support & Redhat says ver 7.3 has KDE 3.0 & Gnome 1.4. So could someone explain? (2 Replies)
Discussion started by: da_gee
2 Replies

7. UNIX for Dummies Questions & Answers

FreeBSD 4.4 Uninstalling KDE or GNOME

Hey all :) I finally got around to installing FreeBSD 4.4, which considering it's my first attempt with *nix, didn't go too badly. I've managed to configure X and everything else, but I've got a bit of a problem, lol. I installed KDE and GNOME. I had a rough idea as to what they were, but I... (5 Replies)
Discussion started by: hellz
5 Replies
Login or Register to Ask a Question
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)