Neal asks:
I wanted to know what is going on with the development of HawkNL? HawkNL 1.7 beta 1 has been sitting there for a long time now, and I’m sort of worried that the Hawk* libraries are basically dead. I’m working with a guy on building a game engine using HawkNL, so I have been keeping an eye on it.
My response:
Yes, my projects have gotten a little dusty, but they were left in a state that many people have been able to continue to use them in the interim.
I have been slowly allocating more time to Hawk Software, and will soon begin a series of updates. HawkNL 2.0 will have major changes, but the API will contain as few changes as possible for greater backwards compatibility. The features and boundaries between HawkNL and NLU will be more defined, and some features that crept into NL will be moved to NLU.
November 16th, 2009 at 3:34 PM
Hi Phil,
I’m the author of GNE, Jason Winnebeck (aka Gillius). I’ve been working on building a new release of the software, mostly just to focus on the build environment. A key part of making GNE a lot easier to build also depends on HawkNL. I wanted to make a deb (Debian/Ubuntu package) for GNE, but that also requires packaging HawkNL. In 2006 I did a fork of HawkNL to convert it to use automake, libtool, and also to Debianize it. But I never released that, because I never released an updated GNE (wow it’s been so long).
Do you have any interest in the patches/modifications made? I put the original project into a local SVN then did all of my modifications onto that.
I converted GNE over to CMake, and after having more experience with CMake and also with Debian packaging I am thinking to revisit the build system and possibly even scrap the autotools version and go with CMake instead. I’m not sure yet, but I only used autotools once, and that was to redo the build system for HawkNL and I barely understood it, so I’m not sure I could maintain that as easily as a CMake, and CMake has the benefit of working also in Windows to replace the MSVC workspaces.
The only other significant change I had to make is renaming the libNL.so to libhawknl.so, since there is already a “libnl” in Debian. I didn’t HAVE to rename nl.h header file because libnl doesn’t provide an nl.h, so I didn’t, but it should probably take on a new name.