Re: [DynInst_API:] Building Static Libraries

["Mark W. Krentel" <krentel@xxxxxxxx>]

You may also need to turn off cotire.  In the past, we've seen
problems with cotire and parallel builds.  Something about cotire
generating some header files twice.  In a parallel build, this could
result in one process writing a file while another one is reading it
and crashing the build.

Bill, I just checked dyninst master.  I still don't see an option to
turn off cotire, other than patching shared.cmake.  I thought we were
going to provide a cmake/ccmake option for this.

--Mark


On 04/02/18 14:33, Bill Williams wrote:
> There should be an enable_static_libs option in CMake, which will add _static targets for each component. So:
>
> cmake [usual options] -DENABLE_STATIC_LIBS=TRUE
> make dyninstAPI_static
> make install
>
> should do the trick.
>
> --bw
> ________________________________________
> From: Dyninst-api <dyninst-api-bounces@xxxxxxxxxxx> on behalf of Buddhika Chamith Kahawitage Don <budkahaw@xxxxxxxxxxxx>
> Sent: Monday, April 2, 2018 2:05 PM
> To: dyninst-api
> Subject: [DynInst_API:] Building Static Libraries
>
> Hi All,
>
> How do I build Dyninst as static libraries?
>
> Regards
>
> _______________________________________________
> Dyninst-api mailing list
> Dyninst-api@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api