[no subject]

I have to rework my build systems to handle this new library naming
convention; offer
end-users a switch to select VC80/90 and then link to the correct libraries
after "assembling"
a library name based on the switch.

A better approach would have been to use the standard names we are
accustomed to:
cairomm-1_0.lib, sigc-2_0.lib, gtkmm-2_4.lib, etc. and creating separate
installers targeting
the required runtime.  The root of the installation tree would be the ONLY
place where the
runtime was indicated, e.g.:

C:\Program Files\Gtkmm-2.14.1-VC80

or

C:\Program Files\Gtkmm-2.14.1-VC90

That way, you can easily point into the needed tree to link instead of
having to rework
build systems.

Also, I haven't built gtkmm from source since this changeover.  What naming
convention
do you use for the import libraries when building with MSVC?  Do you
discover the runtime
version automatically and name appropriately?

Really would have preferred to see my approach above....

------=_Part_10370_29383210.1224091998550
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">I installed the latest gtkmm Windows development package and I have some comments.<br><br>From the point of view of application developers who require gtkmm as a dependency,<br>this new -vcXX- naming convention for the import libraries is a burden.<br>
<br>I have to rework my build systems to handle this new library naming convention; offer <br>end-users a switch to select VC80/90 and then link to the correct libraries after &quot;assembling&quot; <br>a library name based on the switch.<br>
<br>A better approach would have been to use the standard names we are accustomed to:<br>cairomm-1_0.lib, sigc-2_0.lib, gtkmm-2_4.lib, etc. and creating separate installers targeting<br>the required runtime.&nbsp; The root of the installation tree would be the ONLY place where the<br>
runtime was indicated, e.g.:<br><br>C:\Program Files\Gtkmm-2.14.1-VC80<br><br>or<br><br>C:\Program Files\Gtkmm-2.14.1-VC90 <br><br>That way, you can easily point into the needed tree to link instead of having to rework<br>
build systems.<br><br>Also, I haven&#39;t built gtkmm from source since this changeover.&nbsp; What naming convention<br>do you use for the import libraries when building with MSVC?&nbsp; Do you discover the runtime<br>version automatically and name appropriately?<br>
<br>Really would have preferred to see my approach above....<br>
</div>

------=_Part_10370_29383210.1224091998550--