Sysprogs forums › Forums › VisualGDB › Error trying to build Cmake linux project with latest VisualGDB and a VS
- This topic has 3 replies, 2 voices, and was last updated 1 week ago by support.
-
AuthorPosts
-
November 20, 2024 at 07:03 #36145drjonemParticipant
Hi,
I’ve had an issue with my VisualGDB linux projects for a while where trying to build with F7 or rightclicking on the topmost node under Solution (first line with CD5X in the attached image) and selecting Build does not start the build – the message is
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Build completed at 14:52 and took 00.069 seconds ==========no matter what files have changed.
I used to be able to right click on the node with the command prompt icon (3rd row with CD5X in attached image) and select build which would then build correctly so it has not bothered me too much.
However, since upgrading to VisualGDB 6.0R4 and VS 17.12.0, if I try to build in this way, I get the following exception:
VisualGDB version: 6.0.104.5220
—————— System.ArrayTypeMismatchException ——————
System.ArrayTypeMismatchException: Attempted to access an element as a type incompatible with the array.
at System.ThrowHelper.ThrowArrayTypeMismatchException()
at Microsoft.VisualStudio.CommonIDE.Solutions.BuildManager.SolutionBuildManager.HrUpdateProjects(vsBuildScope buildScope, SLNUPDACTION dwUpdateActions, UInt32 cProjs, IVsHierarchy[] rgpHierProjs, __VSDBGLAUNCHFLAGS grfLaunch, Boolean fSuppressUI, IVsSlnConfiguration pSlnCfg, Boolean alwaysRespectSlnCfgCheckBoxes)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at w4.q2(Object b, iu1 a)
at vg1.a.c_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2(sb1 b, Object a)
at dh3.b.Exec(Guid& d, UInt32 a, UInt32 b, IntPtr e, IntPtr c)
trace=[System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal:-1, w4.q2:116, vg1+a.c_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2_2:332, dh3+b.Exec:438]Now, the only way I can get a build to run is to right click on the top node and select Rebuild. This works succesfully but is not a long term solution as this project takes around 3.5 minutes to do a Rebuild.
Solutions to both problems would be appreciated.
Note that I have a number of non-linux projects – for these the F7 build has always worked though they exhibit the same issue now if trying to build by rightclicking on the command prompt icon
Thanks.
Attachments:
You must be logged in to view attached files.November 24, 2024 at 20:32 #36154supportKeymasterHi,
No problem, please try this build: VisualGDB-6.0.104.5238.msi
November 26, 2024 at 03:27 #36158drjonemParticipantHi,
That resolves the exception so I can do incremetal builds again, many thanks for the prompt support.
However, the issue with an F7 build still remains. Is there any solution to that?
Thanks,
Jon
November 26, 2024 at 19:32 #36162supportKeymasterSorry, we couldn’t reproduce that one. Most likely, it is caused by something else. In order to narrow it down please try checking the following:
- Does it happen with a newly created project of the same type?
- If yes, does it happen with remotely built CMake projects, locally built CMake projects or both?
- Does it also happen with MSBuild-based projects of the same layout (local/remote)?
-
AuthorPosts
- You must be logged in to reply to this topic.