mysolver.def(15) : fatal error LNK1118: syntax error in 'VERSION' statement

Question

Hello MSC Community,

I would like to reproduce a given example to generate a DLL from a user-written subroutine and at the last steps, I get an error.

Here the details:

Initial situation:

The example I do have ran under Windows 7 Professional Service Pack 1 (64bit) with the compiler: Microsoft Visual Studio 2017 Community Edition ; and with the Adams version: Adams2017.2 ,

My OS: Windows 7 Enterprise Service Pack 1 (64bit),

My Compiler: Microsoft Windows SDK v7.1 (see installation information in “ sdk-compiler-information.txt ”),

My Adams version: Adams2018 ,

The Example is an user-written subroutine and is written in C . I will call this file " file.c ".

My steps taken:

I opened the command prompt " Windows SDK 7.1 Command Prompt CMD Shell Optimized for Windows SDK " from the SDK installation folder.

In the command prompt, I went to the " file.c " directory with the command " cd " ( C:\Users\Username\Desktop\ ).

Preparation for the compile step: I executed the command " Set NO_FORTRAN=1 ".

Compile step: " cl /c /Ox /MD file.c "; This step generated an object-file called " file.obj "

Link step: With the command " adams2018 cr-u n file.obj -n file.dll " I tried to generate a Libary which is called " file.dll ". This step generated the following: 
 
 file.dll , 
 mysolver.bat , 
 mysolver.def .

The error occurs after the execution of the command from the last step. For the whole report of the command prompt after this step please look at the file “ Error.txt ”

Result: I generated a complete empty DLL (0kb) and normally it should have like 28kb.

These steps were given to me and except for small changes, I did copy the given steps. The differences to the given steps are the following:

In the example, an additional step had to be carried out. The step was to set the right environment for the compiler and for this the Batch-File " vcvars64.bat " was executed.

Example command: " adams2017_2 cr-u n file.obj -n file.dll " --> My command: " adams2018_1_SE cr-u n file.obj -n file.dll "

In the example, the own command prompt from Adams was used to execute the whole steps. I couldn't do this, because I didn’t have the admin permissions to execute " vcvars64.bat " (For now my workplace is in a university where I don’t have any admin permissions). In the end, I decided to get along with the SDK compiler that was the only available except my access to my private notebook which will be mentioned later on.

My tries to get rid of the error:

I added " /EHsc " in the compile command --> " cl /c /Ox /MD /EHsc file.c ". I still did get the same error and same results.

I did execute the whole steps again in a new setup, which is available to me with my private notebook. The new set up is:

OS: Windows 7 N Professional Service Pack 1 (64bit) 
 
 Compiler: Microsoft Visual Studio 2017 Community Edition (same as from the example) 
 Adams version: Adams 2018.1 Student Edition (The Technical Support told me the academic license is permissible for my intention)

--> First, for this setup, I used the own Adams command prompt from the installation folder ( C:\Program Files\MSC.Software\Adams Student Edition\2018_1\common\AdamsSetup.bat )

--> Next, for the setup, I used the VS command prompt " x86 Native Tools Command Prompt for VS 2017 ". For this first I had to execute the Batch-file " C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars64.bat” to set up the 64bit environment.

==> Results of these two modes in this new setup: The same error occurs ( mysolver.def(15) : fatal error LNK1118: syntax error in 'VERSION' statement )

If you can give me some hints, I would be very happy.

Thank you!

Kind regards,

A. Balaj

Attached Files (1)

Text-Data.zip

Stats

mysolver.def(15) : fatal error LNK1118: syntax error in 'VERSION' statement

Community Guidelines