> LIB for libraries. We never really defined a "lib" before because > FreeDOS doesn't support the shared-library model, and developers used > different compilers which may not be able to share each others' *.lib > files. But if we need it, then a LIB directory is a good place for it.
I like the idea of a standard LIB directory for developers installing supplementary libraries or replacement C libraries, like my own. The installer could automatically add this directory to the LIB path for compilers like OW. Also, INCLUDE would be good for the same reason. > > INCLUDE would be a good place for any *.h files that are associated > with the libraries in LIB. But I don't think I'd put them under LIB. > This should be a top-level directory. > > > > -jh > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > -- Fall is my favorite season in Los Angeles, watching the birds change color and fall from the trees. David Letterman (1947 - ) See ya ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
