Silverfrost Forums

Welcome to our forums

My older EXEs do not start with new SalfLibc

25 Apr 2014 11:17 #13989

If i install latest FTN95 it runs my older compiled programs OK. But if i substitute SalfLibc with the latest SalfLibc libraries then my older EXE files do not start with this message:

http://i1320.photobucket.com/albums/u523/rrr2005r/export_pcx_zps46c9fa03.png

I need to recompile the code with new libraries for this message not to appear. What can cause this ?

25 Apr 2014 2:05 #13993

I think that __export_pcx will be present in both dlls but it is possible that the signature has changed. For example, normally functions are exported as 'extern 'C'' and maybe for some reason this function was changed.

As a general rule a user exe should be kept with the dll used when building. Anything else is a bonus.

25 Apr 2014 3:33 #13996

Well, that will be cumbersome, sometimes I have to look at older code compiled with specific parameters, so I keep EXEs with the data it produced. And all was working OK for 25 years, hope to find exact reason and there will be no need for keeping old DLLs with each of 1000 EXEs I have 😭

25 Apr 2014 6:55 #13999

I will have a look at the history of this function.

26 Apr 2014 8:13 #14001

This turns out to be a regression and it has been fixed for the next release.

It affects the following functions

import_gif@ ddb_paint@ import_pcx@ export_pcx@

26 Apr 2014 10:13 #14004

Cool! Many, many thanks, Paul

Please login to reply.