4 ms·
The LGPL parts here are dynamically linked, which is exactly what the LGPL was supposed to let you do.
by Jasper_ 6y ago
The LGPL parts here are dynamically linked, which is exactly what the LGPL was supposed to let you do.
- jcelerier 6y agothey definitely aren't. no libchromiumcontent.so to be seen anywhere. $ ls /opt/visual-studio-code/**/*.so /opt/visual-studio-code/libEGL.so /opt/visual-studio-code/libffmpeg.so /opt/visual-studio-code/libGLESv2.so /opt/visual-studio-code/swiftshader/libEGL.so /opt/visual-studio-code/swiftshader/libGLESv2.so /opt/visual-studio-code/swiftshader/libvk_swiftshader.so And running `strings` on the `code` binary obviously prints the name of classes covered by the LGPL.