On 16 Dec 2012, at 11:10pm, Tim Johnson <t...@akwebsoft.com> wrote: > I've recently set up drupal on my workstation which is hosting Mac > OSX 10.7. I would welcome > 1)Recommendations on what I should install to manage sqlite > 2)How they should be installed > NOTE: macports works well for me but alternative suggestions are > welcomed. > The macports list re sqlite can be seen here : > http://www.macports.org/ports.php?by=name&substr=sqlite
While as a Linux-user you expect to see DarwinPorts, MacPorts, Fink, Homebrew and/or other package managers, it might help to know that Mac-users don't think in those terms. There is almost no library-sharing on Macs. The two big collections of shared libraries are the ones which Apple supplies with OS X and the ones which Microsoft supplies with its Office suite. Normal professional and hobby programmers will use Apple's libraries intensively, and never use Microsoft's libraries unless they're specifically interfacing with Microsoft's stuff. A mundane Mac user hit with "This app requires jcrak and visdis." wouldn't know what to do about it. Normal Mac programmers generally statically link libraries and include copies of them (as .dylib files, or whole frameworks) as part of their application bundles. Almost nobody shares copies of libraries because the original reason for doing so has gone. You have to include an extra 1.1Meg of stuff with your application ? Your users have to find an extra 1.1Meg of disk space and it'll take them an extra six seconds to download it. Nobody cares. Disk space is cheaper than programmer time. Further upsides are that you always know exactly which version of libraries you're calling so you don't have to work around version faults, and you never have the problem of someone else's app installer overwriting your library and introducing unexpected behaviour. SQLite on a Mac has standard Mac behaviour here. As a programmer you aren't expected to use a library. You can download up-to-date source files for SQLite 'Amalgamated' version from the SQLite server <http://www.sqlite.org/download.html> and use those. You get .h and .c files, drop them into your IDE and go. If you're a database admin, or as a programmer you want to use a tool to admin the databases your apps will use, you get the sqlite3 command-line tool from the same page and use that. No shared libraries. In fact no library at all, just C source code. Think you've found a bug ? You've got the source code right there. Go look at it. If you find something, post here. But actually SQLite is used so much on Macs that Apple included a copy of the shell tool with the OS. You'll find a copy of the sqlite3 shell tool as /usr/bin/sqlite3 Apple's Developer Tools installations include copies of the .h and .c files (many many copies of the .h file) but I recommend that you just grab new ones from the SQLite server whenever you start a new project. That way you get all the recent features and bugfixes. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
