> I'm looking for a way to run test executables - created by QBS - outside > of a QBS environment. To me this looks problematic since you can define > runVars inside QBS that are not known outside of QBS. > > Any idea how to handle this?
An idea, not a solution. You could generate a shell wrapper script together with each executable where you export all relevant variables. Then you call the wrapper script instead of the executable, or you would source the wrapper script. I guess you are most interested in dynamic library resolution which is handled by the environment variables: - LD_LIBRARY_PATH on Linux - DYLD_LIBRARY_PATH on MacOs - PATH on Windows For how to find out all relevant library paths for an application product, you can get an inspiration from https://code.qt.io/cgit/qbs/qbs.git/tree/share/qbs/modules/cpp/setuprunenv.js You might even use these functions as they are. _______________________________________________ Qbs mailing list [email protected] https://lists.qt-project.org/listinfo/qbs
