#18554: [PATCH] Update sqlite3 build process, add +fts3 variant -----------------------------------+---------------------------------------- Reporter: eridius@… | Owner: mww@… Type: enhancement | Status: closed Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.7.0 Resolution: wontfix | Keywords: Port: sqlite3 | -----------------------------------+---------------------------------------- Changes (by mww@…): * status: new => closed * resolution: => wontfix Comment: Regarding interprocedural optimization, gcc prior to 4.1 only supports inlining, so the edge of the amalgamation source should be minimal at best. Later versions of gcc and llvm may gain more from this source but as the bottleneck of sqlite is normally IO, the effect should again be minimal (if any). On PPC this might actually reduce performance as the larger binary (due to inlining) requires more memory; Apple compiles its sources for PPC optimized for size because of this. The [http://www.sqlite.org/amalgamation.html sqlite homepage] states that the amalgamation source is for integration (''...contains everything you need to integrate SQLite into a larger project''); To enable the FTS3 module, the amalgamation sources are not required. Should we add a {{{fts3}}} variant nevertheless? -- Ticket URL: <http://trac.macports.org/ticket/18554#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS