From: Carsten H. (T. R. <ra...@ra...> - 2013-04-30 11:58:15
|
On Tue, 30 Apr 2013 18:03:21 +0800 hYde <hyd...@gm...> said: > Since my BIOS has only about 8MB of space, I take Evas + Edje. you'll need ecore, eet and eina too then. (well some of ecore). > May I ask what is pre-merge? efl 1.7.x ... from efl 1.8 we have a single build tree and we have upped our dependencies. 1.8 is not out yet.. but release is scheduled for end of may. > And what really confuses me is I'm not porting it on any OS, just an > environment with framebuffer support, so any OS based config would not > work on my base, still working on stripping the code and figure out > why MinGW always fails on me.. > > > Hi, > > > > this is quite of a hard task and I'd request you to evaluate the > > requirements before digging much. How does coreboot behaves? How much space > > do you have? > > > > Having it to compile should be the simplest task, but then you need to > > implement the OS layers EFL expects in Ecore: main loop (timers, file > > descriptors, ...), I/O (wayland, fb, x11)... Unless coreboot already > > emulates a real OS, you'll have lots of work to do, maybe base yourself on > > PSL1GHT work (PS3 native port). > > > > Also, EFL takes around 5mb by default, if you don't have that memory > > (flash, RAM) you'll have extra work to strip it. > > > > My take on this is: get Evas (pre-merge) and port only it, integrate it > > directly in coreboot. Base your UI in Expedite, as it looks okay using just > > Evas, no other EFL. If you need to strip down, consider using Evas before > > Eina, then you do not rely on other EFL. Yes, you'll end with a fork, but > > your project just need a simple way to show graphics on screen, the extra > > features of EFL are likely unneeded and will do more harm than good. > > > > > > Regards, > > -- Gustavo > > > > On Mon, Apr 29, 2013 at 6:55 PM, hYde <hyd...@gm...> wrote: > > > Hi all: > > > > I've been thinking porting elementary into my open source BIOS loader > > (coreboot), to beautify my BIOS setup menu, but I don't know how to start > > with. > > > > Because the BIOS loader are C code, build with Microsoft Visual C++ > > compiler, the first step I'm trying to do is to make elementary out of the > > box of MinGW, which is very hard. > > > > So I tried to build them with MinGW on my working machine (Windows 7) > > first, to observe the makefile and result, and to make a doable solution > > for MSVC10, but after following the instructions > > > > https://phab.enlightenment.org/w/windows/#windows-64-bits > > > > I keep failing on the autoconf section with errors like : > > > > configure: error: cannot find install-sh, install.sh, or shtool in "." > > "./.." ". > > /../.." > > make: *** [builddir/efl] Error 1 > > > > I'm a real newbie to linux toolchains, stucked here for about two weeks... > > please help me with some tutorials, I'm really hitting the wall, thanks. > > > ------------------------------------------------------------------------------ > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET > Get 100% visibility into your production application - at no cost. > Code-level diagnostics for performance bottlenecks with <2% overhead > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap1 > _______________________________________________ > enlightenment-users mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |