- This topic has 6 replies, 2 voices, and was last updated 10 years, 1 month ago by
.
-
Posts
-
Hi,
I’ve noticed a pronounced delay after clicking build before VisualGDB calls make.exe. On my laptop this is around 3 or 4 seconds..
Is it possible to optimise/reduce this? It’s often as long as it takes to actually build the project.Thanks,
solder_pen1> Build started: Project: WindowsProject1, Configuration: Release Win32— Big pause here —-
1> VisualGDB: Run "cmd.exe /c "C:devgcc_distsmingwmingw32binmingw32-make.exe -r" CONFIG=Release" in directory "C:devsourcesTestingDeleteWindowsProject1WindowsProject1" on local computer
1> C:/dev/gcc_dists/mingw/mingw32/bin/g++.exe -ggdb -ffunction-sections -O3 -std=gnu++1y -I"C:/dev/libs/boost_1_56_0" -I../../../../BusyBeaver_Cpp/BusyBeaver_Cpp -DNDEBUG -DRELEASE -c WindowsProject1.cpp -o Release/WindowsProject1.o -MD -MF Release/WindowsProject1.dep
1> C:/dev/gcc_dists/mingw/mingw32/bin/g++.exe -o Release/WindowsProject1.exe -Wl,-gc-sections -Wl,--start-group Release/pch.o Release/WindowsProject1.o -Wl,--end-group
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
Build Summary 00:08.205 - Success - Release Win32 - WindowsProject1WindowsProject1.vcxproj
Total build time: 00:09.991
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped, Completed at 19/09/2014 16:55:08 ==========Hi,
Does it also happen when you launch VisualGDB build from command line? Does your project have lots of source files? Is Visual Studio window responsive during the delay?
Hi,
It has exactly the same delay when launched from the command line. Visual Studio is fully responsive during the delay.
As a simple example, when I make a small change and compile the initial “Hello, World” code that is in a new VisualGDB MinGW project, the delay is longer than the actual full compile.
#include
using namespace std;
int main(int argc, char *argv[])
{
char sz[] = “Hello, World!”; //Hover mouse over “sz” while debugging to see its contents
cout << sz << endl; //<================= Put a breakpoint here
return 0;
}Hi,
Please try enabling the verbose logging (Tools->Options->VisualGDB) and rebuild your project. Does the delay happen after any particular line in the verbose log?
OK, here are the results…
1> Build started: Project: delete_me, Configuration: Debug Win32……small delay ~0.5->1 second……..
1> VisualGDB: using project file C:devscratchpaddelete_medelete_me.vcxproj
1> VisualGDB: using solution file C:devscratchpaddelete_medelete_me.sln
1> VisualGDB: using configuration Debug……big wait here ~2 seconds…….
1> VisualGDB: Trying to detect if your Makefiles need updating... Using configuration: Debug|Win32
1> VisualGDB: Found a makefile: C:devscratchpaddelete_meMakefile
1> VisualGDB: Found 1 source file(s):
1> delete_me.cpp
1> VisualGDB: Found 0 excluded file(s) for current configuration:
1> VisualGDB: No source changes detected. C:devscratchpaddelete_meMakefile needs no updating.
1> VisualGDB: Run "cmd.exe /c "C:devgcc_distsmingwmingw32binmingw32-make.exe" CONFIG=Debug" in directory "C:devscratchpaddelete_me" on local computer
1> mingw32-make: Nothing to be done for 'all'.Hi,
There should not be anything performance-critical between those lines. How large is the RAM on that machine and how much of it is used according to Task Manager?
- You must be logged in to reply to this topic.