Jürgen E. Fischer wrote: > > > FMPOV the build system is the real issue not the codebase. > > > The build system is a non-issue, as it doesn't affect the resulting > > binaries. > > Sorry, I don't see what's your point is here.
My point is that you get the same binaries whether you use GNU make or nmake, so it doesn't affect the end result, only the method by which you get there. > > Maintaining DSW/DSP files (or nmake files) isn't a realistic option, > > and anything else will be "foreign" on Windows. > > cmake would work both ways. It can produce Makefiles and MSVC projects > (nmake or DSW/DSP/SLN/vcproj). > > My point was simply, that if GRASS were to use cmake instead of > configure/make most part of making that happen would be on the build > system and not on the codebase itself. >From the (inadequate) online documentation, I can't tell for sure whether it would be suitable. At a first impression, it appears to be too high-level. Such systems tend to either require that you use whatever the system emits without understanding it, or that you understand the inner workings of the system along with all of its targets. It might help if you explain what the problem with the existing system is, given that GNU make is available on Windows. -- Glynn Clements <[email protected]> _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
