BGL: Debug too slow
It seems my debug build is exteremely slow in the parts that call boost graph library functions. Is there a way I can force the boost lib files to compile with optimizations even though the rest of my app is in debug?? Cheers -John Krajewski
John Krajewski wrote:
It seems my debug build is exteremely slow in the parts that call boost graph library functions. Is there a way I can force the boost lib files to compile with optimizations even though the rest of my app is in debug??
Unlikely. Because Boost.Graph is header-only, it's compiled with whatever settings your application is. If you have few .cpp files that use BGL, you can build those .cpp files in release mode, using whatever mechanism your build system provides. - Volodya
It seems my debug build is exteremely slow in the parts that call boost graph library functions. Is there a way I can force the boost lib files to compile with optimizations even though the rest of my app is in debug??
Unlikely. Because Boost.Graph is header-only, it's compiled with whatever settings your application is. If you have few .cpp files that use BGL, you can build those .cpp files in release mode, using whatever mechanism your build system provides.
You could encapsulate your use of the BGL behind a compiled library. The library could be built for release while the client code is in debug. Obviously, this is unlikely to work if all of your client code is also templated. Andrew Sutton andrew.n.sutton@gmail.com
participants (3)
-
Andrew Sutton -
John Krajewski -
Vladimir Prus