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

I have a shared library (stand alone .dll file. No .ma file.) Is there any example of this in the CONNECT SDK?

Parents
  • Hi ,

    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



  • 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

  • I was not more clear about my goal. I have a SS3 DLL I am trying to upgrade to CONNECT

    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.

     
    Regards, Jon Summers
    LA Solutions

Reply Children
No Data