On Wed, 2 Oct 2013 23:16:36 -0700 Marc MERLIN <[email protected]> said:
> On Thu, Oct 03, 2013 at 12:01:57PM +0900, Carsten Haitzler wrote: > > it *IS* the "out of the box" experience with terminology in git. it > > requires no configuration, no special theme or changes. it's the default. > > if you are on a package and that package has altered the default > > experience, then look at that. if it's an older release - then i am unsure > > why you have tabs but not the gfx overlay for it as i added that at about > > the same time. but it is the default out-of-the-box thing for terminology > > (as far as i am concerned as future releases are based off what is > > currently in git). > > Understood. It then just douns like the package I got is bad. > > I tried to build from source, but: > checking pkg-config is at least version 0.9.0... yes > checking for TERMINOLOGY... no > configure: error: Package requirements ( elementary >= 1.7.0 eina >= > 1.7.0 eet >= 1.7.0 evas >= 1.7.0 ecore >= 1.7.0 ecore-evas >= > 1.7.0 ecore-file >= 1.7.0 edje >= 1.7.0 emotion >= 1.7.0 > ecore-input >= 1.7.0 ecore-imf >= 1.7.0 ecore-imf-evas >= 1.7.0 > ecore-ipc >= 1.7.0 efreet >= 1.7.0 ethumb_client >= 1.7.0 ) were not > met: > > Package ecore-cocoa was not found in the pkg-config search path. > Perhaps you should add the directory containing `ecore-cocoa.pc' ecore-cocoa is for mac osx support.. you have zero need of that... but that list above didnt even list ecore-cocoa.... where on earth did that come from? i CAN tell you for sure that terminology doesnt ask for ecore-cocoa... at all... and nothing in efl core REQUIES it. it smells like some kind of indirect dependency was added to whatever efl packages you use and thus it is being sucked in... but how this got added, i reallyu don't know as ecore-cocoa shouldnt even build without being on osx... thus how it can become a dep... beats me. > And none of my packages seem to have ecore-cocoa > core > libecore-con1 > libecore-dev > libecore-evas1 > libecore-fb1 > libecore-file1 > libecore-imf1 > libecore-input1 > libecore-ipc1 > libecore-x1 > libecore1 > > > > Would that be easy to add? > > > > ugly to add without exposing it via elm - its kind of violating the efl > > layers and digging into a layer underneath that is not exposed. > > That's probably true, although it's a minor worry when your WM is hung and > you're trying to type in any terminal to rescue your system but you can't > because they're not getting typing input :) i'd argue that your wm being hung is in and of itself the big problem... and with compositing... you can focus all u like. compositor wont render anything you can see... :) fix your nfs... etc. :) (or ensure any data the wm needs from libs to binaries to data are local and not on nfs) :) > Thanks for your answers. > Marc > -- > "A mouse is a device used to point at the xterm you want to type in" - A.S.R. > Microsoft is to operating systems .... > .... what McDonalds is to gourmet > cooking Home page: http://marc.merlins.org/ > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
