Yeah, using -qmc2_config_path
is the way to go... however, for the configuration to be really
portable from one system to another, you'd have to make sure that all paths referred to in qmc2.ini (i.e. image directories, dat-files etc.) are the same, and you may want to use relative paths to accomplish that - relative to QMC2's current working directory, that is.
There's been a discussion about this a while ago, and a solution for users who don't want to set the working directory explicitly (for instance through the application icon's properties), but want QMC2 to use its installation path as the working directory automatically. Please see bug tracker ID #23
and the forum-post it links to.
From the QMC2 wiki
(the option is on the 'Front end' / 'GUI' tab of the main setup dialog):
- Set working directory from executable: when this option is set, QMC2 will change its run-time working directory to the path where the running executable is stored -- this may be useful if you want to use relative paths elsewhere in the configuration (i. e. for portable setups).