I know, it would be important for BCC and MSVC, too. Not for me, but if we want not to lose anything on this, we may want to deal with it. The current problem is the double pass needed for BCC/MSVC, one without HB_DYLIB, and one with it, for .dlls.
One solution could be to permanently use HB_DYNLIB if someone requests a .dll enabled build for these compilers. This means that each generated final executable will have an export table. It doesn't cause any harm as far as I could tell, besides some minor size increase. So in essence we will split the BCC/MSVC builds into two flavours for those who are bothered by this disadvantage. Official builds can be done with HB_DYNLIB. Assuming we have enabled HB_DYNLIB, the .dll generation logic should still be added to the GNU-make system, and I wonder if there is anyone wanting to do this. Brgds, Viktor On Tue, Feb 17, 2009 at 12:06 PM, Przemyslaw Czerpak <[email protected]>wrote: > On Tue, 17 Feb 2009, Szak�ts Viktor wrote: > > Other opinions of this topic? > > Can .dll creation be implemented using our GNU-make system? > > It is in MinGW builds. > > best regards, > Przemek > _______________________________________________ > Harbour mailing list > [email protected] > http://lists.harbour-project.org/mailman/listinfo/harbour >
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
