Is there any example of a shared library (.dll)? No .ma file.

RE: Is there any example of a shared library (.dll)? No .ma file.

Ken Adams — Thu, 14 Apr 2022 19:02:19 GMT

Thank you Jon! At least this gets me to the .cpp compiler errors.

RE: Is there any example of a shared library (.dll)? No .ma file.

Jon Summers — Thu, 14 Apr 2022 14:31:43 GMT

[quote userid="338809" url="~/products/programming/microstation_programming/f/microstation-programming---forum/228331/is-there-any-example-of-a-shared-library-dll-no-ma-file/706549"]my knowledge of the intracacies of how make files work is limited[/quote]

I know how you feel.

Here's an updated version of your bmake file. Keep in mind that I can't test it because I have none of your source code. It's a shot in the dark...

communities.bentley.com/.../KenAdams.zip

RE: Is there any example of a shared library (.dll)? No .ma file.

Ken Adams — Wed, 13 Apr 2022 20:22:17 GMT

communities.bentley.com/.../fplcommon.txt

I confess my knowledge of the intracacies of how make files work is limited. But this attached file does work in producing a usable DLL for my other V8 SS3 applications with no apparent errors.

communities.bentley.com/.../results.txt

RE: Is there any example of a shared library (.dll)? No .ma file.

Robert Hook — Wed, 13 Apr 2022 20:01:01 GMT

Hi Ken Adams,

Back around the 2000 BDN developer conferences Bentley made recommendations to 3rd party developers to Migrate Interpreted MDL code to Native code where that article provides the initial process and steps recommended in the migration chain you are likely need to exercise (now); being:

Migrating to CONNECT (parent topic and below list of migration actions needed between each major release)

Migrate V7 Code
Porting MDL Applications To MicroStation V8 (V8 to XM)
MicroStation V8 XM Edition View Code Updates (XM to V8i)
Migrating MDL Applications To Native Code (V8i to CONNECT)
[Recommended] Become familiar and productive with the new CONNECT APIs.
1. Developer Training > CONNECT API Training, CONNECT APIs
2. SDK Docs > SDK Help and Visual Studio Extensions
[Optional] Due to limited effectiveness in a 1:1 source code migration.
1. MicroStation CONNECT SDK - Introduction (MigrationTools)

HTH,
Bob

RE: Is there any example of a shared library (.dll)? No .ma file.

Jan Šlegr — Wed, 13 Apr 2022 14:40:44 GMT

Hi Ken,

Jon wrote it already: Please attach the file (use Insert > Insert image/video/file tool). Or when you decide to share its content, use Insert > Insert code to ensure it will be readable and not displayed as plain not formatted text.

[quote userid="338809" url="~/products/programming/microstation_programming/f/microstation-programming---forum/228331/is-there-any-example-of-a-shared-library-dll-no-ma-file/706292"]I am simply trying to convert the make file at this point.[/quote]

In the first step, you should remove all macros that makes no sense:

As Jon wrote, they are some definitions, that were used in MicroStation/J era and were not valid even in V8: MSJ_SKIP_SIGNRSCS
Other macros are valid for old MDL (pseudocode) development, not supported in CE: MLINK_STDLIB and everything targeting "MDL shard libraries" with dlo and ml extensions
Check mki files (both in V8 and CE SDK) what is defined as obsolete and remove it or replaced it: E.g. dlmcomp.mki is obsolete from V8 time
Migrate from C to C++, so there are no files with .c extension.

[quote userid="338809" url="~/products/programming/microstation_programming/f/microstation-programming---forum/228331/is-there-any-example-of-a-shared-library-dll-no-ma-file/706292"]It is not as obvious how to use 'myapp' as a template to update this for CONNECT.[/quote]

My knowledge of using shared dll files in MicroStation native apps is limited, but I guess there is no big difference between "main dll" and "shared dll": When dll is to be loaded by MicroStation as "MicroStation application", there must be MdlMain method exported and .ma loader compiled, whereas shared .dll does not contain these definitions.

I recommend also to check dlmlink.mki for overview of DLM_ definitions, that can be used to configure different aspects of build process.

With regards,

Jan

RE: Is there any example of a shared library (.dll)? No .ma file.

Jon Summers — Wed, 13 Apr 2022 07:00:51 GMT

[quote userid="338809" url="~/products/programming/microstation_programming/f/microstation-programming---forum/228331/is-there-any-example-of-a-shared-library-dll-no-ma-file/706292"]I was not more clear about my goal. I have a SS3 DLL I am trying to upgrade to CONNECT[/quote]

OK, that's make sense!

Please insert your entire bmake file rather than a copy. There are a few things in there that are a hangover from MicroStation V7 days. There are some things in there that would not have built correctly in V8.

RE: Is there any example of a shared library (.dll)? No .ma file.

Ken Adams — Tue, 12 Apr 2022 18:49:45 GMT

appName = fplcommon

MSJ_SKIP_SIGNRSCS = 0

DLM_NO_SIGN = 0

privateInc = $(baseDir)

%include mdl.mki

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

#---------------------------------------------
# mdl.mki contains the default rules for creating .rsc, .mo, etc files
#---------------------------------------------
%if defined (MLINK_STDLIB)
libraryExt = dlo
%else
libraryExt = ml
%endif

# Display compile warning in MS/J
moreMdlCompileOpts + -b
#------------------------------------------------
# Set up to use dlmcomp.mki and dlmlink.mki
#------------------------------------------------

DLM_OBJECT_DEST = $(o)
DLM_LIBDEF_SRC = $(baseDir)
DLM_NAME = fplcommon
DLM_OBJECT_FILES = $(o)$(DLM_NAME)$(oext)
DLM_LIBRARY_FILES = $(mdlLibs)dgnfileio.lib $(mdlLibs)toolsubs.lib
dlm_special_linkopt=-Fixed:no

#------------------------------------------------
# Compile the source files for the DLM
#------------------------------------------------
%include dlmcomp.mki

$(o)$(DLM_NAME)$(oext): $(baseDir)$(DLM_NAME).c

#------------------------------------------------
# Use dlmlink.mki to compile the Dynamic
# Load Specification (.dls) file and link
# the DLM.
#------------------------------------------------

%include dlmlink.mki

#---------------------------------------------
# Compile the Dynamic Link Specification
#---------------------------------------------

$(o)fplcommon.dlo : $(baseDir)fplcommon.dls

$(mdlapps)$(appName).dll : $(mdlapps)$(appName).dll
$(msg)
-copy $(mdlapps)$(appName).dll ..\bin\$(appName).dll
~time

RE: Is there any example of a shared library (.dll)? No .ma file.

Ken Adams — Tue, 12 Apr 2022 18:48:50 GMT

Sorry I was not more clear about my goal. I have a SS3 DLL I am trying to upgrade to CONNECT. It is a set of common functions that several other MDLs call. It has no .ma file itself.

I am simply trying to convert the make file at this point.

My SS3 make file looks a little different than my other make files. It has no cmd or typ resources or mki file. It is not as obvious how to use 'myapp' as a template to update this for CONNECT.

RE: Is there any example of a shared library (.dll)? No .ma file.

Robert Hook — Tue, 12 Apr 2022 18:21:34 GMT

Hi Ken Adams,

As Mike requests, if you can provide some brief information related to your workflow or needs it may help provide better recommendations early on.

As Jon suggests, for MDL (.cpp Native Code) both a .DLL + .MA are required "to load" an application and access functionality defined in the .DLL library file - and - common Microsoft DLL library dependencies and common address space interactions are possible w/o need for Inter-Process Communication (a.k.a. IPC named pipes and queues preferred).

For MDL (.cs Managed Code) only a .DLL (standalone) file is generated as output; however behind the scenes the MicroStation .NET loader will create a temporary .MA image if not present "to load" a MDL .NET Addin application.

Bob

RE: Is there any example of a shared library (.dll)? No .ma file.

Jon Summers — Tue, 12 Apr 2022 17:22:41 GMT

[quote userid="338809" url="~/products/programming/microstation_programming/f/microstation-programming---forum/228331/is-there-any-example-of-a-shared-library-dll-no-ma-file"]I have a shared library (stand alone .dll file. No .ma file.) [/quote]

A DLL is intended to be loaded into the address space of a running process. Presumably, that running process wants to access functions implemented in the DLL. One DLL can call functions in another. You can build a DLL using standard tools for Windows. Nothing to do with MicroStation.

When you build an app for MicroStation, the implementation is stored in a DLL. The above rules apply. The running process will be MicroStation. In addition to the DLL rules, MicroStation requires a resource (.ma) file usually of the same name as the DLL. The data contained in that .ma file tells MicroStation what to look for when you key-in mdl load KenAdamsApp.

[quote userid="338809" url="~/products/programming/microstation_programming/f/microstation-programming---forum/228331/is-there-any-example-of-a-shared-library-dll-no-ma-file"]Is there any example of this in the CONNECT SDK?[/quote]

The SDK helps build an app for MicroStation. Why would you build a DLL that is unable to be loaded? One reason might be to have a DLL that stores code common to many of your apps, that each app's DLL can call. That common DLL might want to link with the SDK libraries to provide that common functionality, and it would never be loaded with key-in mdl load KensCommonDll.

If you don't need a .ma file, simply omit the part of your bmake file that generates that resource.

RE: Is there any example of a shared library (.dll)? No .ma file.

Mike Robertson — Tue, 12 Apr 2022 16:29:16 GMT

Please be more specific for what functionality you are looking for, what version of MicroStation you are using, and what programming language.