forums.silverfrost.com

I have an FTN95 (32bit) Studio project which requires the addition of a static library and dll's as references. When using SLINK outside Studio I always put the static library (.LIB) file before the d ...

Brilliant. That update to the FTN95 integration works fine. I can now add GINO dll's as references and get the project to link and run.

I have a separate problem which I will raise as a separate to ...

I'm not sure how to load a dll as an extra linker option. I have tried adding 'lo ginlibs9.dll' but the linker does not recognise 'lo'. I have tried adding just the dll name, but this does not work ei ...

Robert, Is there any progress on correcting the FTN95 integration with Visual Studio for 32 and 64bit win32 projects viv-a-vis the incorrect linking order and addition of .NET libraries when they are ...

But the 32bit .NET libraries are automatically added to the project as part of the FTN95 plugin to Studio.

How does one remove them from the project?

Robert,

A further problem with using Silverfrost FTN95 with Visual Studio is that if you change the project to x64, you get the following link error:

FTN95.EXE "C:\Users\Public\Documents\ ...

Robert, It lokks like coleague has found the cause of the problem:

1. If I take the slink command that VS shows in the build.log file:

slink.exe "C:\Program Files (X86)\gino\v9.0sal\GMWINE ...

We normally use a command file of the following form:

echo lo %1.obj>%1.lnk
echo subsystem windows>>%1.lnk
echo lo %GINO%\ginlibs9.dll>>%1.lnk
echo file>>%1.lnk
slink $%1.l ...

Yes, it is a Win32 project. I was unsure whether to add the import library under the compiler/source option or as a linker option, but neither work. The build log follows:

///////////////////////// ...

Using our GINO libraries created as a dll, there is no problem linking these with an FTN95 object file using SLINK in interactive mode, but when trying to create a FTN95 project in Visual Studio 2017 ...

It appears that the routine fgetc returns different values when compiled with the 64bit SCC compiler than under the 32bit SCC compiler.

A simple test using fputc and fgetc using the byte values 1 t ...

So after working with Paul Laidler, it looks like that the floating point exception was occurring within the OPENGL32.DLL (wglSwapBuffers) and that the default action for the 64bit Silverfrost compile ...

Paul, I sent an e-mail with a zip file attachment to 'ftn95@silverfrost.com' with title FAO Paul Laidler last Thursday. Did you not receive it?

Thanks for your optimism Ryan, but have you got your OpenGL examples working with the Silverfrost FTN/64 compiler under Windows? The project you pointed to only uses gfortran, which we don't have a pr ...

I have been concerned about the conversion between 64 bit pointers and addresses being passed to the 32bit OPENGL32.DLL, but it seems to work with the Intel and now Absoft 64 bit compilers, so there i ...