Problems compilingxfm mdl project

Re: Problems compilingxfm mdl project

Krister Surell — Mon, 02 Apr 2012 13:23:50 GMT

Finally my friends!

compOpts was the way to go.

compOpts + -i"$(GEOINCS)"

Thanks,

Krister

Re: Problems compilingxfm mdl project

Jeff Bielefeld — Fri, 30 Mar 2012 20:59:03 GMT

Krister,

Jon is correct, if not using C/C++ native code then use of...

compOpts + i$(GEOINCS)

....in your .mke file is correct. It seems the definition of the GEOINCS environment variable may not be pointing to the location of the Bentley Map header files. From your development shell, what does the following command produce?

dir %GEOINCS%\XfmApi.fdf

Re: Problems compilingxfm mdl project

Krister Surell — Fri, 30 Mar 2012 20:43:58 GMT

Hi,

My make file now look (partly) like this:

%ifndef CC_LANGUAGE

langSpec = swedish

%endif

privateInc = ./$(langSpec)

#privateInc = C:\PROGRA~2\Bentley\MICROS~1\Map\mdl\include

%include mdl.mki

dirToSearch = $(GEOINCS)

#dirToSearch = $(genSrc)

%include cincapnd.mki

This results in a massive error listing (see below). Switching the comments (quick fix) will make my project compile.

E:\Lagring\prj\Samlingskartan_v8i\src\SamText\txt_edit.mc(42) : error: can't ope

n #include file xfmElement.fdf

E:\Lagring\prj\Samlingskartan_v8i\src\SamText\txt_edit.mc(42) : error: No such f

ile or directory

C:\PROGRA~2\Bentley\MICROS~1\MICROS~1\mdl\include\xfmApi.fdf(22) : error: can't

open #include file xfmApiDef.h

C:\PROGRA~2\Bentley\MICROS~1\MICROS~1\mdl\include\xfmApi.fdf(22) : error: No suc

h file or directory

C:\PROGRA~2\Bentley\MICROS~1\MICROS~1\mdl\include\xfmApi.fdf(23) : error: can't

open #include file xfmApiTyp.h

C:\PROGRA~2\Bentley\MICROS~1\MICROS~1\mdl\include\xfmApi.fdf(23) : error: No suc

h file or directory

C:\PROGRA~2\Bentley\MICROS~1\MICROS~1\mdl\include\xfmApi.fdf(24) : error: can't

open #include file xfmSettings.h

C:\PROGRA~2\Bentley\MICROS~1\MICROS~1\mdl\include\xfmApi.fdf(24) : error: No suc

h file or directory

C:\PROGRA~2\Bentley\MICROS~1\MICROS~1\mdl\include\xfmApi.fdf(36) : error: expect

ed ,, got *

C:\PROGRA~2\Bentley\MICROS~1\MICROS~1\mdl\include\xfmApi.fdf(37) : error: expect

ed ,, got IDENT

...

Re: Problems compilingxfm mdl project

Jon Summers — Fri, 30 Mar 2012 20:43:11 GMT

[quote user="Jeff Bielefeld"]%include mdl.mkidirToSearch = $(GEOINCS) %include cincapnd.mki[/quote]

That works when you're using the C++ build tools. It appends /I $(GEOINCS) to the C++ compiler command.

If you're building a pure MDL application, as Kristel implies he is, then you need this in the make file:

compOpts + i$(GEOINCS)

Re: Problems compilingxfm mdl project

Jeff Bielefeld — Fri, 30 Mar 2012 19:57:13 GMT

Krister,

The bmake_opt variable is used to define options for bmake.exe such as -I option which defines the Include (.mki) file path, not the header file includes. What you need to do is update your applications .mke file by extending the paths in which the compiler looks for the header and function prototype files. Something such as the following where GEOINCS has been defined in your shell to point to the folder containg the required header files etc...

%include mdl.mkidirToSearch = $(GEOINCS) %include cincapnd.mki

Re: Problems compilingxfm mdl project

Krister Surell — Fri, 30 Mar 2012 19:53:55 GMT

BMAKE_OPT is set as defined by the geodevshell.bat, ie:

REM ---------------------------------------------------------------------------------------------------------

REM Extend the BMAKE_OPT environment variable setting.

REM ---------------------------------------------------------------------------------------------------------

SET BMAKE_OPT=%BMAKE_OPT% -I$(GEOINCS)

SET BMAKE_OPT=%BMAKE_OPT% +dDEBUG

I could change this to anything but the output in make.opt would still be the same.

I've solved it for now by "stealing" the privateInc variable in the make file, but that meant I had to copy my llanguage files to the parent directory. Ugly, but it works.

/Krister

Re: Problems compilingxfm mdl project

Jon Summers — Fri, 30 Mar 2012 19:43:01 GMT

[quote user="ksurell"]I know I'm a old timer but I never seem to get the time to enter the VC-world[/quote]

The transition is really quite harmless!

All the MDL examples in the V8i SDK are C++ (.cpp) files. In fact , there's almost no C++ in those files, but they do use the Microsoft C++ tools (i.e. Visual Studio compiler and linker) to build an application.

The bmake (.mke) files look similar to what you are used to. bmake invokes the Microsoft tools for you and builds a native-code application DLL.

Of course, you need to acquire Microsoft Visual Studio, but I believe that the Express editions work OK.

Re: Problems compilingxfm mdl project

Jon Summers — Fri, 30 Mar 2012 19:38:52 GMT

[quote user="ksurell"]When I add xfm-includes it can't find them eventhough BMAKE_OPT is updated[/quote]

Please post your definition of BMAKE_OPT.