Sorry, now I see that jambase doesn't support VC++11 yet. I added a dirty workaround for the MSVC version detection and everything got built without further errors. This was actually easier and faster than using MinGW. 2013/8/4 János, Tóth F. <janos666@xxxxxxxxxx> > I tried to compile the current developer code with VS2012 (minimal > install). > I ran makall from the VS2012 x86 Native Tools Commad Prompt (lauched as > Administrator) after I placed the precompiled jam.exe in the freshly > uncompressed ArgyllCMS source code folder. > > As it was already noted, I had to remove the /DEBUGTYPE:BOTH argument from > the jambase file. After that I received this error: > > LINK : fatal error LNK1318:Cc_ numlib\LUtest.obj > Unexpected PDB error; ACCESS_DENIED (15) 'D:\Argyll_V1.6.0_beta\NONE' > LUtest.c > > As I understand it's an arithmetic test, but I don't get one of the > predefined error messages, just this unexpected PDB error. > Any ideas? > > > 2013/3/27 Graeme Gill <graeme@xxxxxxxxxxxxx> > >> Fridger Schrempp wrote: >> >> > http://www.argyllcms.com/ajam-2.5.2-1.3.3.zip, gives a *404 Not Found* >> error at least since >> > yesterday evening. Is this a bug or on purpose? >> >> My hosting company seems to delete files from my website at random >> intervals. >> I'm waiting for an explanation from them before uploading things again. >> >> > Anyway, Win32 compilation of ajam and Argyll sources in my proven VC++ >> 2010 SP1 Express dev >> > environment was a simple task, taking not more than a few minutes. >> >> Good to hear. >> >> > Just three small points: >> > >> > 1) Given a proper VC++ 2010 installation there is a dedicated Visual >> Studio 2010 command prompt >> > that has everything needed for the compilation already in the %PATH%. >> Using it makes the things >> > very straightforward. >> > >> > 2) When compiling ajam I had to replace libc.lib by libcmt.lib in >> builds/win32-visualc.mk, since >> > libc.lib gives the familiar MSVC Win error... >> >> Jam uses threads, so I guess that's not much of a surprise, although the >> Makefile should >> take care of it... >> >> > 3) In Jambase of Argyll_V1.5.1 the line LINKDEBUGFLAG ?= >> /DEBUGTYPE:BOTH /DEBUG ... ; >> >> It's not meant to use that option unless its' VC++6, but that's my fault >> - I'm >> not detecting the compiler properly. My setup scripts set $COMPILER and >> Jambase >> uses that. I'm not quite sure what environment variable to depend on >> though. >> I could try looking for "VC++NN" in the install path MSVCNT or >> VCINSTALLDIR, >> but I'm not sure if that is something that is fixed. >> >> Graeme Gill. >> >> >