> On Oct 31, 2020, at 2:38 AM, Rugxulo <[email protected]> wrote: > > Hi, > > On Wed, Oct 28, 2020 at 7:56 PM Jerome Shidel <[email protected]> wrote: >> >> Aren’t there nearly 100 DGJPP packages? Any others needed or should be added? >> >> Like I said, I don’t use DGJPP and am not very familiar with it. Someone who >> actually uses it should work on making the updated packages. > > Getting all the (huge!) sources and dependencies is the most worrisome > part to me. Not that most people care anyways, it's just tedious > (especially since these will only cross-build). > > The README.1ST or Zip Picker should give you some idea. > > * ftp://ftp.delorie.com/pub/djgpp/current/v2/readme.1st > * http://www.delorie.com/djgpp/zip-picker.html > > Long story short, you don't need much beyond DJDEV*, BNU*, GCC* (and > probably MAK*) for bare minimum. Add GPP* for C++. (Maybe add a > third-party lib like PDCurses or FSU Pthreads or Allegro or Zlib, if > you really want.) > > Everything else is optional. Bison and Flex aren't needed by 90% of > things or people. Even GDB is technically optional (although > RHIDE/RHGDB is obsolete and too old to be much use anymore). TexInfo > is just for documentation, and while somewhat useful, you can do > without (since it's just plain text with hints for navigation) or use > (huge!) GNU Emacs. >
Yup, like I said. It’s enormous, fairly complex, tons of permutations and something that is not part of any of my workflows. I’m not saying it shouldn’t be updated. I’m just saying someone who is familiar with it should provide the update packages. There have been several requests to update DJGPP. So, there is used at least by some. It should not be too difficult for someone who uses the DJGPP toolchain to create some updated packages for it. _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
