-----BEGIN PGP SIGNED MESSAGE----- Support PKG_CONFIG in configure for UnicodePlugin : PKG_CONFIG path to pkg-config utility Note that I believe that Ian Piumarta's "cmake" system for squeak-4 also The reason why I made this change, is for compiling on Solaris 11.4. You can see in the "mvm" script that I set PKG_CONFIG_PATH for the 64bit: On Solaris 11.4 32bit there is: pkg-config --cflags glib-2.0-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include and on Solaris 11.4 64bit there is: PKG_CONFIG_PATH=/usr/lib/64/pkgconfig pkg-config --cflags glib-2.0-I/usr/include/glib-2.0 -I/usr/lib/amd64/glib-2.0/include Note the '64' or 'amd64' subdirectories. Finally a remark: I modified
because I don't see how to define the UNICODE_PLUGIN_CFLAGS in the plugin, Because of the 'mkmf' script, this will thus modify all Unix Makefiles ... If somebody has a better idea, let's hear it ! I understand from Eliot Miranda that abandoning 'configure' is an option. But that still has the issue of multiple locations on various Unix flavors, David Stes -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJfY5HNAAoJEAwpOKXMq1MaLpEIAL0qgm0zmtJs3kqV9GHli96I You can view, comment on, or merge this pull request online at:https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/520 Commit Summary
File Changes
Patch Links:
— |
I'd rather not use pkg-config just for parts of the system. — |
In reply to this post by David T Lewis
-----BEGIN PGP SIGNED MESSAGE----- OK, it's true that this may be a risky change to 'configure'. I don't have a problem with closing/withdrawing this pull request ... I can work-around the issue with some alternatives (like replacing the hardcoded paths by other paths), so I don't really mind. Note that the squeak-4 package ("cmake") uses pkg-config however. David Stes -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJfY5d7AAoJEAwpOKXMq1MaisUH/Rxk9mUC+8VIYO1Zrqy7b4tn — |
In reply to this post by David T Lewis
Yeah, I'm painfully aware :) — |
In reply to this post by David T Lewis
I'm closing this pull request. For me this "configure" change works. It's simply: PKG_CHECK_MODULES(UNICODE_PLUGIN,[glib-2.0 pangocairo],,AC_PLUGIN_DISABLE) the "PKG_CHECK_MODULES" macro checks whether glib-2.0 and pangocairo are installed VIA the pkg-config tool. My understanding is that GTK uses pkg-config exactly for this purpose. But it's true that any change to 'configure' has some risk associated to it (it may break things on some other platforms). Because I have a workaround, I'm closing the request. I'll just open a request to document in the README that we have discussed the issue, so that somebody who stumbles upon the same issue in the future, knows about it. It's seems likely that this issue will come up again - on different platforms. — |
In reply to this post by David T Lewis
I'm closing this pull request. For me this "configure" change works. It's simply: PKG_CHECK_MODULES(UNICODE_PLUGIN,[glib-2.0 pangocairo],,AC_PLUGIN_DISABLE) the "PKG_CHECK_MODULES" macro checks whether glib-2.0 and pangocairo are installed VIA the pkg-config tool. My understanding is that GTK uses pkg-config exactly for this purpose. But it's true that any change to 'configure' has some risk associated to it (it may break things on some other platforms). Because I have a workaround, I'm closing the request. I'll just open a request to document in the README that we have discussed the issue, so that somebody who stumbles upon the same issue in the future, knows about it. It's seems likely that this issue will come up again - on different platforms. — |
In reply to this post by David T Lewis
I'm closing this pull request. For me this "configure" change works. It's simply: PKG_CHECK_MODULES(UNICODE_PLUGIN,[glib-2.0 pangocairo],,AC_PLUGIN_DISABLE) the "PKG_CHECK_MODULES" macro checks whether glib-2.0 and pangocairo are installed VIA the pkg-config tool. My understanding is that GTK uses pkg-config exactly for this purpose. But it's true that any change to 'configure' has some risk associated to it (it may break things on some other platforms). Because I have a workaround, I'm closing the request. I'll just open a request to document in the README that we have discussed the issue, so that somebody who stumbles upon the same issue in the future, knows about it. It's seems likely that this issue will come up again - on different platforms. — |
In reply to this post by David T Lewis
I'm closing this pull request. For me this "configure" change works. It's simply: PKG_CHECK_MODULES(UNICODE_PLUGIN,[glib-2.0 pangocairo],,AC_PLUGIN_DISABLE) the "PKG_CHECK_MODULES" macro checks whether glib-2.0 and pangocairo are installed VIA the pkg-config tool. My understanding is that GTK uses pkg-config exactly for this purpose. But it's true that any change to 'configure' has some risk associated to it (it may break things on some other platforms). Because I have a workaround, I'm closing the request. I'll just open a request to document in the README that we have discussed the issue, so that somebody who stumbles upon the same issue in the future, knows about it. It's seems likely that this issue will come up again - on different platforms. — |
In reply to this post by David T Lewis
I'm closing this pull request. For me this "configure" change works. It's simply: PKG_CHECK_MODULES(UNICODE_PLUGIN,[glib-2.0 pangocairo],,AC_PLUGIN_DISABLE) the "PKG_CHECK_MODULES" macro checks whether glib-2.0 and pangocairo are installed VIA the pkg-config tool. My understanding is that GTK uses pkg-config exactly for this purpose. But it's true that any change to 'configure' has some risk associated to it (it may break things on some other platforms). Because I have a workaround, I'm closing the request. I'll just open a request to document in the README that we have discussed the issue, so that somebody who stumbles upon the same issue in the future, knows about it. It's seems likely that this issue will come up again - on different platforms. — |
In reply to this post by David T Lewis
Sorry for multiple messages, when I click "Close with comment" Github does not seems to close my pull request. It's ok to close it anyway, sorry for the multiple messages. — |
In reply to this post by David T Lewis
No worries. In any case, thanks for your efforts! — |
In reply to this post by David T Lewis
Closed #520. — |
Free forum by Nabble | Edit this page |