| 1 |
On 12/23/20 12:13 PM, Jonathan Callen wrote: |
| 2 |
> |
| 3 |
> One way this could be done without breaking things might be to create a |
| 4 |
> subdirectory of /usr/$(get_libdir) for each version of Lua and creating |
| 5 |
> a liblua.a and/or liblua.so symlink in that directory pointing to the |
| 6 |
> liblua${VERSION}.* file in /usr/$(get_libdir). Then you could simply |
| 7 |
> point those build systems at that directory and they would still use the |
| 8 |
> correct version. As a hack in an ebuild, you probably could just create |
| 9 |
> such a setup in (subdirectories of) ${T}, pointing liblua.a, liblua.so, |
| 10 |
> and lua.pc at the appropriately-versioned files. |
| 11 |
|
| 12 |
All of these packages are masked, so breakage isn't an issue. |
| 13 |
|
| 14 |
And since these hacks are needed in every package that will link against |
| 15 |
liblua, doesn't it sound like something the eclass should be doing? Even |
| 16 |
the CMake packages would benefit, no longer having to pass in |
| 17 |
-DLUA_INCLUDE_DIR and -DLUA_LIBRARY by hand. |
Archives