Public Support

Hi Wolfgang,

thank you for your answer.

I am trying to run the Macro Resolver from my code, but does not seem to work:

cString sessionDir = adtf::services::ant::adtf_resolve_macros(adtf::services::macro::ADTF_SESSION_DIR);

The value of sessionDir is always just "ADTF_SESSION_DIR", both run from plugin description generator and adtf launcher.
I tried to resolve it from both the constructor and the Configure function, neither of them work.

Am I doing something wrong?

Thank you for your help!

Hi Gergő,

You're almost there - does the following snippet work for you?

const tChar* filePath = "$(ADTF_DIR)/path/to/some_file.png";
cString resolvedFilePath = adtf::services::ant::adtf_resolve_macros(filePath);

You mentioned that your plugin loads files relative to the session directory.
While I don't know your use-case I find it odd that a plugin would require files belonging to a session.
The thing is: there is no concept of a session (i.e. *.adtfsession) in the context of the Plugin Description Generator (PDGen)

Would it be possible to load the required files from a location relative to the .adtfplugin or $(ADTF_DIR)?

If the plugin does indeed load files belonging to a specific session, I suggest to load the files as late and lazily as possible.

Regarding the feature request for specifying the working directory (WD):

We can provide an option to set the PDGen's WD with a caveat:
Due to a limitation in CMake < 3.13 there is no obvious way of specifying the WD depending on the configuration (Debug, Release, ...).
This prevents us from setting the WD to the obvious default which is $(ADTF_DIR)/bin and $(ADTF_DIR)/bin/debug respectively.

We will evaluate whether bumping the CMake dependency to 3.13 is an option.

That being said, I believe a macro-based solution fits your use-case best.

- Wolfgang

Hi Wolfgang,

yes, this code works for me. :)

We have a folder for all the configuration files (json files, pictures, etc.) in each ADTF project, that all of the plugins use present is our sessions to access these config files.
This is why (although not ideal) ADTF_SESSION_DIR would be currently the best solution for us to access this folder.

Thank you for your help, I think we will stick with the macro based solution for now.