Compilation errors

Did anything change on your system (e.g. new group policies, Windows update, etc.)? Does the same thing happen if you compile the delivered examples? How are you compiling your application (IOW, what is the command line that you are using)? Are you using the MicroStation Developer Shell?

Unfortunately I don't know if anything changed on my system from when I could compile V8i and when I couldn't any longer. It might have, there seems to be lots of updates coming all the time...

I haven't found any delivered examples, so I haven't been able to try them... where are they? I have installed sdk 08110517, but there were no examples there, as far as I can see. I would be very interested in trying them!

 I'm using our own version of mstndevvars.bat which includes those compiler options needed to compile pure mdl, as well as defining some other variables we use and also running bmake on all files in the current directory with the extension mk8i. I have double checked it today and copied some lines from the original again but with no improvement. There is one more difference though - I'm not changing the directory to %msmde% as in mstndevvars since I'm compiling every mk8i file in the current directory and the variables we are using are all based on the compilation taking place in the base directory of the program being compiled. But that part hasn't changed since the days I could compile for V8i.

In our make files I have included  mdl.mki as well as our own mki. Our own mki-file is defining a few variables, such as the appDir depending on the category of the program, where to find some include files of ours, defining the default language to swedish etc. I had to make some changes in this file to make the compilation work for V8i in the beginning, but I haven't made any changes from when it worked to when it stopped working. The directory checks I was writing about takes place in this mki file, so whatever has gone wrong I think have done that before this point - the first half of our mki file.

There are a few definitions at the top of our mki file added by a collegue of mine eons ago. I don't know why they are there so I have tried to remove them just to see if something changes. It does, slightly. I still get a problem with the directory check, but the error messages when removing these changes a little - there is no directory mentioned, just "can't open #include file mdl.h" for example.The lines I commented out were definitions of mdlLibs, publishInc, publichIdsInc, stdlibInc, mdlLibs and rscdir. But still, it's not working!

Lena

Unfortunately I don't know if anything changed on my system from when I could compile V8i and when I couldn't any longer. It might have, there seems to be lots of updates coming all the time...

I haven't found any delivered examples, so I haven't been able to try them... where are they? I have installed sdk 08110517, but there were no examples there, as far as I can see. I would be very interested in trying them!

 I'm using our own version of mstndevvars.bat which includes those compiler options needed to compile pure mdl, as well as defining some other variables we use and also running bmake on all files in the current directory with the extension mk8i. I have double checked it today and copied some lines from the original again but with no improvement. There is one more difference though - I'm not changing the directory to %msmde% as in mstndevvars since I'm compiling every mk8i file in the current directory and the variables we are using are all based on the compilation taking place in the base directory of the program being compiled. But that part hasn't changed since the days I could compile for V8i.

In our make files I have included  mdl.mki as well as our own mki. Our own mki-file is defining a few variables, such as the appDir depending on the category of the program, where to find some include files of ours, defining the default language to swedish etc. I had to make some changes in this file to make the compilation work for V8i in the beginning, but I haven't made any changes from when it worked to when it stopped working. The directory checks I was writing about takes place in this mki file, so whatever has gone wrong I think have done that before this point - the first half of our mki file.

There are a few definitions at the top of our mki file added by a collegue of mine eons ago. I don't know why they are there so I have tried to remove them just to see if something changes. It does, slightly. I still get a problem with the directory check, but the error messages when removing these changes a little - there is no directory mentioned, just "can't open #include file mdl.h" for example.The lines I commented out were definitions of mdlLibs, publishInc, publichIdsInc, stdlibInc, mdlLibs and rscdir. But still, it's not working!

Lena

ah! Thats why I haven't found them. I never use "My Documents"... (everything is on the servers)

I'm probably not doing this right because I can't compile any examples.

 I'm running the mstndevvars.bat first, and then

bmake -dNO_COMPILERS_MKI -dBUILD_USING_NoToolset   <path\makefile>

I get the message  "can't open include file mdl.mki"

Have I missed anything?

Lena

Lena:

I get the message "can't open include file mdl.mki"

Did you install the SDK to its default location? Is that file in folder \MicroStation\mdl\include?

In the Windows command window where you have run mstndevvars.bat, what are the values of environment variables MS and MSMDE?

Regards, Jon Summers
LA Solutions

mdl.mki is in the folder ...\MicroStation\mdl\include

MS is pointing to ...\MicroStation\

MSMDE to ...\MicroStation\mdl\

When I tried to compile the example, I used the standard version of mstndevvars.bat. I just found the mistake I made, I had typed the wrong path to the SDK in the command line (just happened to add \mdl). So now it works to compile the examples... Now I just have to find out what my problem is with my files...

Our modified version of mstndevvars.bat has similar settings as mstndevvars.bat (except that I don't need to type in the paths in the command line so I've got rid of a potential error there...). The differences are the addition of some of our own variables, no change in the active directory, and the command line for running bmake for all make-files in the active directory with -dNO_COMPILERS_MKI -dBUILD_USING_NoToolset added to the command line.  It is quite short:

I still get the message "can't open #include file mdl.h" etc. when compiling. It's when running mcomp

C:\BentleyV8i\MicroStation\mdl\bin\mcomp @make.opt

and make.opt is

Any ideas of where to look next?

/Lena

Lena:

set MS=C:\BentleyV8i\MicroStation\
set PATH=%MS%\mdl\bin;%MS%\mdl\library;%MS%;%MS%\jmdl\bin;%PATH%

Be careful with folder terminator slashes. Your definitions expand to:

MS=C:\BentleyV8i\MicroStation\
set PATH=C:\BentleyV8i\MicroStation\\mdl\bin;C:\BentleyV8i\MicroStation\\mdl\library;C:\BentleyV8i\MicroStation\;C:\BentleyV8i\MicroStation\\jmdl\bin;%PATH%

There are several double terminators in the above line. They may cause problems.

Lena:

set BOLIS_SRC=c:\KALLKOD\mdl\bolis8i
set BOLIS_LIB=c:\kallkod\mdl\bolislib
set BOLIS_APPL=c:\kallkod\mdl\mdlapps
set gensrc=%BOLIS_APPL%\

Be consistent with folder terminator slashes. Your MDL paths are terminated, but your own paths are not. Confusion will follow.

Regards, Jon Summers
LA Solutions