I'm using v8i select series 4 and I was wondering if anyone could tell me how to specify in the MicroStation Developer Shell that I would like bmake to use the compile built into microstations and not the vs 2005 compile?

Jan,

Below is the make file that I am attempting to run that is getting the error:

#
# menus MDL Make File
#

%include mdl.mki

%if defined (_MakeFilePath)
 baseDir = $(_MakeFilePath)
%else
 %if defined (powerc) || (m68k)
  baseDir = /
 %else
  baseDir = ./
 %endif
%endif

objectDir = $(baseDir)
privateInc = $(baseDir)
appDir = $(baseDir)

# Define symbol for files included in our link and resource merge
Objs = \
 $(objectDir)menus.mo \
 $(mdlLibs)alertlib.ml
   
Rscs = \
 $(objectDir)menus.rsc \
 $(objectDir)menus.mp

# Compile the MDL source using MCOMP
$(objectDir)menus.mo : $(baseDir)menus.mc $(baseDir)menus.h

# Compile Resources (RCOMP OF MAIN RESOURCE)
$(objectDir)menus.rsc : $(baseDir)menus.r $(baseDir)menus.h

# LINK MDL APPLICATION
$(objectDir)menus.mp : $(Objs)
 $(msg)
 > $(objectDir)make.opt
 $(linkOpts)
 -a$@
 $(Objs)
 <
 $(MLinkCmd) @$(objectDir)make.opt
 ~time

# USE RLIB TO MAKE .MA FILE
$(baseDir)menus.ma : $(Rscs)
 $(msg)
 > $(objectDir)make.opt
 -o$@
 $(Rscs)
 <
 $(RLibCmd) @$(objectDir)make.opt
 ~time

Please, use Insert > Insert code tool always! you need to share a code snippet. Or attach is as a text file (when the snippet is long).

It's not only confusing to try to read code formatted as a plain text, but in the case of make files, where indentation is important, it can change how code is understood.

I do not see any critical error in your code, even few things does not make any sense. It seems you use very very very old templates, not make files from V8 applications. E.g to check whether _MakeFilePath exists does not make sense, because it's "always existing" variable. Also, to thing whether to support PowerPC or Motorola 68000 is nonsense, because MicroStation V8 exists only for Windows (and these platforms do not exists anymore, and the processors are used for other applications).

How your environment is defined? Are MS and MSMDE variables defined correctly? And are not other variables (like BUILD_USING_VS2005 or any other), that can switch mki procesing in unwanted way, defined?

To analyze complete log how macros are evaluated, should help to understand why right compilers are not called .... and something from AssertToolSet.mki is used instead of it.

Regards,

  Jan

Please, use Insert > Insert code tool always! you need to share a code snippet. Or attach is as a text file (when the snippet is long).

It's not only confusing to try to read code formatted as a plain text, but in the case of make files, where indentation is important, it can change how code is understood.

I do not see any critical error in your code, even few things does not make any sense. It seems you use very very very old templates, not make files from V8 applications. E.g to check whether _MakeFilePath exists does not make sense, because it's "always existing" variable. Also, to thing whether to support PowerPC or Motorola 68000 is nonsense, because MicroStation V8 exists only for Windows (and these platforms do not exists anymore, and the processors are used for other applications).

How your environment is defined? Are MS and MSMDE variables defined correctly? And are not other variables (like BUILD_USING_VS2005 or any other), that can switch mki procesing in unwanted way, defined?

To analyze complete log how macros are evaluated, should help to understand why right compilers are not called .... and something from AssertToolSet.mki is used instead of it.

Regards,

  Jan