Commit 9a3cae17 authored by Chun-wei Fan's avatar Chun-wei Fan

build: Rename MSVC_Net2017 to MSVC_NMake

This prepares for the transition to using NMake Makefiles for building
glibmm, rather than the Visual Studio project files, to ease future
maintenance.
parent af768ca0
......@@ -43,10 +43,10 @@ nodist_giomm_libinclude_HEADERS = gio/giommconfig.h
pkgconfigdir = $(libdir)/pkgconfig
nodist_pkgconfig_DATA = glib/$(GLIBMM_MODULE_NAME).pc gio/$(GIOMM_MODULE_NAME).pc
include $(srcdir)/MSVC_Net2017/filelist.am
include $(srcdir)/MSVC_NMake/filelist.am
text_files = COPYING.tools README.SUN README.win32
msvc_files = $(addprefix MSVC_Net2017/,$(msvc_net2017_data))
msvc_files = $(addprefix MSVC_NMake/,$(msvc_net2017_data))
dist_noinst_DATA = $(text_files) $(msvc_files)
dist_noinst_SCRIPTS = autogen.sh
......
......@@ -46,7 +46,7 @@ make install
2. MS Visual Studio 2017
Open the glibmm.sln solution file in the MSVC_Net2017 directory. In
Open the glibmm.sln solution file in the MSVC_NMake directory. In
the Tools/Options panel, add the appropriate GTK+ include and lib
directories to the Projects and Solutions/VC++ directories, if they
are not in the locations specified by the property sheets, i.e.
......
......@@ -169,12 +169,12 @@ AC_CONFIG_FILES([Makefile
examples/Makefile
docs/Makefile
docs/reference/Doxyfile
MSVC_Net2017/glibmm/glibmm.rc
MSVC_Net2017/giomm/giomm.rc])
MSVC_NMake/glibmm/glibmm.rc
MSVC_NMake/giomm/giomm.rc])
# Copy the generated configuration headers into the MSVC project directories.
AC_CONFIG_COMMANDS([MSVC_Net2017/glibmm/glibmmconfig.h],
[cp -f glib/glibmmconfig.h MSVC_Net2017/glibmm/glibmmconfig.h])
AC_CONFIG_COMMANDS([MSVC_Net2017/giomm/giommconfig.h],
[cp -f gio/giommconfig.h MSVC_Net2017/giomm/giommconfig.h])
AC_CONFIG_COMMANDS([MSVC_NMake/glibmm/glibmmconfig.h],
[cp -f glib/glibmmconfig.h MSVC_NMake/glibmm/glibmmconfig.h])
AC_CONFIG_COMMANDS([MSVC_NMake/giomm/giommconfig.h],
[cp -f gio/giommconfig.h MSVC_NMake/giomm/giommconfig.h])
AC_OUTPUT
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment