Hey, On 28/05/2020 15:17, Marcel Hollerbach wrote: > > Yeah, something like that was planned in the future, or building small > stubs without code that are just dragging in efl-one.so This way we do > not have to worry about platforms with problems about symlinks etc. > The problem is that the parts that are outside efl-one.so are still > linking to the smaller .so's and not to efl-one.so as that is a little > bit harder to realize, > and I first want to ensure that we *really* have a working efl-one.so > which totally works before investing more time into that.
That actually makes so much more sense than my suggestion. :facepalm: > > The plan for getting everything on efl-one.so looks a little different > to me: > - Maybe move ecore_wayland and ecore_drm to a deprecated folder, that is > not handled as normal efl subproject anymore > - Move elua to lua bindings and or build it from there > - Find out what to do about ecore_avahi > > After that our normal code and build structure is in a state where > everything natively links to efl-one.so simply by calling subdir(...) in > another directory. We then can also automatically generate the > "declare_dependency" and "library" calls and shrink down the lib > meson.build files even more, which should simplify everything overall > quite a bit. > > But thats for the future, first lets find out how this works out :) Sure, just wanted to share my thoughts in case it would be too late later on, but it looks like you are already on it. :) > efl.pc is sadly not beta anymore, shipped, and used. > > I basically just really want to ensure that everyone understands that > this is not yet another subproject within efl, but the overall library > including a lot but not everything. And in the end, its just a name ... :) > Makes sense. :) Anyhow, again, great job! -- Tom _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
