On Tue, 10 Jun 2014 18:54:01 +0200 "Dominig ar Foll (Intel OTC)" <[email protected]> said:
can i just point to: http://docs.enlightenment.org/stable/elementary/group__App.html specifically the elm_app_info_set which is key... and thereafter elm_app_prefix_dir_get(), elm_app_bin_dir_get(), elm_app_lib_dir_get(), elm_app_data_dir_get() and elm_app_locale_dir_get(). these handle proper runtime relocation of your app and should be able to detect where it is installed, where the data files are, extra binaries are, library related files, and locale files. use the most specific one. i.e. if app binary were: /opt/app/foo/bin/myapp the prefix would be: /opt/app/foo bin dir: /opt/app/foo/bin lib dir: /opt/app/foo/lib data dir: /opt/app/foo/share/foo locale dir: /opt/app/foo/share/locale it follows standard unix/linux hierarchy. examples of usage: https://git.enlightenment.org/core/elementary.git/tree/src/bin/test.c#n894 https://git.enlightenment.org/apps/terminology.git/tree/src/bin/main.c#n2829 https://git.enlightenment.org/apps/rage.git/tree/src/bin/main.c#n67 that does the setup, provides compile-time info and runtime info that then allows relocation handling at runtime. move /opt/app/foo to /home/user/apps/blah and it should work just fine. note. this applies only if you are using an efl native app, but there are enough of those in tizen, so it's worth noting this. it's important for things like multiuser to work, allow apps to install anywhere etc. also note - there is a lower level api that does this too if you are not at the elementary widget level. all the libraries and tools shipped with efl use this to handle relocation: http://docs.enlightenment.org/auto/evas/group__Eina__Prefix__Group.html > Hello, > > we have spent a considerable amount of time to remove all the hard coded > path in Tizen in order to enable multiuser, it would be nice to see the > maintainers blocking them to come back at the Gerrit review phase. > We will look on how to add and autocheck during the build, but that will > come late on the process and will be painful each time that the check > will fail, so better to get it done earlier. > > Thanks in advance for your cooperation. > > Dominig ar Foll > Senior Software Architect > Open Source Technology Centre > Intel SSG > > Le 10/06/2014 14:35, Jean-Benoit MARTIN a écrit : > > Hi all, > > > > For Multi-user architecture, hardcoded paths were removed from Tizen > > common source code. > > > > New bugs have been created. > > Here the list: https://bugs.tizen.org/jira/issues/?filter=13223 > > > > If your code contains hardcoded paths, could you please check the wiki > > page about Multi-user Architecture. > > https://wiki.tizen.org/wiki/Multi-user_Architecture > > > > Don't hesitate to contact me if you need help. > > > > Best Regards > > Jean-Benoît > > _______________________________________________ > > Dev mailing list > > [email protected] > > https://lists.tizen.org/listinfo/dev > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev > -- Carsten Haitzler (The Rasterman) <[email protected]> _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
