AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
b3bd5fefb1
gtk2/build/win32/detectenv-msvc.mak

77 lines
2.1 KiB
Makefile
Raw Normal View History

MSVC builds: Update how introspection builds are done This first adds a common autotools module that can be included by the Makefile.am's to generate the file lists and the g-ir-scanner/ g-ir-compiler command lines to build the introspection files. The autotools files for gdk/ and gtk/ are then updated to generate the full file lists needed to build the introspection files, with the full command lines for g-ir-scanner and g-ir-compiler as NMake Makefile modules that can be used to build the introspection files for Visual Studio builds. https://bugzilla.gnome.org/show_bug.cgi?id=765195
2015-09-08 06:14:46 +00:00
# Common NMake Makefile module for checking the build environment
# This can be copied from $(glib_srcroot)\build\win32 for GNOME items
# that support MSVC builds and introspection under MSVC, and can be used
# for building test programs as well.
MSVC Builds: Rework Introspection Build The current approach of building the introspection files for GTK works, but is often cumbersome as one needs to set many environmental variables before launching a solution file, which runs a Windows batch script to generate the .gir/.typelib files. It was also possible to hand-run the batch script from the Visual Studio command prompt, but even more environmental variables need to be set. This changes the approach to build the introspection files using an NMake Makefile (but elimating from the Visual Studio Project Files the part to build the introspection files) to: -Make it clearer to the person building the introspection files what environmental variables are needed, specifically for PKG_CONFIG_PATH and MINGWDIR and CFG (formerly CONF). Setting stuff like VSVER, PLAT and BASEDIR is no longer required, which was a bit clunky. -Allows some more easier flexibility on the build of the intropsection files.
2014-01-13 08:05:00 +00:00
# Check to see we are configured to build with MSVC (MSDEVDIR, MSVCDIR or
# VCINSTALLDIR) or with the MS Platform SDK (MSSDK or WindowsSDKDir)
!if !defined(VCINSTALLDIR) && !defined(WINDOWSSDKDIR)
MSG = ^
This Makefile is only for Visual Studio 2008 and later.^
You need to ensure that the Visual Studio Environment is properly set up^
before running this Makefile.
!error $(MSG)
!endif
ERRNUL = 2>NUL
_HASH=^#
!if ![echo VCVERSION=_MSC_VER > vercl.x] \
&& ![echo $(_HASH)if defined(_M_IX86) >> vercl.x] \
&& ![echo PLAT=Win32 >> vercl.x] \
&& ![echo $(_HASH)elif defined(_M_AMD64) >> vercl.x] \
&& ![echo PLAT=x64 >> vercl.x] \
&& ![echo $(_HASH)endif >> vercl.x] \
&& ![cl -nologo -TC -P vercl.x $(ERRNUL)]
!include vercl.i
!if ![echo VCVER= ^\> vercl.vc] \
&& ![set /a $(VCVERSION) / 100 - 6 >> vercl.vc]
!include vercl.vc
!endif
!endif
!if ![del $(ERRNUL) /q/f vercl.x vercl.i vercl.vc]
!endif
!if $(VCVERSION) > 1499 && $(VCVERSION) < 1600
VSVER = 9
!elseif $(VCVERSION) > 1599 && $(VCVERSION) < 1700
VSVER = 10
!elseif $(VCVERSION) > 1699 && $(VCVERSION) < 1800
VSVER = 11
!elseif $(VCVERSION) > 1799 && $(VCVERSION) < 1900
VSVER = 12
MSVC builds: Update how introspection builds are done This first adds a common autotools module that can be included by the Makefile.am's to generate the file lists and the g-ir-scanner/ g-ir-compiler command lines to build the introspection files. The autotools files for gdk/ and gtk/ are then updated to generate the full file lists needed to build the introspection files, with the full command lines for g-ir-scanner and g-ir-compiler as NMake Makefile modules that can be used to build the introspection files for Visual Studio builds. https://bugzilla.gnome.org/show_bug.cgi?id=765195
2015-09-08 06:14:46 +00:00
!elseif $(VCVERSION) > 1899 && $(VCVERSION) < 2000
VSVER = 14
MSVC Builds: Rework Introspection Build The current approach of building the introspection files for GTK works, but is often cumbersome as one needs to set many environmental variables before launching a solution file, which runs a Windows batch script to generate the .gir/.typelib files. It was also possible to hand-run the batch script from the Visual Studio command prompt, but even more environmental variables need to be set. This changes the approach to build the introspection files using an NMake Makefile (but elimating from the Visual Studio Project Files the part to build the introspection files) to: -Make it clearer to the person building the introspection files what environmental variables are needed, specifically for PKG_CONFIG_PATH and MINGWDIR and CFG (formerly CONF). Setting stuff like VSVER, PLAT and BASEDIR is no longer required, which was a bit clunky. -Allows some more easier flexibility on the build of the intropsection files.
2014-01-13 08:05:00 +00:00
!else
VSVER = 0
!endif
!if "$(VSVER)" == "0"
MSG = ^
This NMake Makefile set supports Visual Studio^
MSVC builds: Update how introspection builds are done This first adds a common autotools module that can be included by the Makefile.am's to generate the file lists and the g-ir-scanner/ g-ir-compiler command lines to build the introspection files. The autotools files for gdk/ and gtk/ are then updated to generate the full file lists needed to build the introspection files, with the full command lines for g-ir-scanner and g-ir-compiler as NMake Makefile modules that can be used to build the introspection files for Visual Studio builds. https://bugzilla.gnome.org/show_bug.cgi?id=765195
2015-09-08 06:14:46 +00:00
9 (2008) through 14 (2015). Your Visual Studio^
MSVC Builds: Rework Introspection Build The current approach of building the introspection files for GTK works, but is often cumbersome as one needs to set many environmental variables before launching a solution file, which runs a Windows batch script to generate the .gir/.typelib files. It was also possible to hand-run the batch script from the Visual Studio command prompt, but even more environmental variables need to be set. This changes the approach to build the introspection files using an NMake Makefile (but elimating from the Visual Studio Project Files the part to build the introspection files) to: -Make it clearer to the person building the introspection files what environmental variables are needed, specifically for PKG_CONFIG_PATH and MINGWDIR and CFG (formerly CONF). Setting stuff like VSVER, PLAT and BASEDIR is no longer required, which was a bit clunky. -Allows some more easier flexibility on the build of the intropsection files.
2014-01-13 08:05:00 +00:00
version is not supported.
!error $(MSG)
!endif
VALID_CFGSET = FALSE
MSVC builds: Update how introspection builds are done This first adds a common autotools module that can be included by the Makefile.am's to generate the file lists and the g-ir-scanner/ g-ir-compiler command lines to build the introspection files. The autotools files for gdk/ and gtk/ are then updated to generate the full file lists needed to build the introspection files, with the full command lines for g-ir-scanner and g-ir-compiler as NMake Makefile modules that can be used to build the introspection files for Visual Studio builds. https://bugzilla.gnome.org/show_bug.cgi?id=765195
2015-09-08 06:14:46 +00:00
!if "$(CFG)" == "release" || "$(CFG)" == "debug" || "$(CFG)" == "Release" || "$(CFG)" == "Debug"
MSVC Builds: Rework Introspection Build The current approach of building the introspection files for GTK works, but is often cumbersome as one needs to set many environmental variables before launching a solution file, which runs a Windows batch script to generate the .gir/.typelib files. It was also possible to hand-run the batch script from the Visual Studio command prompt, but even more environmental variables need to be set. This changes the approach to build the introspection files using an NMake Makefile (but elimating from the Visual Studio Project Files the part to build the introspection files) to: -Make it clearer to the person building the introspection files what environmental variables are needed, specifically for PKG_CONFIG_PATH and MINGWDIR and CFG (formerly CONF). Setting stuff like VSVER, PLAT and BASEDIR is no longer required, which was a bit clunky. -Allows some more easier flexibility on the build of the intropsection files.
2014-01-13 08:05:00 +00:00
VALID_CFGSET = TRUE
!endif
MSVC builds: Update how introspection builds are done This first adds a common autotools module that can be included by the Makefile.am's to generate the file lists and the g-ir-scanner/ g-ir-compiler command lines to build the introspection files. The autotools files for gdk/ and gtk/ are then updated to generate the full file lists needed to build the introspection files, with the full command lines for g-ir-scanner and g-ir-compiler as NMake Makefile modules that can be used to build the introspection files for Visual Studio builds. https://bugzilla.gnome.org/show_bug.cgi?id=765195
2015-09-08 06:14:46 +00:00
# We want debugging symbols logged for all builds,
# using .pdb files for release builds
CFLAGS_BASE = /Zi
!if "$(CFG)" == "release" || "$(CFG)" == "Release"
CFLAGS_ADD = /MD /O2 $(CFLAGS_BASE)
MSVC Builds: Rework Introspection Build The current approach of building the introspection files for GTK works, but is often cumbersome as one needs to set many environmental variables before launching a solution file, which runs a Windows batch script to generate the .gir/.typelib files. It was also possible to hand-run the batch script from the Visual Studio command prompt, but even more environmental variables need to be set. This changes the approach to build the introspection files using an NMake Makefile (but elimating from the Visual Studio Project Files the part to build the introspection files) to: -Make it clearer to the person building the introspection files what environmental variables are needed, specifically for PKG_CONFIG_PATH and MINGWDIR and CFG (formerly CONF). Setting stuff like VSVER, PLAT and BASEDIR is no longer required, which was a bit clunky. -Allows some more easier flexibility on the build of the intropsection files.
2014-01-13 08:05:00 +00:00
!else
MSVC builds: Update how introspection builds are done This first adds a common autotools module that can be included by the Makefile.am's to generate the file lists and the g-ir-scanner/ g-ir-compiler command lines to build the introspection files. The autotools files for gdk/ and gtk/ are then updated to generate the full file lists needed to build the introspection files, with the full command lines for g-ir-scanner and g-ir-compiler as NMake Makefile modules that can be used to build the introspection files for Visual Studio builds. https://bugzilla.gnome.org/show_bug.cgi?id=765195
2015-09-08 06:14:46 +00:00
CFLAGS_ADD = /MDd /Od $(CFLAGS_BASE)
MSVC Builds: Rework Introspection Build The current approach of building the introspection files for GTK works, but is often cumbersome as one needs to set many environmental variables before launching a solution file, which runs a Windows batch script to generate the .gir/.typelib files. It was also possible to hand-run the batch script from the Visual Studio command prompt, but even more environmental variables need to be set. This changes the approach to build the introspection files using an NMake Makefile (but elimating from the Visual Studio Project Files the part to build the introspection files) to: -Make it clearer to the person building the introspection files what environmental variables are needed, specifically for PKG_CONFIG_PATH and MINGWDIR and CFG (formerly CONF). Setting stuff like VSVER, PLAT and BASEDIR is no longer required, which was a bit clunky. -Allows some more easier flexibility on the build of the intropsection files.
2014-01-13 08:05:00 +00:00
!endif
!if "$(PLAT)" == "x64"
LDFLAGS_ARCH = /machine:x64
!else
LDFLAGS_ARCH = /machine:x86
!endif
Reference in New Issue Copy Permalink