GNOME.org
 

gtkmm-documentation r71 - in trunk: . docs/tutorial/C docs/tutorial/C/figures

Author: arminb
Date: Tue Oct 21 22:16:05 2008
New Revision: 71
URL: http://svn.gnome.org/viewvc/gtkmm-documentation?rev=71&view=rev

Log:
2008-10-21  Armin Burgmeier  <armin openismus com>

	* docs/tutorial/C/gtkmm-tut.xml: Removed the section on MSVC++ 2005 as
	it has been moved to the wiki on
	http://live.gnome.org/gtkmm/MSWindows/UsingMSVC. Fixed the installer
	link in the Windows packaging section.

	* docs/tutorial/C/figures/msvc_*.png: Removed.


Removed:
   trunk/docs/tutorial/C/figures/msvc_add_existing_property_sheet.png
   trunk/docs/tutorial/C/figures/msvc_application_settings.png
   trunk/docs/tutorial/C/figures/msvc_corrected_main.png
   trunk/docs/tutorial/C/figures/msvc_corrected_stdafx.png
   trunk/docs/tutorial/C/figures/msvc_main_program.png
   trunk/docs/tutorial/C/figures/msvc_new_project_dialog.png
   trunk/docs/tutorial/C/figures/msvc_new_project_menu.png
   trunk/docs/tutorial/C/figures/msvc_project_created.png
   trunk/docs/tutorial/C/figures/msvc_project_properties.png
   trunk/docs/tutorial/C/figures/msvc_properties_maincrtstartup.png
   trunk/docs/tutorial/C/figures/msvc_properties_noinherit.png
   trunk/docs/tutorial/C/figures/msvc_properties_remove_warning_4250.png
   trunk/docs/tutorial/C/figures/msvc_properties_subsystem_windows.png
   trunk/docs/tutorial/C/figures/msvc_property_files.png
   trunk/docs/tutorial/C/figures/msvc_property_manager.png
   trunk/docs/tutorial/C/figures/msvc_property_manager_with_gtkmm_properties.png
Modified:
   trunk/ChangeLog
   trunk/docs/tutorial/C/gtkmm-tut.xml

Modified: trunk/docs/tutorial/C/gtkmm-tut.xml
==============================================================================
--- trunk/docs/tutorial/C/gtkmm-tut.xml	(original)
+++ trunk/docs/tutorial/C/gtkmm-tut.xml	Tue Oct 21 22:16:05 2008
@@ -294,8 +294,8 @@
 
 <sect1 id="sec-packages-windows">
 <title>Microsoft Windows</title>
-<para>GTK+ and &gtkmm; were designed to work well with Microsoft Windows, and the developers encourage its use on the win32 platform.  However, Windows has no standard installation system for development libraries. Please see the <link linkend="sec-windows-installation">Windows Installation</link>
-appendix for Windows-specific installation instructions and notes.</para>
+<para>GTK+ and &gtkmm; were designed to work well with Microsoft Windows, and the developers encourage its use on the win32 platform.  However, Windows has no standard installation system for development libraries. Please see the <link url="http://live.gnome.org/gtkmm/MSWindows";>Windows Installation</link>
+page for Windows-specific installation instructions and notes.</para>
 </sect1>
 
 </chapter>
@@ -9408,363 +9408,6 @@
 
 </appendix>
 
-<appendix id="chapter-msvc">
-<title>Using &gtkmm; with Visual Studio 2005</title>
-<sect1 id="sec-installing-and-configuring-vs2005-express">
-<title>Installing and Configuring Visual Studio 2005 Express</title>
-<para>
-You may wish to build and run &gtkmm; applications on Microsoft Windows with the
-free-of-cost Visual Studio 2005 Express Edition. The following instructions
-descibe how to configure a workstation to build &gtkmm; applications easily. If
-you already have Visual Studio 2005 Standard Edition or above, skip to the
-section titled <link linkend="sec-win32-installing-gtkmm-exe">Installing
-  Gtkmm</link>
-</para>
-
-<para>
-Download Visual Studio 2005 Express from <ulink
-  url="http://www.microsoft.com/express/2005/";>Microsoft's Visual
-  C++ Download Page.</ulink>
-</para>
-
-<para>
-After installing VS 2005 Express, you'll need to download the Windows Platform
-SDK. Because Microsoft requires that you validate your Windows install using the
-GenuineAdvantage ActiveX control, you must download it using Internet Explorer
-from a Windows box with a valid license.
-</para>
-
-<para>
-The Platform SDK can be downloaded from the <ulink
-  url="http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&amp;displaylang=en";>platform
-  SDK download page.</ulink>
-</para>
-
-<para>
-After installing the Platform SDK, use the instructions from <ulink
-  url="http://www.microsoft.com/express/2005/platformsdk/default.aspx";>Brian
-  Johnson</ulink> to configure Visual Studio to build native Win32
-Applications. 
-</para>
-</sect1>
-
-<sect1 id="sec-win32-installing-gtkmm-exe">
-<title>Installing &gtkmm;</title>
-<para>
-Once Visual Studio is installed and has been configured to build native Win32
-applications, you must install the &gtkmm; development package. To do this,
-download and install the &gtkmm; development package from the
-<ulink url="http://ftp.gnome.org/pub/gnome/binaries/win32/gtkmm/";>Gnome FTP
-  site.</ulink> At the time of this writing, the latest version is 2.14. Do not
-  be afraid of the size of the development packages as they are much larger
-  than the runtime packages which your end users will depend on.
-</para>
-</sect1>
-
-<sect1 id="sec-visual-studio-new-project">
-<title>Creating a New Project with Gtkmm Support</title>
-<sect2 id="visual-studio-getting-started">
-  <title>Getting Started</title>
-  <para>
-    First, create a new project in Visual Studio by Selecting <literal>New
-      Project</literal> in the <literal>File</literal> menu as shown in <xref
-      linkend="figure-msvc-new-project"/>. From the <literal>New
-      Project</literal> window, make sure to select <literal>Win32</literal> and
-    <literal>Console Application</literal> as shown in <xref
-      linkend="figure-msvc-new-project-dialog"/>. Also, give your project a name
-    and a location. For this example, the name of the project is
-    <literal>gtkmm_test</literal> and the location is
-    <literal>C:\work</literal>.
-  </para>
-
-  <para>
-    <figure id="figure-msvc-new-project">
-      <title>Selecting <literal>New Project</literal> from the menu.</title>
-      <screenshot>
-        <graphic format="PNG" fileref="&url_figures_base;msvc_new_project_menu.png"/>
-      </screenshot>
-    </figure>
-  </para>
-
-  <para>
-    <figure id="figure-msvc-new-project-dialog">
-      <title>Selecting Win32 Console Application.</title>
-      <screenshot>
-        <graphic format="PNG" fileref="&url_figures_base;msvc_new_project_dialog.png"/>
-      </screenshot>
-    </figure>
-  </para>
-
-  <para>
-    <figure id="figure-msvc-application-settings">
-      <title>Verifying Application Settings.</title>
-      <screenshot>
-        <graphic format="PNG" fileref="&url_figures_base;msvc_application_settings.png"/>
-      </screenshot>
-    </figure>
-  </para>
-
-  <para>
-    Clicking <literal>Finish</literal> will create for you a new native Win32
-    console project. Now we need to modify this project to use Gtkmm.
-  </para>
-
-  <para>
-    <figure id="figure-msvc-project-created">
-      <title>New Project as Created by Visual Stuido.</title>
-      <screenshot>
-        <graphic format="PNG" fileref="&url_figures_base;msvc_project_created.png"/>
-      </screenshot>
-    </figure>
-  </para>
-</sect2>
-
-<sect2 id="visual-studio-correct-main">
-  <title>Correct <literal>main()</literal> function</title>
-  <para>
-    The first order of business for this new project is to correct the
-    <literal>main()</literal> function. Visual Studio wants to use a translated
-    main function called <literal>_tmain()</literal>. This is fine, but will
-    give you a non-portable project, and one of the goals of &gtkmm; is to
-    provide a framework for portable applications. That being said, remove
-    <literal>_tmain()</literal> and replace it with good old fashioned
-    <literal>main()</literal>, just like mom used to make.
-  </para>
-
-  <para>
-    <figure id="figure-msvc-corrected-main">
-      <title>Corrected <literal>main()</literal> function.</title>
-      <screenshot>
-        <graphic format="PNG" fileref="&url_figures_base;msvc_corrected_main.png"/>
-      </screenshot>
-    </figure>
-  </para>
-</sect2>
-
-<sect2 id="visual-studio-correct-stdafx">
-  <title>Correct <literal>stdafx.h</literal></title>
-  <para>
-    The next thing to alter is the <literal>stdafx.h</literal> precompiled
-    header file. At the time of this writing, many Windows programmers are
-    familiar with the concept of precompiled headers. However, many Unix
-    programmers are not, as precompiled header support was only recently added
-    to GCC (in version 3.4) and is still not used in most open source projects.
-    Unix programmers may be tempted to just disable precompiled headers
-    altogether, but think carefully before doing this. Proper use of precompiled
-    headers provides a much improved compile time when using &gtkmm;, and will
-    save you many hours over the course of a project.
-  </para>
-
-  <para>
-    <xref linkend="figure-msvc-corrected-stdafx"/> shows how to change the default <literal>stdafx.h</literal> to be more portable, and also shows the include line for the <literal>&gtkmm;.h</literal> header file. The portability changes include removing the <literal>#pragma once</literal> line and replacing it with a standard <literal>#ifdef</literal> include guard as well as removing the <literal>tchar.h</literal> include. It is advisable to put all of your &gtkmm; related headers (e.g.: <literal>libglademm.h, libxml++</literal>, etc.) in this file as opposed to other files as this will <emphasis>greatly</emphasis> speed up the compilation of your project.
-  </para>
-
-  <figure id="figure-msvc-corrected-stdafx">
-    <title>Corrected <literal>stdafx.h</literal> header file.</title>
-    <screenshot>
-      <graphic format="PNG" fileref="&url_figures_base;msvc_corrected_stdafx.png"/>
-    </screenshot>
-  </figure>
-</sect2>
-
-<sect2 id="visual-studio-simple-window">
-  <title>Add Code to Create a Simple &gtkmm; Window</title>
-  <para>
-    Next, add the contents of a simple &gtkmm; program to the
-    <literal>main()</literal> function. The example shown in the figure below is
-    the one from <xref linkend="chapter-basics"/>
-  </para>
-
-  <figure id="figure-msvc-main-program">
-    <title>Simple &gtkmm; Program.</title>
-    <screenshot>
-      <graphic format="PNG" fileref="&url_figures_base;msvc_main_program.png"/>
-    </screenshot>
-  </figure>
-</sect2>
-
-<sect2 id="visual-studio-property-files">
-  <title>Add the MSVC Property Files for &gtkmm;</title>
-  <para>
-    The next step is to add the MSVC Property files which come with the &gtkmm;
-    distribution. As of the 2005 version, Visual Studio supports the use of
-    property files for adding settings to a project. Property files can contain
-    build settings of all kinds (e.g.: defines, include paths, link paths, and
-    libraries) and make it easy to build against 3rd party packages. When a
-    property file is added to a project, the project inherits all the build
-    settings which the property file specifies. To keep your project portable
-    (portable in the relative path vs. fixed path sense), you will want to copy
-    the property files from the &gtkmm; distribution (commonly
-    <literal>C:\Gtk\MSVC\</literal>) to the directory which contains your
-    project (in our case <literal>C:\work\&gtkmm;_test\</literal>).
-  </para>
-
-  <figure id="figure-msvc-property-files">
-    <title>Visual Studio Property files in the &gtkmm; Distribution.</title>
-    <!-- TODO: Make a new screenshot that shows the new gtkmm-vc80-d-2_4.vsprops -->
-    <screenshot>
-      <graphic format="PNG" fileref="&url_figures_base;msvc_property_files.png"/>
-    </screenshot>
-  </figure>
-
-  <para>
-    Next, add the property files to your project. Do this by clicking the
-    <literal>Property Manager</literal> tab of your Solution explorer as
-    indicated in <xref linkend="figure-msvc-property-manager" />.
-  </para>
-
-  <figure id="figure-msvc-property-manager">
-    <title>Property Manager (left) with <literal>Property Manager</literal> tab circled.</title>
-    <screenshot>
-      <graphic format="PNG" fileref="&url_figures_base;msvc_property_manager.png"/>
-    </screenshot>
-  </figure>
-
-  <para>
-    Right-Click on the <literal>Debug | Win32</literal> folder and select
-    <literal>Add Existing Property Sheet.</literal> From the file browser,
-    select the file <literal>&gtkmm;-vc80-<literal>d</literal>-2_4.vsprops</literal>.
-    Next, Right-Click on the <literal>Release | Win32</literal> folder and again
-    select <literal>Add Existing Property Sheet.</literal> From the file
-    browser, this time select the file <literal>&gtkmm;-vc80-2_4.vsprops</literal>.
-    If you are using MSVC++ 2008 instead of MSVC++ 2005, then you might want
-    to use the vc90 property sheets instead. When you are done, the Property
-    Manager should look like the one in <xref
-      linkend="figure-msvc-property-manager-with-gtkmm-properties" />.
-  </para>
-
-  <figure id="figure-msvc-add-existing-property-sheet">
-    <title>Adding an Existing Property Sheet.</title>
-    <screenshot>
-      <graphic format="PNG" fileref="&url_figures_base;msvc_add_existing_property_sheet.png"/>
-    </screenshot>
-  </figure>
-
-  <figure id="figure-msvc-property-manager-with-gtkmm-properties">
-    <title>Property manager with &gtkmm; property files added.</title>
-    <screenshot>
-      <graphic format="PNG" fileref="&url_figures_base;msvc_property_manager_with_gtkmm_properties.png"/>
-    </screenshot>
-  </figure>
-</sect2>
-
-<sect2 id="visual-studio-project-settings">
-  <title>Change a Few Project Settings</title>
-  <para>
-    At this point we're almost done. The last part is to change a few settings
-    in the <literal>Project Properties</literal> page. The easiest way to get to
-    this page is to right-click on the project name in the Solution Explorer and
-    click the <literal>Properties</literal> menu item as shown in <xref
-      linkend="figure-msvc-project-properties"/>.
-  </para>
-
-  <figure id="figure-msvc-project-properties">
-    <title>Opening the Project Properties.</title>
-    <screenshot>
-      <graphic format="PNG" fileref="&url_figures_base;msvc_project_properties.png"/>
-    </screenshot>
-  </figure>
-
-  <para>
-    The first thing to do is remove the <literal>$(NoInherit)</literal> option
-    from the linker settings as shown in <xref
-      linkend="figure-msvc-properties-noinherit"/>. Get to the linker page using
-    the tree on the left. Open <literal>Configuration Properties,</literal> then
-    <literal>Linker,</literal> then click on <literal>Input</literal>. Now
-    remove the <literal>$(NoInherit)</literal> token from the
-    <literal>Additional Dependencies</literal> line. Make sure to do this in
-    both <literal>Debug</literal> and <literal>Release</literal> modes.
-  </para>
-
-  <figure id="figure-msvc-properties-noinherit">
-    <title>Removing the <literal>$(NoInherit)</literal> flag.</title>
-    <screenshot>
-      <graphic format="PNG" fileref="&url_figures_base;msvc_properties_noinherit.png"/>
-    </screenshot>
-  </figure>
-
-  <para>
-    At this point your application will build and run. However, The &gtkmm;
-    headers will cause a harmless warning during the build. Fortunately, this
-    warning can be disabled from the same Project Settings dialog. In the tree
-    on the left of the dialog, open <literal>Configuration Properties,</literal>
-    then <literal>C/C++,</literal> then click <literal>Advanced</literal>. Now
-    type <literal>4250</literal> in the <literal>Disable Specific
-      Warnings</literal> field as shown in <xref
-      linkend="figure-msvc-properties-remove-warning-4250"/>. Make sure to make
-    this change in both <literal>Release</literal> and <literal>Debug</literal>
-    modes. Press <literal>Ok</literal> when done.
-  </para>
-
-  <figure id="figure-msvc-properties-remove-warning-4250">
-    <title>Disabling warning 4250.</title>
-    <screenshot>
-      <graphic format="PNG" fileref="&url_figures_base;msvc_properties_remove_warning_4250.png"/>
-    </screenshot>
-  </figure>
-</sect2>
-
-<sect2 id="visual-studio-windows-console">
-  <title>About the Windows Console</title>
-  <para>
-    If you build and run your application now, you will see a simple Gtk+ window
-    appear with nothing on it. Your application will also pop up a console
-    window with it. The console window is quite valuable for debugging a &gtkmm;
-    application because many Gtk+ warnings will print to this console and
-    nowhere else (unlike the <literal>OutputDebugString()</literal> or
-    <literal>TRACE()</literal> functions which Windows programmers are familiar
-    with).
-  </para>
-
-  <para>
-    When you release your application however, you will probably want to have it
-    <emphasis>not</emphasis> pop up the console. This requires two small changes
-    to the linker settings. From the tree on the left of the properties page,
-    open <literal>Configuration Properties,</literal> then
-    <literal>Linker,</literal> then <literal>System</literal>. Now change the
-    value of the <literal>Subsystem</literal> field from
-    <literal>CONSOLE</literal> to <literal>WINDOWS</literal> as shown in <xref
-      linkend="figure-msvc-properties-subsystem-windows"/>. This will disable
-    the creation of the console window when your app starts. When you do this,
-    you also have to change the entry point of your application. From the tree
-    on the left, select <literal>Advanced</literal> then change the
-    <literal>Entry Point</literal> field to read
-    <literal>mainCRTStartup</literal> (make sure to use the proper case) as
-    shown in <xref linkend="figure-msvc-properties-maincrtstartup"/>.
-  </para>
-
-  <para>
-    Some users have found it convenient to leave the console active in Debug
-    mode and disabled in Release mode. Others will want to have it the same in
-    both modes. It is completely up to the preference of the developer. Press
-    <literal>Ok</literal> when done. 
-  </para>
-
-  <figure id="figure-msvc-properties-subsystem-windows">
-    <title>Setting the Subsystem to <literal>Windows</literal> to disable the console.</title>
-    <screenshot>
-      <graphic format="PNG" fileref="&url_figures_base;msvc_properties_subsystem_windows.png"/>
-    </screenshot>
-  </figure>
-
-  <figure id="figure-msvc-properties-maincrtstartup">
-    <title>Setting the correct entry point symbol for Windows programs using <literal>main()</literal>.</title>
-    <screenshot>
-      <graphic format="PNG" fileref="&url_figures_base;msvc_properties_maincrtstartup.png"/>
-    </screenshot>
-  </figure>
-
-  <para>
-    That's all there is to it. After this initial setup, your &gtkmm; app can be
-    edited, built, and run just like any other Visual Studio project.
-  </para>
-
-</sect2>
-
-</sect1>
-
-</appendix>
-
 </book>
 
 <!-- some vim settings
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]