configure vs cmake?
Joost Kraaijeveld <[email protected]>
| Newsgroups | gmane.comp.lib.wxwindows.general |
|---|---|
| Message-ID | <[email protected]> |
Hi, I am trying get the "configure" and "cmake" build procedure/command to get the same result in terms of the libraries: build the same libraries with he same size (assuming that they are the same than) and linking with the same libraries (have the same dependencies). I know that the (installed) include files differ (see https://github.com/wxWidgets/wxWidgets/issues/22714). Currently my "configure" command line is "./configure --with-gtk=3 -- enable-debug --with-cxx=17 " and "cmake" command line is "cmake .. - DCMAKE_CXX_STANDARD=17". Both command lines fessult in a successful compilation but different size of libraries with different dependencies. My understanding is that debug is default which means that "--enable- debug" or giving no argument will result in debug libraries. However the size of the libraries differ. E.g. libwx_baseu-3.2.so.0.2.1 with cmake is 21 MB, with configure is 18.3 MB. The library dependencies also differ. E.g. using "cmake" has ldlibs_xml="-lwx_baseu-3.2 /usr/lib/x86_64-linux-gnu/libexpat.so" as dependency while using "configure" has ldlibs_xml=" -lexpat" according to wx-config. ldlibs_base, ldlibs_html, and ldlibs_stc also differ in the libraries. All dependencies differ in terms of the path to the libraries: some have an absolute path, some don't. Shouldn't this be all the same? Is it possible to make these all the same? Is "configure" better than "cmake", i.e. result in less problems when using the compiled version of wxWidgets? -- Groeten, Joost Kraaijeveld -- Please read https://www.wxwidgets.org/support/mlhowto.htm before posting. --- You received this message because you are subscribed to the Google Groups "wx-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/wx-users/28caf01b45d0e6916ae306a5b06ae2e5cf3c4db9.camel%40Askesis.nl.
signature.asc
(application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRhTG7cle0tRusTnEXRUkpSQdxfvwUCZSwq7wAKCRDRUkpSQdxf v/EaAJ4mViaawpuKg9vVWxCKAU3RG7+X3gCeNdpxK6/34DSOX866DiYCPOsnX/0= =c7Q3 -----END PGP SIGNATURE-----