>> [ But, can't wholeheartedly endorse the concept of hbmaindllp, it looks >> like an ugly and incomplete kludge. So I'm not sure we should use >> hbmk2 to find out what's missing from it. Could be I'm misunderstanding >> the purpose. ] > > I do not understand. hbmaindllp makes exactly what it should and makes it > well though in my opinion it should be moved to separate directory and > divided into few files. The main files should conatin only hb_vmExecute() > and hb_vmProcessSymbolsEx(). Only these two function are necessary to > create .DLL with .prg functions compiled with -gc2. Wrapper for other > functions (if any) should be added inb seprate files. F.e. dllxvm.c with > functions necessary for -gc3 code, dllext with extended API functions, > etc.
IMO not very elegant solution. It needs manual syncing with all of our public APIs (that means something will *always* be missing or out of sync), and part of the APIs logic needs to be replicated there manually (which means it will be sometimes wrong due to typos or lack of testing), and it's currently incomplete (pbly for above reasons). That's what I meant by my attributes. > Forget about it. -nohblibs will be enough. If user does not understand > what he should do then he should not make it at all. I've added it, please test it. It can be useful if someone wants to manually assemble Harbour core liblist. F.e. when using hbmk2 with a different Harbour version (and automatic options don't make it right), or trying to find out dependencies, or when using customized Harbour build or just plain experimenting. It's not meant for normal user though :) Brgds, Viktor _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
