On 21/05/12 12:20, Vincent Torri wrote: > On Mon, May 21, 2012 at 11:11 AM, Tom Hacohen<[email protected]> wrote: >> On 21/05/12 12:07, Vincent Torri wrote: >>> Cflags must add dirs where the exported headers of Eo are located. You >>> have only one such header (Eo.h), so you do not need 2 locations, >>> here. You should revert that commit >> >> If you look closely, > > you want *me* to look closely at the cmake horror ? Funny. > >> you'll see I put my header in ${includedir} that >> is, I added the correct path. The second path, i.e the eo-@VMAJ@ was >> what I previously had there. I kept that because I'll may add stuff >> there at some point and it doesn't really matter. But I can't revert my >> commit as it'll not work and my commit is correct. > > then remove the second header dir and add it later > > But, if you follow the EFL scheme wrt those directories, you should > put them in $includedir/eo-@VMAJ@, and not $includedir.
Yeah, well, all the build related styles will be adjusted to match the ones of the EFL once the build tool settles (i.e we conform with the rest of the EFL). -- Tom. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
