View previous topic :: View next topic |
Author |
Message |
BillJohnson
Joined: 31 Aug 2011 Posts: 30 Location: Connecticut
|
Posted: Wed Aug 31, 2011 7:02 pm Post subject: Publishing Single Exe without including Multiple DLLs |
|
|
Hello,
I have developed an application with Visual Studio 2010 and successfully integrating FORTRAN Code. There are multiple projects within a single solution file. Therefore, this results in multiple DLLs including the exe to run the application.
The executable works fine when all the accompanying DLLs are within the same folder as the exe. However, I want to deliver a single executable without any other DLLs.
Does anyone know how to make a single executable without DLLs hanging within the same folder or on the machine? I want to send someone the final executable and have them be able to run the application without anything else install on their machine. Is this even possible?
Regards,
Bill Johnson |
|
Back to top |
|
 |
JohnCampbell
Joined: 16 Feb 2006 Posts: 2615 Location: Sydney
|
Posted: Thu Sep 01, 2011 1:23 am Post subject: |
|
|
Bill,
For a FTN95 win32 executable, you need only salflibc.dll somewhere in the path.
My understanding of this is not guaranteed, but I think that you can not avoid suplying this dll. salflibc.lib is used at link time to link your resulting .exe to the .dll.
I don't think there is a static version of salflibc.lib that can be linked, to avoid inclusion of the .dll. (Lahey provided this equivalent)
Your comment that you have multiple DLLs implies that you are also linking other dynamic libraries. I'm not sure if these are from other suppliers or you have created them yourself. I avoid creating dll's so all my own libraries are static and reside in the .exe.
I have no experience of .NET to comment on the requirements for this.
John |
|
Back to top |
|
 |
BillJohnson
Joined: 31 Aug 2011 Posts: 30 Location: Connecticut
|
Posted: Thu Sep 01, 2011 3:26 am Post subject: |
|
|
Hi John,
Thank you for the reply. Where do I find the salflibc.dll?
Thanks,
Bill |
|
Back to top |
|
 |
JohnCampbell
Joined: 16 Feb 2006 Posts: 2615 Location: Sydney
|
Posted: Thu Sep 01, 2011 4:21 am Post subject: |
|
|
Bill,
Run SALDIAG and you can find out a lot.
or SET or PATH in a dos box will provide the info.
Multiple copies of different versions of salflibc.dll causes problems !
John |
|
Back to top |
|
 |
BillJohnson
Joined: 31 Aug 2011 Posts: 30 Location: Connecticut
|
Posted: Fri Sep 02, 2011 5:24 am Post subject: SALDIAG |
|
|
Hello John,
What is SALDIAG?
Bill |
|
Back to top |
|
 |
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8215 Location: Salford, UK
|
Posted: Fri Sep 02, 2011 6:58 am Post subject: |
|
|
saldiag.exe is a diagnostic tool that you will find it the compiler folder. By default the compiler is installed to
c:\Program Files (...)\Silverfrost\FTN95
This tool can search for copies of salflibc.dll on your machine. |
|
Back to top |
|
 |
|