From: Karl B. <ka...@tu...> - 2000-09-26 14:04:42
|
Hi All, large_printf(), vsprintf(), errored out on me on the 9-24-00 cvs source. I've downloaded the latest cygwin, and will try doing a build with it soon. (the cygwin cvs tag is 1-1-4, the version is 1001.4.19) To just run the SDCC binaries on Win32, all that is needed is this cygwin1.dll. Of coarse the bcc compiled exe's will be nice because they run a bit faster. I want to think about how to make an easier install under windows. Some ideas are to add cygwin1.dll to the bin pkg, and/or use the bcc native exe's. Also it might be nice to switch to a self-extracting exe for a bin pkg. Maybe add a really simple example program that should compile out of the box. Cheers, Karl. ----------------------- At 02:45 PM 9/25/2000 -0600, you wrote: > >On 25-Sep-2000 Karl Bongers wrote: >> Otherwise, I think a neat solution would be to post a binary native >> package with the Borland compiled binaries on the web site. > >I am planning on doing just this when we get the ds390 support solid >enough to make a release of a TINI-DK (which should be pretty soon, >unless Johan can keep up his current rate of bug-finding >indefinitely!). > >By the way, I am using sdcc with Cygwin 1.1.2 (not quite the latest; >there is a 1.1.4 DLL patch release available (as far as I can tell >there was no 1.1.3 at all), but there was no compelling reason to >upgrade) without any troubles. Note that I only make use of the >compiler/assembler/linker, so I can't speak to the working (or not) >of the simulator/debugger. > > Peace, > Kevin >_______________________________________________ >sdcc-devel mailing list >sdc...@li... >http://lists.sourceforge.net/mailman/listinfo/sdcc-devel > |