forums.silverfrost.com

[stfark1]

Creating a project module and when I do, it asks for existing routines. When I select .for files, it creates a pointer to the file for execution. I would like to transfer this executable module to another processor but the pointers to the .for modules do not exist on the different processor. Is there a way when one creates an executable file to "pull" the .for programs into the executable module so that the complete executable can be transferred to the different processor and be "self contained" Sid Kraft

[JohnCampbell]

Sid,

I am not aware of modules or .mod files being required on another processor once the .exe file has been generated.

The .mod files are required for compilation of other .for files that reference these modules.
The .obj or .dll files are required for building the .exe files, but I don't think the .mod files are required at linking.
Once you build the .exe it should be transferable to another processor, to be executed.
This is providing you have not used .dll files when building the .exe. In this case you would need the .dll files on the other processor, but not the .mod files.

[wahorger]

John is right, and a clarification is needed.

If you are using Clearwin+ (i.e. building windows/dialogs), then the Silverfrost DLL's are automatically used (invisible to you, unless you look deeply into a .MAP file) and need to be on the target machine.

As an example, this is from one of my main programs .MAP file: