Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29280 Discussions

Migrating from CVF to Intel

esantiago1
Beginner
‎09-12-2006 06:36 PM
400 Views
Our company is currently looking at moving to IVF from CVF. We currently have a 5-user concurrent network license of the CVF 6.6 Pro. We would like to replicate this functionality and license setup as much as possible with IVF.

I want to make sure that we are going about this correctly.

1. IVF is available with concurrent licensing for it's standard product and not the pro, so we would get a 5-user concurrent license of IVF standard.
2. In order the have the IMSL functionality of CVF Pro, we would have to then get 1 floating license from Visual Numerics for each platform type we see ourselves developing on.
3. From what I understand we also need a Microsoft development environment installed for each installation of IVF. This was not the case with CVF, so is this necessary?

Thanks,
Eli
0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎09-12-2006 10:20 PM
400 Views
Yes, a Microsoft development product is necessary. You seem to understand the concurrent licensing issues.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.