Hello, Matt
There are two issues:
1. Can one synchronize Developer Studio project with the existent
UNIX-base repository ?
To find a proper solution I'd like to remind MS Developer studio can be seen as
an object of VC++ class.
MFC provides a bunch of methods for that class to do everything one can do from
the "click/drag/drop/popup" interface.
There are methods to "add file" . to "compile" , to "build" etc
This means to synchronize things one have to write a small C++ utility. That would
read the current source tree compare it with the current "Developer Studio" object
and adjust it calling "add/remove" file and "build" methods as well.
2. Another question how to manage "cross" platform project?
So far the only "good" solution we found is the perl script. It is so-called "cons" Perl package.
Perl for Windows is available from www.activestate.com, "cons" is a regular "perl" script
available by "ppm" for example.
For futher information see:
http://www.rhic.bnl.gov/STARAFS/comp/train/cons/ConsInSTAR.html
----- Original Message -----
From: Matthew D. Langston <langston@SLAC.stanford.edu>
To: roottalk <roottalk@pcroot.cern.ch>
Sent: 11 ноября 2000 г. 16:17
Subject: [ROOT] VC++ project files for ROOT and a rootcint add-in
> I am looking for VC++ 6.0 workspace and project description files for ROOT
> 2.25.03. Has anyone created these? These VC++ 6.0 workspace and project
> description files would only be useful for people who are doing ROOT
> development. However, on a related note, has anyone created a set of VC++
> workspace and project description files for creating ROOT programs and
> libraries? This would basically be the equivalent of `root-config --cflags`
> and `root-config --libs` for UNIX development of ROOT programs and
> libraries. Finally, a VC++ "add-in" that automatically calls rootcint to
> generate the CINT dictionaries would be nice.
>
> I realize that probably none of these utilities have been written for VC++
> ROOT development, but I wanted to solicit feedback from Windows ROOT
> developers anyway. Hopefully they exist, but if not then perhaps some of us
> could collaborate and contribute them to the ROOT project. What follows is
> some thought about possible solutions:
>
> It would make sense to want ROOT's project description files for VC++ to
> automatically be kept in sync with the UNIX project description files (i.e.
> the *.mk files and the associated UNIX+make build procedure). This sounds
> like a lot of work. One idea would be to describe the ROOT build procedure
> in an XML file so that project description files could be automatically
> generated for any build system (i.e. ROOT's current UNIX+make build system,
> the VC++ build system, the KDevelop build system, an Automake build system,
> and any other build system that might come down the pipe which users may
> need).
>
> I don't know of any XML schema for describing software build systems, but I
> haven't looked that hard either. Does anyone else? If such a schema
> existed, then maybe it would make sense to use it to describe the ROOT
> project database and build system. We could then trivially add support for
> multiple build systems by writing simple XSLT templates for each build
> system.
>
> I would be willing to contribute XSLT templates for VC++ workspace and
> project description files, and to assist in XSLT templates for UNIX+make
> files, if there were interest in creating an XML schema (or using an
> existing one) which describes ROOT's build architecture. However, it
> wouldn't be worth the effort unless there was enough interest to warrant
> such a change to be officially adopted, since otherwise the ROOT XML file(s)
> would have to be manually updated by hand whenever the ROOT source tree
> changed, etc.
>
> Does anyone else have some thoughts about this?
>
> Regards, Matt
>
> --
> Matthew D. Langston
> SLD, Stanford Linear Accelerator Center
> langston@SLAC.Stanford.EDU
>
>
This archive was generated by hypermail 2b29 : Tue Jan 02 2001 - 11:50:37 MET