Re: [E-devel] Blend2D - a gfx framework with dynamic pipelines support

2017-12-03 Thread Carsten Haitzler
On Sun, 3 Dec 2017 01:23:22 -0300 Vinícius dos Santos Oliveira
 said:

> Hi all,
> 
> I'd like to ask what is your opinion on this library[1].
> 
> It's a library where you call all the draw operations that comprise the
> drawing pipeline, and, when you call `context_end`, the pipeline is
> compiled (yep, JIT). Somehow exciting because it allows very interesting
> optimizations.
> 
> But it's also boring, because you have to recompile the whole pipeline
> every time some value changes (i.e. probably every frame if you're writing
> a game).
> 
> But there is also plans to support a shader language (with a working
> experimental code for a useless math functions language). With this support
> added, you could compile the rendering pipeline only once and evaluate it
> for every frame.
> 
> The thing I like is support for Bézier curves. It's like OpenGL done for 2D
> rendering. The API seems a lot like cairo, so it's mostly transparent
> (except for the shaders).
> 
> Maybe EFL could add a backend forked from SDL2 using this library to
> generate the screen bits. Or maybe there is not enough info flowing the
> higher layers to the lower layers to make this idea actually useful.
> 
> Maybe some of these ideas could be stolen by the EFL project.
> 
> I'd like to hear opinion from you guys about this project. You guys are
> experienced with 2d gfx code and I'd love to hear anything you guys have to
> say about this project.
> 
> [1] https://blend2d.com/

Requiring c++ means then lower end systems will require libstd++ which will
bloat our our requirements. no? from that view, i don't like it much.

also i dislike the idea of a jit. i would prefer something like "pre-compile
all permutations into special case functions then runtime call the
right/matching one". the built-in jit is going to cause architecture support
issues for us on various platforms where we do work (maybe not with optimized
ASM but we work). a quick peruse of b2dpipe doesn't tell me what architectures
are or are not supported easily... a quick look seems it needs "../asmjit" in a
parent dir. this leads me to: https://github.com/asmjit/asmjit which says
"x86/x64" only in the arch support. and that right off the bat would veto this
as something we'd depend on. we'd need at least these architectures supported
for me to begin considering:

armv7,v8
x86,x64
ppc
mips

... pretty much what luajit supports.

i actually had been mulling writing such an "offline" code generator that
generated c (with snippets of asm/asm intrinsics or macros for simd), then did
like above.

if blend2d was more like this... then it'd be worth looking at even if it had a
c++ api.

> -- 
> Vinícius dos Santos Oliveira
> https://vinipsmaker.github.io/
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


-- 
- Codito, ergo sum - "I code, therefore I am" --
Carsten Haitzler - ras...@rasterman.com


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] [EGIT] [core/enlightenment] master 01/01: music-control - install properly with meson build with icon

2017-12-03 Thread Carsten Haitzler
On Sat, 2 Dec 2017 00:10:11 +0100 marcel-hollerb...@t-online.de said:

> Hello,
> 
> so it turned out that this is a ninja bug.
> 
> Ninja has some sort of recompactination if the number of entries in the
> .ninja_log and .ninja_deps files are getting too big, then it will cut
> off a few, write that into a temp file, and rename that temp file later
> to .ninja_log or .ninja_deps, if you ran exactly this time ninja as root
> it will place .ninja_log and .ninja_deps as root owned files in the
> directory instead of maintaining the old gid / uid of the file.

I'm amazed it took us to discover this and you to fix it... ninja isn't exactly
THAT new... :) is it that no one does regular "build as user, install as root"
when using ninja? like this is the regular workflow with make like since...
dinosaurs roamed the earth.

> tldr:
> There is a bugfix:
> https://github.com/ninja-build/ninja/pull/1362
> 
> Greetings,
>Marcel Hollerbach
> 
> On Thu, Nov 23, 2017 at 08:57:20AM +0900, Carsten Haitzler wrote:
> > On Wed, 22 Nov 2017 20:13:48 + Mike Blumenkrantz
> >  said:
> > 
> > > I'm on fedora with meson 0.42.1 and ninja 1.8.2
> > 
> > Can you try doing the "build as user, install as root/sudo" and hit the
> > issue and details exactly what files are owned by root at that point and
> > what file the problem is with and why the permission problem is there? I
> > just can't see the source of the issue in my build trees.
> > 
> > > On Wed, Nov 22, 2017 at 1:08 PM Andrew Williams 
> > > wrote:
> > > 
> > > > Hi,
> > > >
> > > > I'm on Arch and generally try to stay up to date so maybe they have
> > > > fixed it?
> > > > Mike?
> > > >
> > > > On Wed, 22 Nov 2017 at 15:55 Jérémy Zurcher  wrote:
> > > >
> > > > > I can't reproduce that root owner ship issue right now.
> > > > > I made the changes to my scripts on the 2017/08/17
> > > > > at that time on my archlinux boxes ninja was 1.7.2 and meson was
> > > > > 0.41.2 since then ninja has been upgraded to 1.8.2, and meson to
> > > > > 0.42.1 then 0.43.0
> > > > > maybe it has been fixed in one of them fixed now.
> > > > > (but I won't dive into their respective repos to check that ;)
> > > > >
> > > > >
> > > > > On Wednesday 22 November 2017  20:51, Carsten Haitzler wrote :
> > > > > > On Wed, 22 Nov 2017 10:36:36 + Andrew Williams <
> > > > a...@andywilliams.me>
> > > > > said:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I'm glad that it is not affecting you. Jeyzu and I both seem to
> > > > > > > have
> > > > > hit
> > > > > > > this issue (and I guess zmike too as described earlier).
> > > > > > > Some times after a "sudo ninja install" I can no longer "ninja"
> > > > > > > due
> > > > to
> > > > > > > permissions issues with files that have become root owned.
> > > > > > >
> > > > > > > It is unfortunate but it would be good to get a solution that
> > > > > > > works
> > > > > all the
> > > > > > > time for everyone if possible.
> > > > > >
> > > > > > I checked what files were root owned. I currently don't see a reason
> > > > why
> > > > > it
> > > > > > should fail. Someone show me a reason where it does fail (a file
> > > > written
> > > > > to as
> > > > > > root has to be overwritten as a user or it cannot be deleted as a
> > > > user).
> > > > > I
> > > > > > don't see it. perhaps its a bug in meson in an older version? or a
> > > > newer
> > > > > one?
> > > > > >
> > > > > > > Andy
> > > > > > >
> > > > > > > On Wed, 22 Nov 2017 at 10:17 Carsten Haitzler
> > > > > > > 
> > > > > wrote:
> > > > > > >
> > > > > > > > On Wed, 22 Nov 2017 10:33:05 +0100 Jérémy Zurcher
> > > > > > > >  > > > >
> > > > > said:
> > > > > > > >
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > I confirm, I had to add the above in my build script :
> > > > > > > > >
> > > > > > > > > sudo -S chown $USER $BUILD_DIR/.ninja_deps
> > > > > > > > > $BUILD_DIR/.ninja_log
> > > > > > > >
> > > > > > > >  7:14PM ~/C/e/build ⎇ master > ls -al
> > > > > > > > total 4.4M
> > > > > > > > 4.0K drwxr-xr-x  9 raster raster 4.0K Nov 22 15:36 ./
> > > > > > > > 4.0K drwxr-xr-x 10 raster raster 4.0K Nov 22 15:36 ../
> > > > > > > > 1.6M -rw-r--r--  1 raster raster 1.6M Nov 22 15:36 .ninja_deps
> > > > > > > >  64K -rw-r--r--  1 raster raster  61K Nov 22 15:36 .ninja_log
> > > > > > > >
> > > > > > > > written not as root. (make ninja install was as root). ... ?
> > > > > > > >
> > > > > > > > > On Wednesday 22 November 2017  08:18, Andrew Williams wrote :
> > > > > > > > > > Hi,
> > > > > > > > > >
> > > > > > > > > > Compiling as root may be a bad thing but mike is right,
> > > > > > > > > > ninja
> > > > > install
> > > > > > > > hits
> > > > > > > > > > log files and other - some times causing root ownership. I
> > > > > > > > > > have
> > > > > seen it
> > > > > > > > > > occasionally myself and have had to either delete the build
> > > > tree
> > > > >