From: Kirk J. <kir...@gm...> - 2013-06-24 19:23:55
|
>> 1. Use the included configure and make files through MSYS. > This should be your preferred option. Glad to hear it, as the other option sounded kind of dumb and seemed to bypass the point of MSYS > configure seems to support an option for specifying the boost location; > what does 'configure --help' say about specifying wxWidgets location? It has a similar option for wxWidgets but it hasn't been working. I'm probably just doing something stupid. Responding to a few points at once here because they're related... > So, where did your build, via Code::Blocks, install wxWidgets? > See: http://www.mingw.org/wiki/IncludePathHOWTO > and: http://www.mingw.org/wiki/LibraryPathHOWTO (although incomplete) > my preference is option #2, as described in the IncludePathHOWTO I did not build wxWidgets through Code::Blocks. I built it from within MSYS like this: $ cd H:/wxWidgets-2.8.12/msys-build $ ../configure --disable-shared --enable-unicode $ make $ make install This seems to have installed wxWidgets into the usual Linux style directories with respect to the MSYS root. When this happened, and after reading and re-reading the HOWTOs, I decided to just try to use the effective MSYS filesystem as my "option #2 (in the parlance of the includePathHOWTO)" file tree. I think I finally understand that now, having put my dependencies in the MSYS file system, I just need to add -l and -L when I run my project's configure to make sure those dependencies are found. By the way, after I ran install make on wxWidgets the following message was printed "The installation of wxWidgets is finished. On certain platforms (e.g. Linux) you'll now have to run ldconfig if you installed a shared library and also modify the LD_LIBRARY_PATH (or equivalent) environment variable." I guess this is a way to not have to explicitly type -l and -L options? > It's been a while since I last used wxWidgets; doesn't it install a > wx-config script, which will tell you what -I and -L paths it expects? There is indeed a wx-configure.in file. Typing config --help in the wxWidgets directory prints an enormous amount of text so long that I can't see most of it. I guess I need to learn how to filter. Thanks for you help. I think I will figure this out now. I'll pipe up if I really can't get it. Also, when I'm all done with this I will very likely have suggestions for the docs and I'd be very happy to contribute personally. -kjoppy |