Hello Arbol, There's nothing special about Stdafx.h or Stdafx.cpp. Even if you switch to a different compiler, they just compile with no PCH. You do have to create them if you're going to use them though. I typically copy them in from another project. I even use them in Linux projects because it's a nice place to centralize headers used by a project.
Once you understand the in's and outs of PCH in VS it's simply not that hard. I don't use PCH with Sqlite.c. It's in it's own library project which my main project links to. In that way, each project can compile however works best for it. Everything I write uses PCH, everything I inherit, might or might not use PCH. AO> What a nightmare Visual Studio is >:( You know what they say. It's a poor craftsman who blames his tools. Your problems with VS seem to stem from general noobishness. Learning devel tools is no different than learning a foreign language. You need to research it and learn how it all works. I think things would be alot easier for you if you made a new static lib project just for Sqlite, compile it there with no PCH and link it into your program. If you add the project as a "Reference" VS will link it in automatically. Tuesday, November 13, 2012, 8:33:48 AM, you wrote: AO> I would also keep this feature, however, in the case of SQLite3 AO> amalgamation, I am really confused. You know how we have to AO> #include the 'stdafx.h' in every declaration file (making it AO> non-portable code), i.e. .c, .cpp, etc., well, I tried doing the AO> same thing with sqlite.c, but VS10 complains about it. AO> What a nightmare Visual Studio is >:( AO> Genius might have limitations, but stupidity is no handicap AO> Eat Kosher AO> -----Original Message----- AO> From: sqlite-users-boun...@sqlite.org AO> [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of John Drescher AO> Sent: Monday, November 12, 2012 7:44 PM AO> To: General Discussion of SQLite Database AO> Subject: Re: [sqlite] VC++ and SQLite AO> On Mon, Nov 12, 2012 at 1:52 PM, Doug Nebeker <pa...@poweradmin.com> 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). >> AO> This is why I use PCH. Building some of my projects take a long AO> time even on a 12 threaded processor with multiple SSDs. AO> -- AO> John M. Drescher AO> _______________________________________________ AO> sqlite-users mailing list AO> sqlite-users@sqlite.org AO> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users AO> _______________________________________________ AO> sqlite-users mailing list AO> sqlite-users@sqlite.org AO> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Best regards, Teg mailto:t...@djii.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users