Those 8.3 DOS filenames can be limiting for package names, so I like the idea of moving the DJGPP packages to DJ_xxxxx instead of DJGPP_xx. I saw your note on GitLab about this, too.
If you're also rebuilding the DJGPP packages (newer version?) you might rename the packages to something like this: djgpp_bn (DJGPP binutils) ==> dj_bin djgpp_bs (DJGPP Bison) ==> dj_bison djgpp_db (DJGPP gdb) ==> dj_gdb djgpp_fq (DJGPP faq) ==> dj_faq djgpp_fx (DJGPP Flex) ==> dj_flex djgpp_gc (DJGPP gcc) ==> dj_gcc djgpp_gp (DJGPP gpp) ==> dj_gpp djgpp_mk (DJGPP make) ==> dj_make djgpp_ob (DJGPP Objective-C compiler) ==> dj_objc djgpp_rh (DJGPP rhide) ==> dj_rhide djgpp_tx (DJGPP Texinfo) ==> dj_txinf djgpp (DJGPP environment) ==> djgpp [keep the same] Those names make more sense to me. Jerome just released the T2209 test build, but maybe this could be added to the T2210 test build? On Thu, Sep 1, 2022 at 11:07 AM Paul Dufresne via Freedos-devel <[email protected]> wrote: > > I added a file dj_alego.zip (using my suggestion for renaming files > from djgpp_ab, to dj_abcde) to my DJGPP packages at: > > Allegro is a library to write games... this is the version on DJGPP > site: 4.2.2. > > https://gitlab.com/dufresnep/freedos-djgpp > > Supposing that you managed to have all the files there inside your > FreeDOS VM, you could build an allegro test.c file by: > > fdnpkg insall-nosrc djgpp > fdnpkg install-nosrc djgpp_bn.zip > fdnpkg install-nosrc djgpp_gc.zip > fdnpkg install-wsrc dj_alego.zip > > cd FreeDOS\Source > cd dj_alego > unzip all422s.zip > [some errors will happen because the file contains some more than 8 chars > name... I said yes] > cd allegro > cd tests > gcc -o test.exe test.c -lalleg > test.exe > strip test.exe [make the file smaller by removing debugging symbols] > > _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
