devkitARM: release 24 and supporting libraries


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News devkitARM: release 24 and supporting libraries
# 1  
Old 12-15-2008
devkitARM: release 24 and supporting libraries

This project is for homebrew console development tools based on the gnu compiler collection with additional tools and libraries to aid programming each supported console. The windows variants will be MinGW based.

ImageImage

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. HP-UX

Ftp command nlist not supporting in sftp

Hi, We are using HP-UX. Previously we were using ftp to connect to remote list the text file name and copy into local file with .ls extension. For this we are using nlist RBOBAR*.txt DMSFT.ls now we want to convert the integration with sftp. So In sftp nlist command is not supported. How can we... (8 Replies)
Discussion started by: Pelins
8 Replies

2. Shell Programming and Scripting

Ssh not supporting sudo and sqlplus commands

Hi Guys , I was facing an issue some thing like , I have to connect remote machine and should execute few commands over there , I am able to run some simple commands , but below commands are throws error like not found. eg : sudo su - username and sqlplus user/pwd@db , srvrmgr commands etc ... (8 Replies)
Discussion started by: chandini
8 Replies

3. Solaris

Supporting NIC speed

Hi, I have few Solaris (9 and 10) servers, whose consoles are running on 10 MBPs. Now, Network team is changing their switch, which doesn't support 10 MBPs and we need to check if console all of those servers will support 100MBPs or more. Is there any way to check supported (or maximum supported)... (7 Replies)
Discussion started by: solaris_1977
7 Replies

4. Red Hat

Redhat enterprise 6.2 virtulazation KVM NOT supporting more than 40GB

Hello, I have installed Red Hat 6.2 version & KVM installed, file system limited is only 40GB, how do i create more than 40 GB ( I need to install more than 100 GB file system ) Could you please me. Thanks... (2 Replies)
Discussion started by: Inamadugu
2 Replies

5. Shell Programming and Scripting

Supporting Others' Scripts

Not a programmer by profession but job entails perl/expect scripting. Generally that means that I/others write scripts for what I/they want/need and I/they support mine/theirs. Due to a recent departure, I now have to support some perl scripts with 10k+ lines of code and little documentation.... (2 Replies)
Discussion started by: Vi-Curious
2 Replies

6. Red Hat

RHEL 3 is not supporting SCASI disk

Hi guys I am having some SCASI Driver issue while installing the RHEL 3 on SunFire X4200 series Server so can anyone help me out as how to get rid off from this problem. (2 Replies)
Discussion started by: daya.pandit
2 Replies

7. Linux

RHEL 3 is not supporting SCASI Disk

Hi guys I am having some SCASI Driver issue while installing the RHEL 3 on SunFire X4200 series Server so can anyone help me out as how to get rid off from this problem. (1 Reply)
Discussion started by: daya.pandit
1 Replies

8. HP-UX

tool supporting SPL

Hi, i heard a tool called "Source reader" used in HP-ux that supports for SPL language.I am also told it works similar to ctags and cscope as in C.Does anybody know abt this tool? If so plz share it with me ..... (0 Replies)
Discussion started by: vijaya2006
0 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)