- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Hello everyone,
I am building a Windows in-process COM server with version 10.1.019. It is essentially a wrapper for some older Fortan code we are incorporating into our main program. Anyway, whenever I add a method to the wrapper interface via the .hie file, my compile order goes wonky and I get errors in the auto-generated, "do not edit these", files. Several of the auto generated files can't access a particular module from some of the other auto generated files. So I do a file-specific compile on each one in order, and then it is able to build the project.
Specifically, IProgram.f90 can't find a module in ProgramTY.f90.
ProgramTY.f90 can't find a module in Program_global.f90.
Program_global.f90 can't find a module in clsfactty.f90.
So when I do a file-specific compile in the reverse order (clsfactty, Program_global, ProgramTY, IProgram), it works. Any ideas?
Thanks!
Jason C.
I am building a Windows in-process COM server with version 10.1.019. It is essentially a wrapper for some older Fortan code we are incorporating into our main program. Anyway, whenever I add a method to the wrapper interface via the .hie file, my compile order goes wonky and I get errors in the auto-generated, "do not edit these", files. Several of the auto generated files can't access a particular module from some of the other auto generated files. So I do a file-specific compile on each one in order, and then it is able to build the project.
Specifically, IProgram.f90 can't find a module in ProgramTY.f90.
ProgramTY.f90 can't find a module in Program_global.f90.
Program_global.f90 can't find a module in clsfactty.f90.
So when I do a file-specific compile in the reverse order (clsfactty, Program_global, ProgramTY, IProgram), it works. Any ideas?
Thanks!
Jason C.
コピーされたリンク
0 返答(返信)
