> make_b32.bat and make_vc.bat are both able to generate > harbour.dlls, but the created .dlls have different names: > harbour-b32.dll using make_b32.bat and harbour-vc.dll using > make_vc.bat. > > I wonder if this is good practice as the actual compiler > used to generate a .dll shouldn't matter for the end user, > so it might be better to simply use harbour.dll in all > cases. > > [ The created .lib should still be named harbour-b32.lib > and harbour-vc.lib (or maybe rather harbour-coff.lib / > harbour-omf.lib) though. ] > > Any opinions?
The reason is - they are not interchangable due to underscore differences. So if you install one dll in system directory it will not work with programs compiled with other compiler. I did not investigate if they can be built in compatible mode for C builds, because the real problem is CPP mode, where name mangling takes place. Although we use extern "C", I do not want to block CPP mode in core dll because for example in Win64 C mode static initialisation does not work. So to me *it makes perfect sense" to have different dll names. Please - do not change it. -- Marek ---------------------------------------------------------------------- W kosciele tez zdarzaja sie wpadki! Smieszny filmik >>> http://link.interia.pl/f1e61 _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
