From: Doug M. <mc...@ia...> - 2012-07-06 19:00:59
|
I tested this out and the build appears OK. It seems that the cppdom-config script is missing from the install target. I am not sure how important this is. I can add it if it is needed. Also, it seems there is a bunch of CMake "cruft" in the cmake directory. Is this needed? Doug On Jul 4, 2012, at 3:34 PM, Patrick Hartling wrote: > I copied the CMake build into the trunk and the 1.2 branch. If it needs to be added to the 1.0 branch, I can do that quite easily. > > -Patrick > > On May 25, 2012, at 9:27 PM, Doug McCorkle wrote: > >> Patrick, >> >> This seems like a useful thing to merge. There are some recent changes to scons that appear to be wrecking havoc with some of our scons builds so we are also looking at migrating away from scons. If it is merged I can test it and provide patches for things that fail. >> >> Doug >> >> On Oct 9, 2011, at 9:37 AM, Patrick Hartling wrote: >> >>> Due to my regrettably limited time for, well, virtually everything, I hadn't noticed that Ryan Pavlik made a CMake build for CppDOM. I was just looking it over, and while it appears to have a lot of things not needed for building CppDOM, it seems to me that it would be a good addition to CppDOM. I am not sufficiently skilled at reading CMake code to tell if it supports everything that the SCons build does, but to be blunt, I am pretty sick of SCons. Even if the CMake build isn't quite ready to replace the SCons build, I would be glad to see CMake available for building CppDOM. Would it be worthwhile to merge Ryan's CMake build into the CppDOM SVN trunk? If so, I can do the initial merge and checkin. Would anyone have time to add information to the README file explaining how to use this build, possibly promoting it as the preferred alternative to the SCons build? >>> >>> -Patrick |