Hello List,
As people here might know, the Visual C++ 2008/2010 projects to build
the GNOME parts of the GTK+ and Clutter stack are currently using
autotools to fill in the source file listings during 'make dist', which
was mostly doing the job for getting the project files to be kept
On Wed, Nov 13, 2013 at 12:24 PM, Colin Walters walt...@verbum.org wrote:
On Wed, 2013-11-13 at 17:10 +0800, fanc...@yahoo.com.tw wrote:
-The Python scripts will read from the various Makefile.am's using
Python regex functionality,
My main concern here is about what kinds of additional
Hi,
Speaking as a consumer of the MSVC project files, is it too much to
ask for contributors to maintain the project files statically and
update them whenever they update the makefiles? There is no need to do
this in VS or even Windows; the vcxproj file is easy to maintain via a
text editor.
It
於 2013/11/14 01:24, Colin Walters 提到:
My main concern here is about what kinds of additional restrictions this
might add to the Makefile.am files we are using. For example, would
this script support nested conditionals like:
if BUILDOPT_FOO
if BUILDOPT_BAR
blah_SOURCES += foo-and-bar.c
endif
Hello Arnavion,
Speaking as a consumer of the MSVC project files, is it too much to
ask for contributors to maintain the project files statically and
update them whenever they update the makefiles? There is no need to do
this in VS or even Windows; the vcxproj file is easy to maintain via a
text
-Sources get added/removed/changed (i.e. renamed/moved/split) every now and
then, and updates to Makefile.am may slip pass me until after a release. For
updating the MSVC projects for one project with a text editor (BTW this is
what I use though) may not seem much, but currently I maintain the
