Hi Viktor,
IMO we'll have to cleanup those few questions in my other
mail (from a few minutes ago), but other than that I fully
agree.
Remaining questions:
- Future hbzlib placement?
I did not investigate zlib/hbzlib problem. After all,
currently it's in contrib. But my experience with some
OpenSource projects (fltk, wxWidgets) shows that they
contain zlib library in source form and they build it
into a separate library (static) if the final platform
does not have it nativly.
On the other hand, PCRE explicitly allows to use it in
binary and *in source* form, provided that the original
Copyright notice is *retained*.
A fragment from a PRCE licence :
---------------------------------------------
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
---------------------------------------------
- gt*, rdd* separate or not? (IMO separate)
I disagree. Having them as separate libraries has no advantages.
I just made some tests with GTs under BCC and including them in
link command changes *nothing*, until you *explicitly* REQUEST
a particular GT. So having them as separate libraries give us
nothing except complications in further link command, as oposed
to putting a *simple* REQUEST in prg source with one common lib.
- What to do with hbmain* libs? Are they really necessary?
AFAIK it allows to build console programs vs GUI programs under
MingW and Cygwin. Linking against mainstd lib builds console
programs. However I may be wrong here, because I've never used
this feature.
- Purpose of hbnulsys?
AFAIK it allows to build programs which do not require *any*
DBF access. It's serves as a plumbing. It has to be a separate
library. Thanks for pointing this.
Finally, VERY important, but not strictly related to that:
Solving the obligatory inclusion of every LICENSE files
in every distribution (binary/source) we release.
I think we have to include ALL such licences either in source
or binary distributions.
We should investigate whether we must include any 3rd party
license texts. If the answer is yes, we must include these
as well (like LICENSE_PCRE.txt, LICENSE_ZLIB.txt) in both
binary and source distributions.
IMO we have to.
--
Marek
----------------------------------------------------------------------
Jozin z bazin! Ustaw jako dzwonek w Twoim telefonie
Pobierz >>> http://link.interia.pl/f1cfa
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
