summaryrefslogtreecommitdiff
path: root/build
Commit message (Collapse)AuthorAgeFilesLines
* MSVC builds: Add NMake Makefile for Introspection BuildsChun-wei Fan2014-02-257-140/+219
| | | | | | | | | | | | | This adds an NMake Makefile that is used to generate the introspection files for GDK-Pixbuf, which replaces the previous approach of generating them via the Visual Studio Projects. This makes it clearer to people on what things are needed in order to build the introspection files if so desired, and makes things a bit cleaner as the build results can be cleaned away easily. This also takes the recent change in g-i into account, where we no longer pass in the DLL file name but instead pass in the library name on Windows, just as it was done on *nix. The existing .bat file for this purpose is removed as a result.
* Don't Build Introspection Files from MSVC ProjectsChun-wei Fan2014-02-258-253/+2
| | | | | | | | This removes the gengir projects from the Visual Studio Projects, so that this paves the initial step of building the introspection files using NMake Makefiles, as the current approach requires many environment variables to be set in order to build the introspection files successfully, which is a bit clunky.
* Visual Studio Projects: Split the Property SheetsChun-wei Fan2013-12-2626-447/+607
| | | | | | | | | | Split up the Visual Studio 2008/2010 property sheets, so that they can be more easily maintained; also remove items that aren't really needed for the build and merge a few items that are frequently repeated. Also make the copying of config.h from config.h.win32 done with a custom build rule so that we have a clean source tree when cleaning the build from the IDE.
* Declare the removal of Makefile.decl completeColin Walters2013-12-212-6/+2
|
* Two more instances of Makefile.declMatthias Clasen2013-12-212-5/+1
|
* build: Use UNIX Line Feeds for MSVC ProjectsChun-wei Fan2013-12-173-453/+453
| | | | | | ... so that it would be more consistent with the rest of the source files, and application of patches would be easier and cleaner. The README.txt and .sln files under build/win32/vs* still has to have DOS/Windows line feeds.
* build/win32/vs10/gengir.vcxproj: Add PlatformToolset tagChun-wei Fan2013-11-251-0/+4
| | | | | This makes it easier to upgrade to Visual Studio 2012/2013 formats, like the other *.vcxproj files in GDK-Pixbuf.
* Visual C++ Builds: Use Custom Build RulesChun-wei Fan2013-08-305-98/+113
| | | | | | | | ...so that the gdk-pixbuf.def can be automatically updated upon build when gdk-pixbuf.symbols is updated, and that it could be deleted upon a "clean" request. Also drop some unneeded items from the property sheets and fix a typo.
* Fix Visual Studio 2010 Property SheetChun-wei Fan2013-08-131-6/+6
| | | | | Remove unnecessary quotes, which will also restore the ability for the DLL and the gdk-pixbuf-query-modules tool to be relocatable.
* Add note on libpng for Visual Studio BuildsChun-wei Fan2013-06-172-0/+14
| | | | | | | Tell people that the Visual Studio project files will normally link to the latest stable release series of libpng that is supported by the codebase, and people can still use libpng 1.0.x-1.6.x if they choose to do so by changing some settings during the build.
* Visual Studio Builds: Link to LibPNG-1.6Chun-wei Fan2013-06-172-16/+16
|
* Update Visual Studio solutionsChun-wei Fan2013-03-062-0/+15
| | | | | | | | | This will integrate the utility projects to build the introspection files into the main solution files for building GDK-Pixbuf so that one can build the introspection files if he/she chooses to do so (it is not built by default). https://bugzilla.gnome.org/show_bug.cgi?id=694433
* Add Windows .bat to build the introspection filesChun-wei Fan2013-03-067-2/+433
| | | | | | | | | | | | | This adds a Windows .bat utility to build the introspection files for GDK-Pixbuf, which also makes use of Python REGEX abilities to read the autotools files to determine the sources that need to be placed in the filelist file for giscanner (which is itself a Python 2.6+ module) to consume. This will enable one to build the introspection files for Visual Studio builds without the need of using a shell such as MSYS. Utility Visual Studio projects are also included so that one may be able to use them and build the introspection files from the Visual Studio 2008/2010 IDE.
* VS 2010 property sheets: Add command to build introspectionChun-wei Fan2013-02-211-0/+10
| | | | This is meant as a placeholder, and was accidently left out just now.
* Update Visual Studio property sheetsChun-wei Fan2013-02-214-92/+124
| | | | Improve consistency and cosmetic layout.
* Visual C++ 2010 projects: Slight cleanupChun-wei Fan2013-01-232-4/+2
| | | | Get rid of an unneeded tag
* VS2010 install project updatesChun-wei Fan2012-11-201-0/+4
| | | | | I left out the updates to prepare the VS2010 install project for VS2012 in my last commit. :|
* Visual C++ projects: UpdatesChun-wei Fan2012-11-206-8/+28
| | | | | | | | | | -Prepare support for Visual Studio 2012, by adding the PlatformToolset tag to all configs so that we can provide support for VS2012 with minimal effort by simply copying and replacing the VS2010 items with the VS2012 counterparts with scripts. -Improve consistency by using MultiByte character sets for all project configs
* build/win32/vs*/README.txt: Add noteChun-wei Fan2012-05-102-0/+16
| | | | | Add a note telling people about building and using additional image loader modules that are not included in GDK-Pixbuf.
* MSVC support: Build gdk-pixbuf-pixdata and cleanupsChun-wei Fan2012-02-0816-152/+535
| | | | | Add and dist the project files to build the gdk-pixbuf-pixdata utility and purge unwanted stuff from existing Visual C++ projects
* VS support update: Generate .def file in compiler IntDirChun-wei Fan2012-02-084-18/+25
| | | | | | This will make the source directory a bit cleaner during the build, and will avoid confusion with the .def file that is dist in a release tarball (probably we should stop the distribution of the .def file for GDK-Pixbuf?)
* Update Visual C++ projectsChun-wei Fan2012-02-073-0/+3
| | | | | Update gdk-pixbuf.[vcproj|vcxproj|vcxproj.filters] to build the io-pixdata.c that will be required for all builds.
* Update VS property sheetsChun-wei Fan2011-10-172-2/+2
| | | | | Say bye to G_DISABLE_DEPRECATED and the errors that it causes as warnings are instead issued when deprecated GLib items are used.
* Update VS Readme filesChun-wei Fan2011-08-312-0/+16
| | | | | Tell people about the GNOME Live! page that outlines building GDK-Pixbuf and its dependencies with Visual C++.
* Update Visual Studio README.txt'sChun-wei Fan2011-06-292-208/+208
| | | | These files should also have Windows CRLF EOL...
* Re-attempt to correct EOL on VS solutionsChun-wei Fan2011-06-292-195/+195
| | | | | | | This time I realized that I needed to set autocrlf=false on my Windows side... ugh... These are the files that has to have CRLF line endings to work correctly :(
* Reinstate build/win32/vs10/gdk-pixbuf.slnChun-wei Fan2011-06-241-0/+92
| | | | | | This file now should have the DOS/Windows EOL so that it can be recognized correctly by Windows, without the annoying "Unrecognized Visual Studio Version" problem.
* Temporarily remove build/win32/vs10/gdk-pixbuf.slnChun-wei Fan2011-06-241-92/+0
| | | | This files needs to have DOS/Windows EOL...
* Update VS ProjectsChun-wei Fan2011-06-243-13/+5
| | | | | | | | -Set all DLL/LIB files for the GDK-Pixbuf main projects to be output to <Release or Debug>\<Win32 or x64>\bin for all configurations. -Update VS 2008 property sheet to seperate intermediate directories by project
* Refine Visual C++ 2010 projectsChun-wei Fan2011-06-205-30/+1
| | | | | | | -Remove unneeded tags from projects -Seperate intermediate directories for projects to avoid rebuilding/linking on every rebuild and MSBuild errors (et al.) for not being able to write into build log files as they are in use.
* Fix the Visual C++ 2008 Solution fileChun-wei Fan2011-05-051-1/+1
| | | | | Attempt to avoid the crytic "Unrecognized version" in Windows Explorer when attempting to opening it from there directly.
* Update VS2008/2010 README.txtChun-wei Fan2011-05-012-2/+10
| | | | | Tell people about the usage of ZLib to avoid the problem such as the one mentioned in Bug 633977
* Update VS2008/2010 README.txtChun-wei Fan2011-04-182-13/+9
| | | | | -Fixed a typo -Remove some clutter from them
* Update VS Property sheetsChun-wei Fan2011-03-262-26/+26
| | | | Make include directory more consistent with autofiscated builds.
* VS 2008/2010 support-update the README.txt'sChun-wei Fan2011-03-072-2/+6
| | | | Tell people in the README.txt files that LibPNG 1.5.x is needed
* Update VS 2008/2010 Project filesChun-wei Fan2011-03-072-16/+16
| | | | | Since LibPNG 1.5.x is used by default, update the VS 2008/2010 project files to make use of it.
* Fix .gitignore to ignore all generated files.Jon Nordby2011-03-024-0/+8
|
* Remove uneeded items from VS10 folderChun-wei Fan2011-02-231-2/+1
| | | | There is no install.vcxproj.filters...oops
* Visual C++ 2010 Project FilesChun-wei Fan2011-02-2310-0/+1398
| | | | | | | | | | | | | | | | | | These are the VS 2010 project files themselves. Like the VS9 files, the main gdk-pixbuf project (*.vcxproj, *.vcxproj.filters) are expanded from templates during "make dist" as there may be addition of source files for the main library from time to time. This is done in order to simplify maintenance (please see my last commit) This will build the main gdk-pixbuf library (with image loaders built in), and will also build the gdk-pixbuf-csource and gdk-pixbuf-query-loaders utility programs. Like the VS9 project files, one can choose to use GDI+ or the Non-GDI+ (libtiff, libjasper, IJG JPEG etc.) configurations for building the main gdk-pixbuf library. Comments and suggestions are welcome. Please let me know via BugZilla Thank you!
* VS 2010 support: autotools files updatesChun-wei Fan2011-02-232-1/+18
| | | | | | | | | The autotools files are updated for the generation of the main gdk-pixbuf VS 2010 project (*.vcxproj/*.vcxproj.filters) during "make dist" and to ensure the VS2010 project files will be included in the tarball for distribution. The actual VS2010 Project Files will follow shortly.
* Added forgotten macro in VS property sheet fileChun-wei Fan2011-02-231-1/+1
| | | | Build qtif support into the main DLL, left this out, oops
* Bug 639922: Added distribution stuff for Project FilesChun-wei Fan2011-01-243-0/+19
| | | | | | | Added Makefile.am in the new "build" folder and its subfolders so that Visual C++ 2008 Project Files can be distributed with make dist once the Makefile.am in $(srcroot) has the "build" folder added in the SUBDIRS entry
* Bug 639922: Readme file for VC++ 2008Chun-wei Fan2011-01-211-0/+100
| | | | | Oops, I left out the README.txt file that should accompany my last commit...sorry.
* Bug 639922: Visual C++ 2008 Project FilesChun-wei Fan2011-01-216-0/+1152
After checking with Tor Lillqvist, these are committed here... They are done in a similar way to what is now in GLib and GTK+, so that if the main GDK-Pixbuf library receives new source files, the new items will be added to gdk-pixbuf.vcproj automatically when a tarball is released via 'make dist'. Note that the main GDK-Pixbuf library can be compiled in 2 variants, one using the native GDI+ APIs from Windows which is supplied with the Windows Platform SDK (but still makes use of LibPNG+ZLib) and another that relies on 3rd-party image manipulation libraries (libTIFF, IJG JPEG and libJasPer [JPEG-2000 library]) like what is used on other platforms AFAIK. In either case the image loaders are built directly into the main GDK-Pixbuf library (i.e. the INCLUDE_<loader> macros are used). This will build and "install" the main GDK-Pixbuf library and the gdk-pixbuf-csource and gdk-pixbuf-query-loaders utility programs.
View Lorry Controller Status