Re: [E-devel] EFL interfaces, pkg-config and headers

2017-10-24 Thread Carsten Haitzler
On Tue, 24 Oct 2017 13:04:27 -0400 Cedric Bail said: > Hello, > > As we are moving forward with EFL interfaces, it is becoming quite clear that > we should start to have one header and pkg-config for pure EFL interfaces > applications. The problem is that efl.pc and Efl.h are already taken. Goin

Re: [E-devel] EFL interfaces, pkg-config and headers

2017-10-24 Thread marcel-hollerbach
: > > Original Message > > Subject: Re: [E-devel] EFL interfaces, pkg-config and headers > > Local Time: October 24, 2017 10:16 AM > > UTC Time: October 24, 2017 5:16 PM > > From: [email protected] > > To: Enlightenment developer list > >

Re: [E-devel] EFL interfaces, pkg-config and headers

2017-10-24 Thread Cedric Bail
> Original Message > Subject: Re: [E-devel] EFL interfaces, pkg-config and headers > Local Time: October 24, 2017 10:16 AM > UTC Time: October 24, 2017 5:16 PM > From: [email protected] > To: Enlightenment developer list > > Hello, > >

Re: [E-devel] EFL interfaces, pkg-config and headers

2017-10-24 Thread marcel-hollerbach
Hello, isnt the libefl.so and efl.pc taken for src/lib/efl ? which is basiacally 100% beta api and interfaces ? I think we could just add files to that lib and continue using it ... :) Greetings, Marcel Hollerbach On Tue, Oct 24, 2017 at 01:04:27PM -0400, Cedric Bail wrote: > Hello, > > As

[E-devel] EFL interfaces, pkg-config and headers

2017-10-24 Thread Cedric Bail
Hello, As we are moving forward with EFL interfaces, it is becoming quite clear that we should start to have one header and pkg-config for pure EFL interfaces applications. The problem is that efl.pc and Efl.h are already taken. Going with efl-2.pc, would kind of do it, but we don't have an ass