On Mon, Jun 8, 2009 at 8:19 PM, Przemyslaw Czerpak<[email protected]> wrote:
> On Mon, 08 Jun 2009, Szak�ts Viktor wrote:
>> Thank you very much. I've removed it from hbmk2, and
>> left a note that it should be linked manually when appropriate.
>
> I think that you should also add an option to disable adding standard
> harbour libraries when DLL is linked. It will help to locate used functions
> missing in hbmaindllp at link time. Otherwise user can still create wrong
Okay, I understand that. (-nohblibs f.e. which could work in all modes)
[ 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. ]
> binaries. I think that you can simply bound it with -shared option.
> When -hbdyn is used and static DLL is created then you can use hbmaindllp
> instead of standard harbour static libraries. Otherwise when -[fix]shared
> switch is used explicitly then you can enable linking with harbour.dll
If I understand correctly this means a new 'neutral' mode which is neither
shared nor static.
Now only static mode is supported with -hbdyn:
links with standard Harbour static libraries
If I add -[fix]shared support for -hbdyn:
links with harbour.dll
3rd new mode:
links with hbmaindllp?
Wouldn't it be enough to add -shared support and leave
hbmaindllp to the user? After all, a separate switch should
be used anyway (-something or -lhbmaindllp).
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
