Tomash Brechko <[EMAIL PROTECTED]> wrote: > [H]ow to properly compile the amalgamation wrt C preprocessor > defines? Suppose I got sources tarball, and did './configure > --some-options CFLAGS=...'. This produces a Makefile, I can do 'make > sqlite3.c', but I also would like to be able to do 'make sqlite3.o', > so that compilation would actually use all the proper C preprocessor > defines and options resulted from 'configure' run. Currently, I have > to look though generated Makefile to see what options/defines I should > use to get the same result. It there a better way?
There is no better way. But you are welcomed to submit patches against the makefile. > > Why pread()/pwrite() aren't used by default? Because they are busted on version of Linux currently running on my desktop (SuSE 10.1). -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
