Re: [Freedos-devel] FreeDOS Build Tools
Hi, There are a lot of libraries that are used to BUILD FreeDOS from source. If those libraries were all together, it would make the build process easier. I also think that it would encourage some code re-use because the library to do (x) function is readily available to be included instead of searching for something. FreeDOS would then provide "extensions" to the DOS API. For example, CATS could be the standard internationalization library. When you download the build tools, you automatically get this library and if you need to rebuild FDISK, it's already there (as it's a build requirement for FDISK) and if you wish to make a new application using CATS for internationalization, it's readily available without having to search the web or dig through FreeDOS source to find it. I spend 8+ hours a day programming at my job. I know how crazy it can be building something and one team used one library to build something and another team uses a different library, but the output of the libraries are the same, but the call requirements are different. Case in point. I do Java development at work and some people use Jackson for JSON processing and others use GSON to process JSON. The resulting output is the same, but calling the two and how classes are setup to interface with these APIs are different. -T On Mon, Jan 11, 2016, 5:48 PM Rugxulo wrote: > Hi, > > On Mon, Jan 11, 2016 at 1:59 PM, Antony Gordon > wrote: > > > > If a package called FreeDOS Build Tools/Headers or whatever was built, > what are > > the common 3rd party libraries, such as internationalization, for > example that we > > could include to make building (re-building) things easier? > > I don't know how feasible that is (at least, for explicitly 16-bit DOS > only stuff). There are some libs (e.g. msglib, suppl, d-flat ... > probably many more that I forgot), but they are fairly scattered, so I > don't know if they are much (re)use outside of one or two specific > apps. > > > -- > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS Build Tools
Hi, On Mon, Jan 11, 2016 at 1:59 PM, Antony Gordon wrote: > > If a package called FreeDOS Build Tools/Headers or whatever was built, what > are > the common 3rd party libraries, such as internationalization, for example > that we > could include to make building (re-building) things easier? I don't know how feasible that is (at least, for explicitly 16-bit DOS only stuff). There are some libs (e.g. msglib, suppl, d-flat ... probably many more that I forgot), but they are fairly scattered, so I don't know if they are much (re)use outside of one or two specific apps. -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS Build Tools
On 1/11/2016 12:48 PM, Tom Ehlert wrote: >> So in getting back to this developer studio, it appears obvious the >> previous chain that there was no real agreement on an editor. > editor ??? > EDLIN is the official DOS editor ;) > Tom, just made my day! Ralf ;-) --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS Build Tools
Hi, > Just thought I'd bring this back up as I am currently working on > one of the core components to transition it from Borland to OpenWatcom. > In looking at the code, I noticed that for internationalization, > the CATS library is used. right. so far there's no central, shared source for CATS, but take MORE as an easy example. the actual source is kitten.* prf.c talloc.c tcdummy.c for best effects, tcdummy.c should be fitted to Watcom as Watcom probably also has some functions that are - for our needs - overkill. > One version of the FDISK source code > didn't have the source or the library file for CATS. > So in getting back to this developer studio, it appears obvious the > previous chain that there was no real agreement on an editor. editor ??? EDLIN is the official DOS editor ;) > However, we do have a general agreement on the toolset, primarily > because the spec says so, that being OpenWatcom C (or C++) and NASM. Because the spec says so. aha. unfortunately the spec changes every other year. without much discussion ... > LIke I mentioned before, the DOS API is well represented, which > makes this easy. The next task is the supporting libraries, like CATS for > example. > So to take a page from Linux, FreeDOS pretty much includes > OpenWatcom. It supports the core DOS functions. If a package called > FreeDOS Build Tools/Headers or whatever was built, what are the > common 3rd party libraries, such as internationalization, for > example that we could include to make building (re-building) things easier? kitten.* prf.c talloc.c tcdummy.c are shared between a couple of projects. not much else. RTL comes as given by the compiler people Borland or Watcom), and not sooo compatible. Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
