Hi Pritpal,
Please let's only upload to Harbour SVN only
those files which are new ones implementing
the Harbour "glue layer". All LibHARU binaries,
sources, headers and so on, should be left out,
and installed separately by builders/users.
We should refer to those by setting up an envvar
(at least in non-GNU make files). I can help you
create these make files.
That basically means the /w32 dir should be
left out from SVN IMO.
There is one alternative option, when we want
to build 'libhpdf' from source to create a fully
self contained Harbour lib. This is also OK,
but in this case we need to distribute and
build zlib and libpng sources too, to make
it complete. (I'd vote to leave this route in
the first round).
BTW, what do you think of the name 'hbhpdf'
rather than 'hbharu'? I'm asking because
internally 'hpdf' is how the lib refers to
itself, and it has the word 'pdf' in it, which
would more clearly show the purpose of the
library.
Brgds,
Viktor
On 2008.05.16., at 3:13, Pritpal Bedi wrote:
Hello Everybody
HaruPDF library is ready for port to (x)Harbour. But I need some
clarifications.
The Tree:
(x)harbour/
/contrib/hbharu .c .h
/hbharu/w32
/hbharu/w32/bcc32 .lib libpng.lib
zlib.lib
/hbharu/w32/mingw .a .def
/hbharu/w32/msvc .lib .def
/hbharu/w32/include .h
/hbharu/tests .prg .ch ...resources
W32 folder is provided by harupdf distribution and contains libs for
Windows.
If the scheme is accepted, let me know, I will try to upload this
weakend.
Regards
Pritpal Bedi, INDIA-USA
--
View this message in context:
http://www.nabble.com/HBHaru.lib---PDF-Library-tp17265829p17265829.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
