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.
29282 Discussions

Recommended OpenGL approaches

john3
Beginner
‎07-14-2007 12:09 PM
488 Views
Have now installed IVF 10.025 and am finding some strange things happening when compiling and running some of my OpenGL apps.

The last time I asked, Intel seemed to prefer using the auxlib (via use ifopnl) rather than downloading and using glut libraries. Is this still the case? I.E., what is the current OpenGL recommended approach.

Have I missed something when moving from IVF 9 to 10 when using OpenGL?

My OS is Win XP 32 bit. Thanks

John
0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎07-14-2007 01:09 PM
488 Views
"Intel" takes no position on this. Use whichever approach you like best. We provide interfaces to the Windows-supplied OpenGL API through module ifopngl. We also have worked with Bill Mitchell on his f90GL library that uses GLUT. The latter is probably better if you want platform portability, but if that's not an issue, then it doesn't matter.

I don't know of any OpenGL-related differences, but you haven't said what doesn't work.
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.