On Sat, Apr 27, 2013 at 7:49 AM, Richard Shaw <[email protected]> wrote:
> 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? Those programs are useful in non-package situations. They are useful for people who clone the git repository and make changes. They may also be useful during the package build, allowing you to test the library before you pack it into a *.deb or *.rpm file. In a package, such as a *.deb or *.rpm, you should only be shipping a *.so file and some *.h files. The comment about static linking as a security issue is inapplicable to files that don't ship in the package. Stuff can't become a security issue if it never ends up getting installed. This is not to suggest that linking (either static or shared) is a good idea; that would mean that library-internal symbols are getting exported. Plain #include is better. ------------------------------------------------------------------------------ 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
