[Cmake] Trouble with : Include External MsProject
Bill Hoffman
bill . hoffman at kitware . com
Tue, 15 Jul 2003 08:49:29 -0400
I guess it should not crash, but no, it was never implemented for VS 7.
I think it was someone at Oxford that did the original command for VS 6, if
you are out there, are you interested in implementing it for VS 7? If not,
I think we may have to deprecate the command due to lack of support.
-Bill
At 08:18 AM 7/15/2003, John Biddiscombe wrote:
>Hi all,
>
>I'm using
>INCLUDE_EXTERNAL_MSPROJECT( "${PROJECTNAME}.vcproj" "${Mirada_SOURCE_DIR}/${PROJECTNAME}")
>inside a macro and it bombs out with an access violation. Looking at the code I see that the command for include external msproject creates a utility command which in turn sets
>GetPostBuildCommands() to a vector of stuff.
>
>in the vc71 (dot net 2003 generator) the code does
>
>cmCustomCommand cc = l->second.GetPreLinkCommands()[0];
>
>which looks bad and is causing the trouble. I changed this to
>
>cmCustomCommand cc = l->second.GetPostBuildCommands()[0];
>
>and the AV went away, but instead I get
>"CMake error : WriteExternal project not supported for visual studio 7"
>
>my question is : Am I doing something wrong or is it just not yet implemented for dot net 2003?
>
>thanks
>
>JB
>PS. Used cvs version from a few weeks ago initially, but when it crashed I did a cvs update yesterday and it still crashes.
>
>_______________________________________________
>Cmake mailing list
>Cmake at cmake . org
>http://www . cmake . org/mailman/listinfo/cmake