SCons and Conan: an issue for when GitHub issues are ready
Russel Winder <[email protected]>
| Newsgroups | gmane.comp.programming.tools.scons.devel |
|---|---|
| Message-ID | <[email protected]> |
JFrog seem to be putting a lot of support into Conan as a way of creating for C and C++ the equivalent of Cargo for Rust – integrated build and dependency management. They are emphasizing integration with CMake, which works for anyone using CLion as an IDE or CMake directly, but doesn't for anyone using Meson or SCons. Given Conan is a Python-based system, it ought to be reasonable, though not a small project, to integrate SCons and Conan. (An awful lot easier that trying to integrate SCons and Dub for D builds, though.) With C++2a likely to finally bring modules to C++, not to mention metaclasses, integrating SCons and Conan is likely to be a Good Thing™. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder _______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEETwDs1X+Beyaiaer41L3V0s7Np7gFAlnEn7YACgkQ1L3V0s7N p7iNgQ//XnZRS1INvEPoFVWDcKV88GZcpi9psnSu6i9m/t2PQ0rdwH+9Oshk2tGx d589hsuOFBFHT1XReMSrkrT/sqQBhIewZIMiJK8touc1imkdqaxlUoZvIfNQQ2Nw KP40Eay8BNY2F8Nf64yA74ezDaaD1PpHkoiRfuvBGUJpLaNs969CCOhz4UQeZbaY 7oeEltmkUE1yq6TTHLJcuEd9RkTkpeYB6RRH5uqhi46lPQ3gUK9XESuZX8C3IXBE 09hrx2KG1jk2O36q2l3tslHE3HE1og3I5wG6d3ip+Zi15x+u4pZqCjEHnVf7p69h bZUDrs9HnzXLiPFzdJWhfostUI0irFJxYZ3Ph+k6BmupeCVuVf/mCqxaLKEGXb+9 Qdt4XZ2oGTmZ04ZvPEi0h0ElFzhhCbkWX2xXTEpV2UeYi28AC2qM8SYUwxgCK1IA f0qPpxJ2Nk5O3ZZe2L+meyPvOpj1KgnxUA+UiWlX/S2nlvKd4uPLSrB3Y/RGfzmO mzOKYmDAg+QCSV5/vqrCkji1OhkjAcvjdTqgMVcfqMBSsV6b3ml7gPgLX54kuwC9 OnslxQU7uKccWPdow4woTSMpQOf4wJjADXzxKSxXf6g8pz4592b36tzu8t2xSYih Gf2YRs1hZG0szbMoANsI8VlrznK1dmIcqah+WkRfGBgK6rCayb0= =5XG1 -----END PGP SIGNATURE-----