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

Accessing library in Visual Studio .NET 2003

keithweber
Beginner
‎02-05-2007 05:57 PM
451 Views

I am trying to access a library and keep getting the following error:

error LNK2019: unresolved external symbol _myfunction@12 referenced in function _MAIN_

I have the "Additional Library Directories" under the Linker -> General tab of the project set to the directory of my library and the "Additional Dependencies" under the Linker -> Input tab of the project set to the name of the library. Is there anything that I am missing?

Thanks in advance for any help!

0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎02-05-2007 10:09 PM
451 Views

You are either calling from C/C++ with __stdcall specified, or you have Fortran options that apply the STDCALL calling mechanism to this routine. Is that correct for the routine and is the case of the name (lowercase) correct?

What is the structure of your application? All Fortran? Mix? What type of project (Console?) What are the compiler options shown on the Fortran Command :Line property page?

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.