Compilation Parameters to link dll's or mo files to Native Code

Hi all,

I have received the question below from one of our users in Spain. Could somebody help me?

----------------------------------------------------------------------------------------------------------------------------------------

We need to migrate all our code (more than 400 programs & libraries) to native code in MS SS3, and later migrate them to MS CONNECT version.

Changes in code files (.cpp, .h, .r....) are more or less clear, in fact we have migrated properly basic developments having nor resources neither dependencies (.mo, .dll,..). Our problem appear when these developments have dependencies and we need to link them via the .mke file. We understand the way to create native code and mdl is different, so we are trying to create a base to start (step by step)

Here are our questions:
1. In our development structure, we have several libraries (.mo) working as a "black box". MDL programs ask them for information and the libraries just return the data. These libraries are not only having simple functions, but includes resources, because there are dialog boxes includes (see example L8010000.mke.MDL). Once library is created, we were linking it with the program on the .mke file, as you can see on the sample T8010004.mke.MDL.

How we can implement this process on a native code mke for MS V8i SS3?

2. We are using also external dll's as you can see also on the previous examples. How could we integrate it inside a native code mke?


Summarizing, I am attaching 4 files, 2 "old MDL" .mke + 2 "Native Code" .mke. What do we need to change on the "native code" mke files to succesfully compile?

----------------------------------------------------------------------------------------------------------------------------------------

I have attached the sample files provided by the userCompilation Parameters.zip in a zip file.

Thanks in advance,

Eduardo Cortes

Parents Reply Children
No Data