On 2013-12-6 16:42, niXman wrote: > Hi guys! > > I'm pleased to announce the new builds of MinGW-W64 based on the > GCC-4.8.2 at rev.1. > Changes from rev.0 is: > - Binutils updated to 2.24 > - MinGW-w64 v3 rev.6391 > - Backport MinGW-w64 runtime commits from trunk to stable version: > 6303: Fixed conflicts with xmmintrin.h. > 6332: Install libvfw32.a once again > 6385: Update shlwapi.def for Win7 32-bit > 6386: Update shlwapi.def for Win7 64-bit > 6390: Update shell32.def from Win7 > - Update make to latest from git. > - Fix installing gcc libraries for Python > - Relocate c++ headers to <target>/include/c++ > > Links:
Hi, thanks for your work. I just download this one: i686-4.8.2-release-posix-dwarf-rt_v3-rev1.7z I would like to use this GCC toolchain to build GDB with Python support. I was using the official Python Windows installer, and build GDB against the official Python dll, since the official Python was build with MSVC, and link against msvcr90.dll. The result GDB will have both link to msvcrt.dll and msvcr90.dll(indirectly through python27.dll), this may cause some potential problems since they have different c-run-time libraries. Now, I would try to link against the Python import library shipped with the MinGW-Build i686-4.8.2-release-posix-dwarf-rt_v3-rev1.7z. Question 1: I found that there are two .a files: libpython2.7.a and libpython2.7.dll.a, both under: \i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\opt\lib\python2.7\config folder. So, which should I use? Question 2: I can't find the python header files. Question 3: When build GDB against official python installation, I just add some option to GDB toplevel configure like: --with-python=/python/python Where under MSYS, I have a mount that E:\code\python27 /python (More details on how to build GDB can be found my own wiki page [1]) Note that E:\code\python27 is the folder I install the official python 2.7.x, so if I would like to link to the shipped python, what is the correct configure option? Question 4: What does https://github.com/niXman/mingw-builds/blob/master/sources/gdb-wrapper/gdb-wrapper.c used for? I vaguely remember you have some script code to rename the GDB.exe to some other name, and renamed gdb-wrapper.exe to GDB.exe. It does some PYTHONPATH related changes, but refer to Ruben's post here [2], it is quite safe to put the python27.dll along side the gdb.exe and put all the python script files under bin folder too. Thanks. Yuanhui Zhang [1] https://sourceforge.net/p/gdbmingw/wiki/Build%20GDB%20under%20MSYS/ [2] https://groups.google.com/d/msg/comp.lang.python/-DE5LmBbAC0/xv6q059ez-oJ ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
