Author: wyoung
Date: Fri Feb  7 16:39:59 2014
New Revision: 2765

URL: http://svn.gna.org/viewcvs/mysqlpp?rev=2765&view=rev
Log:
- Added paragraph to README-Visual-C++.txt explaining the best way to
  get 32-bit builds out of VC++ 2008 and newer.

- Clarified the paragraph explaining how VC++ 2012 wrecks the library
  linkage paths when converting the vc2008\* projects, so that the
  solution is more readily apparent.

Modified:
    trunk/README-Visual-C++.txt

Modified: trunk/README-Visual-C++.txt
URL: 
http://svn.gna.org/viewcvs/mysqlpp/trunk/README-Visual-C%2B%2B.txt?rev=2765&r1=2764&r2=2765&view=diff
==============================================================================
--- trunk/README-Visual-C++.txt (original)
+++ trunk/README-Visual-C++.txt Fri Feb  7 16:39:59 2014
@@ -51,12 +51,24 @@
     versions of Visual C++, but beware that the upgrade feature tends
     to be problematic.
 
-    When converting the VC++ 2008 project files to VC++ 2012,
-    I found that it will screw up the output file names for the
-    libraries, so that none of the executables will link properly.
-    This problem is detected by the migration process, so that even
-    though the tool doesn't know how to fix it itself, you can fix
-    it up manually afterward.
+    If you want to do a 32-bit build on VC++ 2008 or newer, it is
+    easiest to open the vc2005\* project files and let Visual Studio
+    upgrade them for you.  The alternative, starting with the vc2008
+    files, requires that you add a 32-bit build option to all of the
+    many targets in MySQL++, then optionally delete the 64-bit targets.
+    This is a lot more work.  Plus, it only works if you have the
+    64-bit compilers installed, since Visual Studio will refuse to
+    open project files where all targets must be built with compilers
+    that aren't installed, even if your goal is to immediately adjust
+    them to use compilers that *are* installed.
+
+    When converting the VC++ 2008 project files to VC++ 2012, Visual
+    Studio will change the output directories from Debug to Debug\x64
+    (and similar for Release), but it won't also change the link paths
+    from Debug to Debug\x64, so that the library and examples will
+    compile but not link.  The migration tool detects that there is
+    a problem, but it can't fix its own mess.  You have to manually
+    fix it.
 
     There were also problems in VC++ 2010 when you had converted 32-bit
     VC++ 2008 projects and then were trying to switch them to 64-bit.


_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits

Reply via email to