This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Craig Vanderborgh <craigv@voxware.com> > I am working with an arm-wince-pe build of GCC and binutils > (versions 3.2 and 2.13 respectively) and I have been able > to successfully create .exe files on X86 linux that run on my > ARM/wince target (an ipaq 3760). Many thanks to all who've > helped me get this far!! > > I am now to the point where I need to create DLL's for my > ARM/wince target. Could someone please, if possible, show > a small example of how to do this for the simplest case. I need > to know what the command line should look like, and what > pitfalls may exist. After someone asked about producing DLLs with 'arm-elf', I remembered somewhere being instructions for creating DLLs with ARM... The 'gcc/config/arm/README-interworking' in the GCC-sources seemed to be that. The part '10.', "How to use dlltool to build ARM/Thumb DLLs" in this document should teach something about this. Generally the GCC-manual would need fixing with the dllimport and dllexport issue, these are documented to be supported with the Cygwin-version for WinNT/PowerPC only, but the BeOS/i386 (ELF-format), ARM/pe, MCORE/pe, MIPS/pe, SH/pe and of course the Cygwin/Mingw/pe on i386 should support these attributes too... Someone recently works with porting Mingw to WinNT/Alpha and also this unofficial 'PE'-port should have this support. But unfortunately not the 'arm-elf' target. Cheers, Kai ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |