21 - Enhanced Properties & Investigate lib_path

[Kaiqgs]

[Kaiqgs]

in lib_path investigation

So far, lib_path has been necessary because we need to load the libs dynamically, and it's much easier to know lib_path at bundled_time, rather than at develop/build_time on the editor.

Currently we do a check to see if it's being executed from the editor

        if (endsIn(exePath, FMB_EDITOR_SUFFIX)) {

Trying to match build/x86_64-osx/dmengine or build/x86_64-win32/dmengine.exe.

Then, for the case it's from the editor, lib_path is queried.

            const char* resPath = FMODBridge_dmConfigFile_GetString("fmod.lib_path", "");
                (...)
               strcpy(newPath, projPath);
            len += projPathLen;

            if (resPath[0] != '/') {
                strcat(newPath, SEP);
                len += 1;
            }

            strcat(newPath + len, resPath);

Later lib_path is used to build the exe+lib path.

    strcpy(exePath, libPath);
    strncat(exePath, SEP LIBPREFIX "fmod." LIBEXT, maxPathLen);
    libOpen(FMODBridge_dlHandleLL, exePath);

    strcpy(exePath, libPath);
    strncat(exePath, SEP LIBPREFIX "fmodstudio." LIBEXT, maxPathLen);
    libOpen(FMODBridge_dlHandleST, exePath);

ongoing discussion

I have raised my points on this issue. I think eventually a plug-and-play solution will be more interesting.

• Does Defold SDK provide an API to query extension installation or extension files?
• Is it acceptable for this extension to access .internal lib, or is it too hacky?

[britzl]

We need to look into the fmod lib_path separately but please go ahead and merge this for now.