469,963 Members | 2,063 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,963 developers. It's quick & easy.

mix Visual c++ 2003 with Fortran IFC 8

Dear all,

I'm trying compile MSV .NET with IFC v8.

In my c++ source I write
....
extern "C" void _stdcall ROUTINE (...)
...
main
{....
void ROUTINE (...);
....}

In fortran source
subroutine routine (...)
....
return

In my MSV Solution, I included the fortran project in MSV .NET (I
called it "prototipo"), and I built my library ("prototipo.lib"). But
when I try link the solution, I have an error
--------------------
Linking...
LINK : warning LNK4075: ignoring '/EDITANDCONTINUE' due to
'/INCREMENTAL:NO' specification
Creating library .\MyApp_d.lib and object .\MyApp.exp
MyApp.obj : error LNK2019: unresolved external symbol _ROUTINE@12
referenced in function "public: void __thiscall
Applica::IniciaPosCoche(void)" (?IniciaPosCoche@Applica@@QAEXXZ)
..\MyApp_d.exe : fatal error LNK1120: 1 unresolved externals
-------

Any solution

Thanks
Pakea
Jul 22 '05 #1
1 1552
pm****@udc.es (Pakea) wrote in message news:<bf**************************@posting.google. com>...
[snip]
I'm trying compile MSV .NET with IFC v8.


This is all off topic here. Here we only talk about C++ language
issues, not specific compilers (except w.r.t. language issues),
not other languages.

You will want one of the microsoft.public.vc.* news groups for
the Microsoft parts. They are available from www.google.groups,
or from the microsoft public news server. You may find more
guidance over there about what to do with the Fortran parts.
Also, a search at www.google.groups may well make it obvious
which news groups discuss these things.
Socks
Jul 22 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Markus Faust | last post: by
140 posts views Thread by Oliver Brausch | last post: by
1 post views Thread by beliavsky | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.