Hello Thomas!
Congratulations for your success on fixing the compilation
error!!! This are very good news! Now I remember that we had the same
problem some time ago, but in your case unfortunately, the error provided by
Visual Studio is not very descriptive. I've put Yves in CC, that is leading
the development of CSnake and he can add this feature to the CSnake roadmap.
Please contact the mailing list again if we can provide you
more support.
Best regards,
Xavi
From: Thomas Wolf [mailto:[email protected]]
Sent: martes, 08 de mayo de 2012 11:23
To: Xavier Planes
Cc: [email protected]
Subject: Re: [Gimias-developers] Visual Studio 2010 Build for 1.4 tags and
1.5 trunk error on plugins (solved)
Hello Xavier!
I'm sorry but I'm not an expert on Visual Studio hotfixes. I think
the best way to receive support on this issue is to ask the question to the
Visual Studio forums:
No worries. I just thought as you had a similar problem, you might have
known the exact issue and hotfix number. I might have possibly ruled out one
cause of error faster.
Regarding the question about precompiled headers (PCH), there's not
an option to disable all PCHs in CSnake. However, you can disable these
independently for each component.
I did disable everything for the plugins, but it did not help.
But:
The solution was much simpler. After following a discussion about regarding
0xC0000417 ( invalid parameter to the c runtime) in a larger open source
project and their fixes for it(using char* pointers instead of char[] arrays
of defined length, circumventing the security checks for bounded arrays), i
slowly realized that my problem also could be related to a string length
issue. But not for the to-be-created program, but for the Microsoft compiler
itself.
And indeed, looking up the specs delivers a string limit of 8191 characters
for the command line (Command prompt (Cmd. exe) command-line string
limitation <http://support.microsoft.com/kb/830473> ). As CMake sadly uses
absolute paths in everything, this becomes an issue quickly.
So the simple answer to my utmost dull problem is: The command line for the
compiler was to long. I had my project in something like
d:/scratch/thomas/projects/current/gimias which caused apparently the
overflow for cl.exe at the stage of the precompiled headers target. One can
blame the guys in Redmond for just letting their compiler crash instead of
giving a precise error message in that case.
Good thing is, after 2 weeks of installing every hotfix possible my Visual
Studio is up to date :P
One thing i noted then, as i did a lot with MITK before, is that the current
makefiles of MITK check the build path length for that reason and won`t
generate the make files if too long. Maybe its worth looking into it and
integrate that function, it might safe other people some trouble in the
future.
Kind regards,
Thomas
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Gimias-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gimias-developers
