re distributable files and licencing

[philbrierley]

Hi,

I have dlls in developed in CFV and bought a copy of IVF some time back when an offer was made for a reduced price for CFV users, as I wanted the array visualizer.

The current verision I have says v9.0 and I suspect my initial annual support has expired.

I now want to re build the dlls in IVF to make use of multi threading. I have several questions...

1. If I want the latest version of IVF do I have to repurchase or can I just re sign up for the annual supportto get the latestdownloads?I have a .lic file

2. Steve frequently mentions the documentation in IVF on optimization where I will fine info on multithreading. I can't find this in my v9.0version. Is it anywhere else online or will I have to install the latest verion.

3.In CFV, when creating my redistribution package I just included my cvf dll and a couple of extra dlls to make it work (DFORRTD.DLL & DFORMD.DLL). Is it as easy in IVF? What files will I need to include?

4. Will the latest verion of IVF work if I don't have visual studio, but only have the visual express editions of c++ and VB.

Thanks in advance.

[Steven_L_Intel1]

1. You can certainly purchase a support renewal, but that extends support 12 months from the expiration of your last support. Depending on how long ago your support expired, that may or may not be a good deal. Note however that renewals, at present, take you to the Professional Edition (with MKL) for a steeply discounted price, so it may be worthwhile to buy two renewals if your last one expired long enough ago.

2. There is an "Optimizing Applications" subsection of the on-disk documentation. If you want to look at the current documentation, you can find it here.

3. Well, I hope you didn't try distributing DFORRTD.DLL. DFORRT.DLL, maybe... The concept is the same though the DLLs are different. You'll also need to include the MSVC DLL your application is using (depends on which VS version you have installed.) For VC2005, you'll need to use the supplied merge module if you are using Windows Installer or use the MS redistributable installer.

4. New purchases and support renewals of version 10 include the necessary pieces of Visual Studio. (Student and Evaluation licenses do not include this.) IVF does not integrate with the "express" editions of VC++ 2005 or VB - this is a Microsoft restriction.

[TimP]

Steve has mentioned it several times before: ifort works on command line with VC++ Express. However, this is not so useful now that the purchased version comes with a version of VS GUI support.

[Steven_L_Intel1]

You might still want to use VC++ 2005 Express if you have a mixed-language application, but you cannot build the C and Fortran pieces together in the same environment using the Express Edition. You'll have to compile the C code separately and link in the object or library,or do it from the command line.

One comment (which is in the Installation Guide, but I know nobody reads that). If you DO want to use both VC++ 2005 Express AND the Visual Studio 2005 Premier Partner Edition that comes with IVF, uninstall VC Express before installing Fortran, and then reinstall it afterward, or else the VSPPE environment won't install properly.

[philbrierley]

Steve,

I downloaded the documentation, (the 3.5mb zip file) twice and on each occasion I could see the help menues pane on the left but when I selected anything no content appeared.

It sounds to me that distributing IVF dlls is a little more involved than distributing CVF dlls. I need to include all the required files in my own installation rather than running some 3rd party installation to make the dlls I've created work on other machines. Are details of whatexact files arerequired in the documentation anywhere? With CVF it was only a couple of extra dlls.

[Steven_L_Intel1]

I don't know why you can't read the documentation. It is a Windows-standard .chm format.

The only thing that complicates the issue of redistributing IVF DLLs is that Microsoft Visual C++ uses shared assemblies for VC2005 so getting that right can sometimes be tricky. On the Fortran side, it's the same as CVF, just different DLLs.

That said, we intend to move to shared assemblies in the future as that solves a lot of problems, especially on 64-bit systems.