(Multi-) Threading

[revelator]

for msvc static pthread build http://sourceforge.net/projects/cbadvan ... z/download

ill upload a static build for gcc also soon.

SDL2 is getting to a point where it beats the old SDL been toying a bit with it and looks promissing.
More info is allways appreciated bring it on !.

[Baker]

[revelator]

np m8 and here are static builds for msvc intel and gcc.
http://sourceforge.net/projects/cbadvan ... z/download

remember too set the PTW32_STATIC_LIB in preprocessor settings for msvc/intel. for gcc yank it in CFLAGS like this export CFLAGS=" -DPTW32_STATIC_LIB" or if using codeblocks set it in build options/compiler settings/#defines.

[Baker]

And get to have my CodeBlocks build have it to

[Baker]

[revelator]

might be because of different runtime dependencies msvc6 vs msvc 2010 runtime. Ill see if i can cook up a library linked to the static msvc runtime.

[revelator]

btw the __imp_ before the typenames just means its trying to link to the dll version hence the define.

[revelator]

http://sourceforge.net/projects/cbadvan ... z/download

yep pthread linked to the dll runtimes so i fixed that part, they are now linked to the static msvc runtime instead.

above package only includes the msvc libraries, just replace the old ones with these and you should be good to go

i also included the debug library in case you need to go bughunting

[Baker]

[revelator]

agh aye those exports are from the newer msvcr runtime.

especially the security check cookie crap is for checking buffer overflows and was not present in the earlier msvc runtime.

actually you might have luck just renaming the libpthreadGC2.a file to pthreadVC2.lib and link with that in msvc6 since mingw by default uses the old msvc runtime.

dont have the old vc6 compiler anymore but if you feel upto compiling it yourself i can upload the source ?.

just cd into the pthread directory while in the msvc shell and do nmake clean VC-static to build it.

msvc6 does not install a link to its commandline utilities by default so you have to make that yourself, its located in the bin directory of your msvc6 compiler and is named VCVARS32.BAT.
rightclick it and select to make a shortcut, now edit its properties by rightclicking the shortcut and put this before it %comspec% /k so that it looks something like this.
%comspec% /k "C:\Program Files\compiler dir\VC\bin\VCVARS32.BAT" in the destination box. viola you now have access to the commandline toolset.

If this is to much for you to take in ill see if i can modify the msvc6 project file so that it gets the right flags for creating a library, normally its setup to create a dll by default.

ok heres the source code http://sourceforge.net/projects/cbadvan ... z/download
try and see if the msvc 6 dsw project works, i changed the output type to output a static library instead of a dll and it statically links to the msvc runtime.

[Baker]

I appreciate the effort, I'm perfectly happy with having a static lib for vs 2008 and also one for mingw.

I'll probably take a stab at compiling using the link tomorrow or Monday, but I'm thrilled I have a static lib I can use for release builds.

[revelator]

allways nice to have a compiler guy handy hehe.

well i was fortunate i still had a copy of msvc6 in a virtual machine backup so i tried the build myself, but and heres the nasty stuff,
msvc 6 is no longer compatible with the pthread source code you will literally get 1000's of errors if you try agh.
mostly seems related to changes in typenames that the old compiler does not have (__int64 for instance) but there are many more.

I can understand the need for a simple IDE and i would like to look into if its possible to use the old msvc6 ide with the newer tools
atm the simplest ide i can give you if you want is sadly gcc based but pretty much as clean as the old msvc 6 IDE.
but its very basic so if you need special defines you would have to do most of them by hand.

[Baker]

[Barnes]

If I remember correctly, intel compiler for Linux - is free.
It can automatically generate parallel code (open mp)

[revelator]

indeed well 2010 is still pretty much like the 2008 version so maybe an option ? also the IDE is not to nasty to handle yet and the compiler still supports atleast XP builds.
2012 also supports XP but the IDE can be a bit overwhelming. 2013 does not support XP at all unless you have a former compiler like 2010 handy in which case you can select that in the compiler options.

Aye the string safe printf runtimes will definatly make things screewy also the 64 bit int timer functions and the changes to C++ namespaces so loads of incompatibilities.

Ah well if you can live with the dll version on msvc6 it shouldnt matter to much can allways use 2008 for release builds with the static library.