cvs.gedasymbols.org/archives/browse.cgi | search |
From: | "John S. Fine" <johnfine AT erols DOT com> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Using DJGPP for embedded 486 application. |
Date: | Thu, 21 Oct 1999 16:47:50 -0400 |
Lines: | 27 |
Message-ID: | <380F7BC8.4919@erols.com> |
References: | <7un5q9$hrl$1 AT fe1 DOT cs DOT interbusiness DOT it> |
Mime-Version: | 1.0 |
X-Trace: | u0qoNJyA8NuQg8+wHgvgSt6M5PGkgjc6lnCXrgwwcVg= |
X-Complaints-To: | abuse AT rcn DOT com |
NNTP-Posting-Date: | 21 Oct 1999 20:52:05 GMT |
X-Mailer: | Mozilla 3.01 (Win95; U) |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Alex wrote: > there is someone who know how to use DJGPP for developing software on an I assume you mean "for" not "on". > embedded target 486 Intel processor (without any DOS, DPMI or other software > structures, but only a proprietary RTOS). I've done that. I use my own linker (you can download it from my web page) to link a combination of .o files produced by DGJPP and .obj files produced by TASM (NASM would work almost as well) into an image that can be put directly into the FLASH memory of the target system. When doing something like that you ought to replace a few OS dependant low level routines in the C library, so that common routines like printf can be used in your environmenmt. I didn't do that. I avoided using the entire C library. My C routines only call others of my own routines; No printf or other standard routines. -- http://www.erols.com/johnfine/ http://www.geocities.com/SiliconValley/Peaks/8600/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |