#1616 Use a saner way of declaring exported libraries in Dune modules
|Reported by||Steffen Müthing (firstname.lastname@example.org)|
|Reported at||Apr 15, 2015 14:19|
|Version||Git (pre2.4) [cmake]|
|Operating System||Unspecified / All|
|Last edited by||Steffen Müthing (email@example.com)|
|Last edited at||Apr 15, 2015 14:20|
After digging around the build system for some time, it looks to me like a module (e.g. dune-common) declares the fact that it exports the library libdunecommon by adding "-ldunecommon" to dune-common.pc.in. That isn't exactly intuitive (or really documented... ;-) ).
After 2.4 (and with autotools out of the way), we should handle this in a more explicit way. This bug is mostly a reminder for discussing this new way. Maybe by handling it in dune_add_library (and adding a flag to that macro to be able to not auto-export problematic libraries like Alberta)?