I guess I'm very confused. All modern flavors of Visual Studio *ship* cmake and ninja. The CMake config lets us toggle options, things that static build files can't do well. CMake will emit nmake, or ninja, or vcproj/sln. And as noted elsethread, it should be able to build for Linux as easily as Windows, although many more autoconf style tests are needed still.
Please explain why this is problematic 20 years later, now that CMake is a very well established and well maintained solution? On Wed, May 13, 2020, 16:49 Gregg Smith <g...@gknw.net> wrote: > Well, with very little work I'm sure the dsw/dsp will still work in any > Visual Studio IDE of the day. They are not that difficult to modify by > hand. The mak/dep files have to be generated since they are not in > trunk. I wish they were in trunk even though they are more difficult to > hand modify, but they still can be. > > Prebuild events I admit are quite tough to hand job into both mak/dsp if > needed. > > Regards > > On 5/13/2020 1:48 PM, Mladen Turk wrote: > > On 13/05/2020 22:08, Gregg Smith wrote: > >> > >> #1, I think this may be your opinion but not so much mine. No, > >> .mak/defs are not in trunk but they never have been and they have been > >> added at fork to currently all the 1.0 series. And unless I'm > >> mistaken, 1.7 was not that long ago. > >> > > > > Well, I'll try to make cmake build for winXX in apr/trunk fully working, > > since it's already there and usable at least for apr-1.[6,7] > > > > But if someone have a will to manually edit and create those .dsp files > > and then generate .mak files from them ... fine. > > > > > > Regards >
