Could anyone tell me the details of their MinGW build setup? For example, which versions of pthreads, etc. that you are using. I am both starting to port the Pd.app build system to Windows, while also documenting how to set up your machine to compile Pd, etc. using MinGW.
There was a very basic page here which I have started to flush out: http://puredata.org/docs/developer/mingw
.hc
________________________________________________________________________ ____
Using ReBirth is like trying to play an 808 with a long stick. -David Zicarelli
Hallo!
Could anyone tell me the details of their MinGW build setup? For example, which versions of pthreads, etc. that you are using. I am both
I just managed to do the right linking with pthread - but for an external and not for main pd ...
for pthread you simply have to link against pthreadGC.dll (with MSVC you link against pthreadVC.dll - which means Visual C - so if you don't have pthreadGC.dll you also have to install this dll, because it's not included in the pd bin folder ... pthead.h is included in the src directory of the pd windows installation ...)
BTW: could it be a problem, if you compile pd with MSVC (= link against pthreadVC.dll) and an threaded external with MinGW (link against pthreadGC.dll) ? I only tried to also link the external in MinGW against pthreadVC.dll, but got a crash - so I think it should be okay ... ?
LG Georg
On Nov 15, 2005, at 10:05 AM, Georg Holzmann wrote:
Hallo!
Could anyone tell me the details of their MinGW build setup? For example, which versions of pthreads, etc. that you are using. I am both
I just managed to do the right linking with pthread - but for an external and not for main pd ...
for pthread you simply have to link against pthreadGC.dll (with MSVC you link against pthreadVC.dll - which means Visual C - so if you don't have pthreadGC.dll you also have to install this dll, because it's not included in the pd bin folder ... pthead.h is included in the src directory of the pd windows installation ...)
Yeah, I compiled the latest version, 2.7.0, and apparently there is a change in the DLL format so its not binary compatible. Therefore, I got pthreadGC2.dll. Anyone used this new version with Pd? Shall I just stick with the old version?
BTW: could it be a problem, if you compile pd with MSVC (= link against pthreadVC.dll) and an threaded external with MinGW (link against pthreadGC.dll) ? I only tried to also link the external in MinGW against pthreadVC.dll, but got a crash - so I think it should be okay ... ?
This won't be a problem. The Windows installer build system will be all based on MinGW, compiled at one time, therefore, they'll all use the same DLL.
.hc
________________________________________________________________________ ____
As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously.
- Benjamin Franklin
Hallo!
Yeah, I compiled the latest version, 2.7.0, and apparently there is a change in the DLL format so its not binary compatible. Therefore, I got pthreadGC2.dll. Anyone used this new version with Pd? Shall I just stick with the old version?
hm ... I used pthreadGC.dll - what is the difference to pthreadGC2.dll ?
This won't be a problem. The Windows installer build system will be all based on MinGW, compiled at one time, therefore, they'll all use the same DLL.
okay ... great !
Just an other MinGW question: I have really problems with read() from <io.h> in windows when used from a child thread (always get -1 as return value) ... has anyone an idea what this could be ?
LG Georg
On Nov 15, 2005, at 11:33 AM, Georg Holzmann wrote:
Hallo!
Yeah, I compiled the latest version, 2.7.0, and apparently there is a change in the DLL format so its not binary compatible. Therefore, I got pthreadGC2.dll. Anyone used this new version with Pd? Shall I just stick with the old version?
hm ... I used pthreadGC.dll - what is the difference to pthreadGC2.dll ?
Which version of pthreads are you using?
.hc
This won't be a problem. The Windows installer build system will be all based on MinGW, compiled at one time, therefore, they'll all use the same DLL.
okay ... great !
Just an other MinGW question: I have really problems with read() from <io.h> in windows when used from a child thread (always get -1 as return value) ... has anyone an idea what this could be ?
LG Georg
________________________________________________________________________ ____
¡El pueblo unido jamás será vencido!