How to improve linking time of a large library. | Together C & C++ | Page 1

fluid dome Oct 16, 2022, 2:08 PM

#

I have a relatively small, pure C project that needs to link with libshaderc. Before I added libshaderc as a dependency it took less than a second to compile just a few thousand lines of C code, but linking with libshaderc_combined adds 10 seconds to the build time, because I also have to link with the system math lib and the C++ stdlib. Is there a proper way to reduce the number of symbols I need to link (I only call around 5 functions from libshaderc) so that I can get my instant build times back?

calm tundraBOT Oct 16, 2022, 2:08 PM

#

When your question is answered use !solved to mark the question as resolved.

Remember to ask specific questions, provide necessary details, and reduce your question to its simplest form. For more information use !howto ask.

atomic flume Oct 16, 2022, 3:13 PM

#

have you tried adding all the stdlib files to a precompiled header? that is probably where most the compile time comes from

fluid dome Oct 16, 2022, 3:30 PM

#

atomic flume have you tried adding all the stdlib files to a precompiled header? that is prob...

wdym? the compile times aren't any longer really, the C interface to libshaderc does not include any stdlib files

#

the problem is linking the library into my executable

atomic flume Oct 16, 2022, 5:32 PM

#

I guess you might just build a library for the functionality you are using in that case, that might get you back to instant build times.

#

oh wait sorry, yeah I see what you are saying. Not sure actually.

#

would need to see your build command I guess

fluid dome Oct 16, 2022, 6:06 PM

#

fuck it im writing my own shader language glsl sucks anyway

calm tundraBOT Oct 17, 2022, 6:14 AM

#

This question thread is being automatically closed. If your question is not answered feel free to bump the post or re-ask. Take a look at !howto ask for tips on improving your question.

#How to improve linking time of a large library.