GNOME Bugzilla – Bug 681965
Clean up the autotools files on the parts used for Visual C++ project generation
Last modified: 2015-09-15 12:04:16 UTC
Created attachment 221344 [details] [review] Enhance the autotools files for header "installation" on MSVC Hi, As it seems that we get changes in headers (additional/removal/deprecation/renaming) in the development phase of GTK+ quite often, I thought it might be a good idea to update the autotools files and property sheets so that the listings of the GDK/GTK+ headers to install in the property sheets can be made up-to-date with every GTK+ release. So, this is the patch for this enhancement. With blessings, thank you! p.s. I will remove the existing gtk+.vsprops and gtk+.props once this bug gets the nod.
Created attachment 266140 [details] [review] Use Python instead of custom autotools scripts to Generate the Visual Studio Project Files Hi, I thought it might be a better idea to move the scripts that were used to generate the Visual C++ project files to Python 2.x/3.x, as: -This removes clutter from the various Makefile.am's -We can add support for generating the projects for more parts of the package quite easily with Python -The project files can be re-generated quite easily, even under Windows, as only a Python 2.x/3.x interpreter is needed. This can still be called easily from 'make dist' by calling the Python scripts with the necessary arguments. -Easier to maintain, as one would not need to worry about what platform the script is run on, so we don't need to filter out sources from platform so-and-so and inject the sources needed for Windows. p.s.: The nmake-exe part in the scripts will be added/updated later with another patch as that is for building the GTK+ test programs with NMake Makefiles, to simplify testing the MSVC builds of GTK+. With blessings, thank you!
Hi, As it seems that
Created attachment 284373 [details] [review] Add common autotools module used for generating MSVC Projects from their respective templates Hi, As it seems that not adding tool requirements and using non-autotools scripts to read autotools files is preferable, it might seem that adding a common module, not unlike the one that is already in use for generating the introspection files ($(INTROSPECTION_MAKEFILE)), is probably better. So, this is my take on adding that module, which can be shared across projects...
Created attachment 284374 [details] [review] Cleanup and enhance the autotools files for Generating MSVC Projects Hi, This updates (cleans up) the various autotools that is currently used to generate the MSVC projects by using the common autotools module (attachment 284373 [details] [review]), and also add gdk-win32 and gtk3-demo to the projects that has their projects being generated as well. The other bonus to this clean-up is that now the property sheets for "installing" the headers are also generated, so that it will be kept up-to-date during releases as headers frequently change during a development cycle. With blessings, thank you!
Created attachment 301784 [details] [review] Add common autotools module used for generating MSVC Projects from their respective templates (take ii) Hi, This is the updated version of the common autotools module that is used to generate the complete MSVC 2008/2010 projects from their respective templatess, as this avoids the use of realpath(1), as there are many incompatible realpath(1) implementations out there that are packaged by different distros.
Created attachment 301785 [details] [review] Cleanup and enhance the autotools files for Generating MSVC Projects (take ii)
Hi, (Sorry, I mistaken hit enter on my keyboard to miss out the comments part, when I did comment to upload the new patch) This is the updates to gdk/Makefile.am and gtk/Makefile.am where we generate the complete MSVC 2008/2010 project files from their respective templates, using the autotools module in attachment 301784 [details] [review]. This cleans up these 2 Makefile.am's, and has the added benefit of making the headers list to "install" in the property sheets automated (i.e. done during 'make dist' as well), where we can avoid a broken "installation" of the MSVC builds if the headers listings are not updated in time for release. This also expands such automation of project file generation and header installation, if applicable to the following items: gdk-win32 gdk-broadway gtk3-demo gtk3-demo-application gtk3-icon-browser gail-util So that the maintenance of project files related to these can also be simplified. With blessings, thank you!
Created attachment 311001 [details] [review] Cleanup and enhance the autotools files for Generating MSVC Projects (take iii) Hi, This replaces attachment 301785 [details] [review] so that all the needed changes are in place. With blessings, thank you!
Fan, you are the maintainer the facto so go ahead! Thanks
Hi Nacho, Thanks for giving me the go-ahead! The patches were pushed as: -Attachment 301874 [details]: deb632c (with Paolo's suggested note from bug 735429) -Attachment 311001 [details]: d836a52 Also, another commit was pushed to remove the static projects that were superseded by this patch series as 908850c. Will close this bug now, after double checking with 'make -j8 dist', meaning that these will no longer get in the way of 'make -jN dist'. With blessings, thank you!