For you is not complicated, but for other user will be
each operation increase difficult, and capability to made error
also here we can find user that miss how compile sample, me included
having "#pragma option:hbmk2 mylib.hbc" in source code cover
complexity
made possible copy and past from internet to a new project
All that needs to be done is to supply an .hbp file
for projects published on the internet. Since you will
never be able to control the whole build process of
apps from .prg source code, such .hbp file should be
distributed anyway. Include .hbc files in these project
files is IMO a no brainer. Project files are common
in most (non-interpreted) programming languages.
I find this #pragma option much less intuitive in its
current form. It needs some more brainstorming to make
it like using/import in other languages. We need to cover
headers, REQUESTs and give it sleeker syntax.
Przemysław
#pragma option:hbmk2 mylib.hbc allow compile with hbmk2 without know
how
request MYLIB is different because instruct only that is need a
library/symbol
In my source i have already included
REQUEST HB_MEMIO
but when compile with hbmk2 i must adding hbmemio.lib
or
#pragma option:hbmk2 hbmemio.hbc
First off, I don't think newbies will start with hbmemio,
but anyway, any "newbie" should be used to the fact that
each functionality is made available through libs. This
has been so since Clipper '85. And these libs needs to be
linked to app. This doesn't seem very complicated or unusual
to me. The last thing a newbie will think of is using #pragma
(which is new syntax), and using it with a relatively obscure
and not well documented option as 'hbmk2:option'.
Much easier to read 'hbmk2 --help' output, or just take
a glance on almost any of our projects inside the repository.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
