> Viktor Szakáts wrote: >> But, back to your actual problem, you must be using some other legacy >> functions which makes this file pulled in. IMO you could simply solve your >> problem by changing this legacy call to the new equivalent, and legacyco.c >> would not be linked at all. That's the reason I moved these legacy wrappers >> in separate files in the first place. > > Hmmm... I do not thing I need this file (or use any legacy function from it), > because after I delete it from hbwin.lib I have no problem linking > application.
It may also be a link order problem. If this is so, you can try swapping the order of hbwin and your own lib, so that your own MESSAGEBOX() symbol gets caught first. It may also be possible that some hbwin code itself still refers to some legacy function names. In this case it should be fixed. > And I do not remember the exact link time warning about duplicated > MessageBox, I just have a habit to delete this file from Makefile :) If you see it, please post it. > I general this is no problem about me, but I was interested in legacy support > policy. IMO it's important, others may have the same problem, and the whole point of this legacy/renaming movement is to avoid the problem you're just having :) What I noticed is that old hbwin legacy functions miss the new guard '#if !defined( HB_WIN_LEGACY_LEVEL_OFF )'. Please feel free to add this to legacyco and legacycd, this way you can simply build Harbour with: set HB_USER_CFLAGS=-DHB_WIN_LEGACY_LEVEL_OFF And all these old symbols will be excluded. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
