Quote:
Originally Posted by stepk
KUAL looks for valid extensions this way:
1. find all config.xml files under /mnt/us/extensions/ and ./extensions/
1.2. if the current config.xml file doesn't include a "name" property goto 1
1.3. if the "menu" property of this valid config.xml file isn't "json" then goto 1
1.4. if the "menu" property is an absolute path goto 1.5, if it's a relative path make it relative to the location of its config.xml folder
1.5. if the absolute/relative path of this menu.json file is valid process the json file else goto 1
Note: ./extensions in step 1 comes in handy for testing KUAL. Its actual location isn't accessible to end users unless they install usbnetwork.
|
But the current working directory when called from KUAL is /
I think you should disable that for the release versions -
If that means you have to make a few directories or something else (or conditionalize for testing) then do that.
This is *nix not Windows - "/" and "." are never in the search path for good reasons.