Age | Commit message (Collapse) | Author | Files | Lines |
|
Get rid of _CRT_SECURE_NO_WARNINGS and _CRT_NONSTDC_NO_WARNINGS
from the preprocessor definitions as those two macros are now defined
in msvc_recommended_pragmas.h, which is force-included in these projects
via the property sheets. This will silence C4005 warnings on macro
redefinition.
|
|
Missed the new glib/gstringchunk.h header that needed to be installed as
well.
|
|
Copy the deprecated headers in their appropriate places.
|
|
-Fix GLib project/filter files generation as some source items are under
the "deprecated" subfolder, and filter out the gthread-*.c
-Explicitly specify gthread-win32.c in the GLib project/filter file
templates, since tarballs are done on Linux.
-Don't define g_static_mutex_get_mutex in the pregenerated
glibconfig.h.win32(.in) as it is defined in deprecated/gthread.h for Windows
|
|
LibFFI 3.0.10 is now out officially...
|
|
Tell people about the GNOME Live! page that outlines building
GLib and its dependencies with Visual C++.
|
|
Stop the "installation" of gio/gtimezonemonitor.h as it has been removed
from GIO (commit 5b68b49b2072)
|
|
Define USE_SYSTEM_PCRE for all configurations which uses the PCRE that
was already built and "installed" beforehand (i.e. the *_ExtPCRE
configurations) so that the compilation will not pick up the
GLib-bundled pcre.h when one wants to use the PCRE "installation" on
his/her system.
|
|
-Added glib/ghmac.h to the list of files to copy during the "install" stage
-Cleaned up a bit (glib-2.0->glib-$(ApiVersion), where $(ApiVersion) is
2.0)
|
|
Copy the new GioTLS headers that were introduced into the GIO
library in commit 0f99cfa8822514dc6b7ccbc59efbe68f27aeb172 during the
"install" stage.
|
|
-Tell people about that libFFI is now needed.
-Tell people not to compile GLib in paths containing spaces.
|
|
Revert commit on distribution of this file as it is meant to be used in
a GIT checkout only.
|
|
|
|
This relates to my previous commit titled "add a script to generator
files for building" on behalf of Shixin Zeng.
Tell people about the availability of a python script to create the
necessary files for a Visual C++ build from a GIT checkout.
This is done with the courtesy of Shixin Zeng's python script which does
the job and eliminates the troubles of getting a suitable shell environment
to do the "make dist" job (which is especially not easy on Windows itself!)
|
|
Signed-off-by: Chun-wei Fan <fanchunwei@src.gnome.org>
|
|
Revert EOL of these files to Unix style as they are to be processed
during "make dist"
|
|
-In gio/Makefile.am, the name for one of the filters for capturing the
sources for the GIO VS Project Files is corrected.
-Remove the GIO source file items in the VS project files templates as
a result for this change, and move the entry of the "new"
gregistrysettingsbackend.c into the filter in gio/Makefile.am
|
|
-The VS2010 README.txt should have Windows CRLF EOL.
-Tell people about the added dependency on LibFFI
|
|
This time I realized that I needed to set autocrlf=false on my Windows side
... ugh...
This is one of those files that must have CRLF line endings to work
orrectly :|
|
|
-Reinstate build/win32/vs10/glib.sln with the correct EOL (DOS/Windows) so
that the file can be correctly recognized by Windows, rather than having
the "Unrecognized Visual Studio Version".
-Update the main GLib projects to output the DLL/LIB file into <Release or
Debug>\<Win32 or x64>\bin for all configurations.
-Update/simplify the property sheets to copy all DLL and LIB files from
<Release or Debug>\<Win32 or x64>\bin for all configurations.
-Update the VS 2008 property sheet to seperate the intermediate directories
for all projects as well to avoid errors/warnings of being unable to
write/access the PDB files as they are in use.
|
|
To fix up for the line endings (this needs to be in the DOS/Windows
format)
|
|
Consolidate my previous commit into property file... should have realized
this sooner...
|
|
-Seperate intermediate directories for each project to avoid intermittent
MSBuild errors that a build log cannot be written while in use, and
update the property sheet as necessary.
-Minor cleanups of uneeded tags in the projects/properties
|
|
These tools require the use of GModule headers also, so update the include
directories so that the correct gmodule.h will be included instead of the
system-installed version.
|
|
"Install" the new gobject/glib-types.h as well... it is needed.
|
|
There is no longer need to distinguish between gatomic.c and gatomic-gcc.c.
This will avoid gatomic.c from being included in the projects twice.
|
|
Correct the unpacking path of GLib...
|
|
The dependencies on gsettings and glib-compile-schemas were missed-made
up for them here.
|
|
There are some new public headers added for GIO. Make up for them here
in the install phase
|
|
Apparently GObject now depends on libffi. Add it to the dependencies list.
For MSVC, use the libffi-3.0.10(rcx) versions.
|
|
Tell people about the usage of ZLib to avoid the
problem such as the one mentioned in Bug 633977
|
|
-Added projects to compile the glib-compile-schemas and gsettings utilities
-Update .vsprops to install these in "install" phase
-Distribute these projects also
|
|
-Added projects to compile the glib-compile-schemas and gsettings utilities
-Update .vsprops to install these in "install" phase
-Distribute these projects also
|
|
There is no install.vcxproj.filters...oops
|
|
These are the actual GLib VS2010 project files (*.vcxproj,
*.vcxproj.filters) and property sheet file (*.props) that are used
to compile the GLib, GModule, GObject, GThread, GIO DLLs, along with
the gspawn-win32-helper* programs, glib-genmarshal utility and
testglib test program. A readme.txt file is also enclosed for
references for building GLib under VS2010.
Note that the project files for GLib, GIO and GObject are templates
that makes use of the autotools items of my last commit so that maintenance
of those files are simplified as new source files are added to these rather
frequently.
Suggestions are welcome for these-please let me know via BugZilla.
Thank you!
|
|
These are the updates to the autotools files to
ensure the expansion of the GIO, GLib and GObject
project files (*.vcxproj, *.vcxproj.filters) and to
enable the distribution of the VS2010 project files
The actual VS2010 project files will follow shortly
|
|
Due to changes in the GIO APIs/headers, the glib.vsprops
is updated to reflect that in the "install" phase, namely:
-removal of the gperiodic.h header
-addition of GPollable I/O Stream, GTCP Connection and
GTLS headers
|
|
|
|
Some symbols need to be excluded from the .def file as they are set to be so on Win64
|
|
-Made up for missed header files in glib and gio during "install"
-Added macro necessary for GLib/GModule .def generation under Win64
-updated location of getting glibconfig.h.win32 for building
|
|
Added option for people to use an existing PCRE build and updated .def generation for x64 systems (some symbols are set to be excluded from Win64 builds)
Also fixed the filter "PCRE" for the bundled PCRE as file layout changed
|
|
Allow the person compiling GLib to use his/her own copy of PCRE, bug#633075
|
|
Made up for missing required source files in gio.vcproj(in) for Windows builds
|
|
It sucks to have the lists of public headers duplicated in the
Makefile.am files and the glib.vsprops file. But it isn't exactly easy
to work around all the weirdness in autotools, Visual Studio, and bat
files either to do it another way.
|
|
List the additional sources needed in gio/Makefile.am, not in
gio.vcprojin. Fix broken usage of sort. Filter out Unix-only source
files.
|
|
Correspond to GUnixInputStream and GUnixOutputStream. No true async
support though. But that is how the Win32 API is, for files not
explicitly opened for so-called overlapped IO.
The API to create these streams takes Win32 HANDLEs. Not file
descriptors, because file descriptors are specific to the C library
used. The user code and GLib might be using different C libraries.
Also add a test program for the new classes, and a gio-windows-2.0.pc
file.
|
|
Instead, explicitly include gatomic.c.
|
|
|
|
Yeah, we should generate the list of headers to install from the
corresponding Makefile.am files, like the lists of source files to
compile.
|
|
Don't keep the lists of source files for libglib, libgobject and
libgio in the VS project files in addition to the canonical location,
the corresponding Makefile.am files.
Instead, generate the corresponding .vcproj files at make dist time
using the C preprocessor, from template files called .vcprojin. We
still list explicitly in the .vcprojin files some of the
Windows-specific source files, and the sources files of gnulib and
pcre.
|