On Sat, Apr 27, 2013 at 1:46 AM, Albert Cahalan <[email protected]> wrote:
> > Yeah static linking for official linux packaging is a big no-no for
> security
> > reasons. With shared libraries, if a vulnerability is found in a library
> > then only the one needs to be updated. With static linking, every package
> > included in the distribution has to be updated, and that's if you can
> find
> > every one of them.
>
> It's fine for this because these executables don't belong in the package.
>
> If not cross-compiling, you might wish to run the executables during
> package creation to verify that the build is OK. Otherwise, there is no
> need to build them.
Thus far I have largely reimplemented the autotools build in cmake, so
until the autotools build is depreciated, I don't want to deviate from that
too much as I don't know what most of the binaries are used for.
So you're saying that the c2sim program is not useful beyond the package
building? Should I be using c2sim to do some checking during packaging
building? What about the other binaries?
Thanks,
Richard
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
