| 1 |
There is one issue that keeps dev-lang/v8 in hard mask and prevents its |
| 2 |
broader usage (I think www-client/chromium could start using it). I hope |
| 3 |
you'll help me find the best solution. |
| 4 |
|
| 5 |
Some context first. Upstream does not promise any binary compatibility |
| 6 |
between releases, so each version has a different SONAME, if any. |
| 7 |
|
| 8 |
Currently dev-lang/v8 does not use SONAME (I think that's the default), |
| 9 |
because I'm not sure what's the best way to handle it. |
| 10 |
|
| 11 |
When present, the SONAME will look like libv8-1.2.3.so, and the |
| 12 |
resulting shared library will be named the same way, i.e. libv8-1.2.3.so. |
| 13 |
|
| 14 |
Without SONAME, it's just libv8.so, so when linking it's sufficient to |
| 15 |
pass -lv8 to the linker. |
| 16 |
|
| 17 |
With the SONAME-d library, I guess I'd need to pass -lv8-1.2.3. I was |
| 18 |
thinking about making a symlink libv8.so -> libv8-1.2.3.so, but I'm not |
| 19 |
sure if that's the right thing to do. |
| 20 |
|
| 21 |
What do you think? Do you need some more details? |
Archives