2008/1/5, Eric Auer <[EMAIL PROTECTED]>: > > Hi! > > > LIB for libraries. We never really defined a "lib" before because > > FreeDOS doesn't support the shared-library model... > > I would put those in BIN if dynamic and in SOURCE if used to compile
I disagree. I agree with Jim, nowadays, BIN is usually considered as a synonym for exectuable programs (I never liked this idea either, a picture encoded as a file to me is also binary). I guess it tries to match the "programming language", but in this case we sould say "intel-binary"). But for me "source" tries to refer to "human readable" and LIB is not. My opinion would be that, no matter if static or dynamic, a library is a library, neither source nor program. > > 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. > > I would put those in SOURCE > > Actually I would not even use SOURCE but the subdirectory > of SOURCE used by this package. After all, dependencies > should know on which package they depend... And you are making the entire thing dependant on the caprice of the library maker and the name (s)he wants to give to the library package, which goes precisely against the idea of having LIB or INC directories. If I am the FASTHELP developer I know where I have to look for the help files. Why this idea is NOT good for libraries? If someone packs SUPPL and provides several libs (for the different memory models and compilers), why would I have to mess about compiling SUPPL? (according to other posters, doesn't seem to be trivial task). But Eric please it is just an example. Do not turn the conversation towards SUPPL. Aitor ------------------------------------------------------------------------- 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
