Hi,
I would be interested to use CMake. I have bin started with CMake a view years ago and we use it for our project to. If you send me the CMakeLists.txt files, I will check it on MAC, cygwin and MSVC the next week.
If WIN32 is a Target too, in my experience, CMAKE are better than GNU autotools.
PS: I used the c:\usr prefix because the net-snmp WIN32 binary distribution use this prefix too.
//claus
On 28.12.2009, at 22:04, Pau Garcia i Quiles wrote:
On Mon, Dec 28, 2009 at 8:56 PM, Juergen Schoenwaelder j.schoenwaelder@jacobs-university.de wrote:
On Sat, Dec 26, 2009 at 12:10:53PM +0100, Claus Klein wrote:
I had to build libsmi with MSVC 2005 and had some little problems to build it from last released distribution.
I have tried to incorporate the changes as far as I understood them. The change of the installation target from c:\smi to a more Unix style c:\usr installation setup I think first needs agreement by the Windows users on this list. So any comments on the suggested change below?
config.nmake change default install path and add missing install dir:
MIBROOT = c:/usr/share/smi/mibs PIBROOT = c:/usr/share/smi/pibs INSTROOT = c:\usr INCDIR = $(INSTROOT)\includeI also might have missed something else; please check and send me a unified context diff.
Somewhat related to this: I have a CMake build system for libsmi, which works on Linux and Windows. It should work on other platforms, too, but I have not tried.
Instead of maintaining two build systems (one for Unix, one for Windows), only one (the CMake one) would have to be maintained. See http://www.elpauer.org/stuff/learning_cmake.pdf if you don't know CMake (slide 10 shows the workflow with CMake).
It's a bit outdated (I developed it in late-July) but I could update it if you are interested in replacing autotools + NMake with CMake.
-- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer)