Never use stdafx stuff on open source project. Don't use precompiled header.
On 13 November 2012 14:33, Arbol One <[email protected]> wrote: > I would also keep this feature, however, in the case of SQLite3 > amalgamation, I am really confused. You know how we have to #include the > 'stdafx.h' in every declaration file (making it non-portable code), i.e. > .c, .cpp, etc., well, I tried doing the same thing with sqlite.c, but VS10 > complains about it. > > What a nightmare Visual Studio is >:( > > Genius might have limitations, but stupidity is no handicap > Eat Kosher > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of John Drescher > Sent: Monday, November 12, 2012 7:44 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] VC++ and SQLite > > On Mon, Nov 12, 2012 at 1:52 PM, Doug Nebeker <[email protected]> > wrote: > > You might be surprised at the speed increase you see in compile time > > if you've got large projects. The time isn't lost to CPU as much, but > > disk I/O time adds up when hitting many hundreds of small (header) > > files (even with an SSD). > > > > This is why I use PCH. Building some of my projects take a long time even > on a 12 threaded processor with multiple SSDs. > > > -- > John M. Drescher > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Noël Frankinet Strategis sprl 0478/90.92.54 _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
