On 10/28/13 18:21, Carsten Haitzler wrote: > On Mon, 28 Oct 2013 17:31:44 +0900 Cedric BAIL <cedric.b...@free.fr> said: > > > On Mon, Oct 28, 2013 at 4:27 PM, Carsten Haitzler <ras...@rasterman.com> > > wrote: > > > On Mon, 28 Oct 2013 14:45:38 +0900 Cedric BAIL <cedric.b...@free.fr> said: > > >> On Mon, Oct 28, 2013 at 11:49 AM, Carsten Haitzler <ras...@rasterman.com> > > >> wrote: > > >> > On Sat, 12 Oct 2013 11:43:33 +0900 Jérôme Pinot <ngc...@gmail.com> > > >> > said: > > >> > > > >> > great.. but how do you EXTRACT this info then from the lib? :) it's a > > >> > lib.. it can't execute on its own... and printfing such strings on > > >> > every > > >> > fn call is just anti-social :) > > >> > > >> I would have said : > > >> #define EFL_BUILD_DISTRO "MyDistro" > > >> #define EFL_BUILD_VENDOR "Main Tainer <f...@bar.org>" > > >> #define EFL_BUILD_VERSION 42 > > > > > > ummm... ok - and so then we have tyo rely on application executables > > > specifically finding these and printfing them or stuffing them into > > > dialogs? > > > > We could put those variable also in the pkg-config, but I was inclined > > on using that in our .e-crashdump.txt infra. So plain C code there. > > that's the point i was hinting at.. if its just some strings inside the > libs... > then we need special stuff to extract it. if we add it to pc files or > otherwise > make it easy to find... then thats useful. What about this? https://phab.enlightenment.org/D288
> > >> >> Hi, > > >> >> > > >> >> During the Enlightenment French League^W^W dinner, we had this idea of > > >> >> having a configure option for the EFL to setup a string identifying > > >> >> the > > >> >> compiler/maintainer/distribution of the build. Several projects use > > >> >> this > > >> >> kind of string, for instance TexLive, LibreOffice or POV-Ray. It can > > >> >> be > > >> >> use to find quickly the maintainer, to generate automatic bug reports > > >> >> and most important, blame someone else (not you, no, really). > > >> >> > > >> >> There are several way to accomplish this during configuration: > > >> >> > > >> >> POV-Ray uses the COMPILED_BY="Main Tainer <f...@bar.org>" environment > > >> >> variable > > >> >> > > >> >> TexLive uses --with-banner-add="Tex Live 2013/MyDistro Main Tainer > > >> >> <f...@bar.org>" > > >> >> > > >> >> LibreOffice uses several options: > > >> >> --with-distro="MyDistro" > > >> >> --with-vendor="Main Tainer <f...@bar.org>" > > >> >> --with-build-version="42" > > >> >> > > >> >> It seems to me that the LibreOffice options are better. > > >> >> > > >> >> What do you think about this? -- Jérôme Pinot http://ngc891.blogdns.net/
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
