davejohncole

If you are actively using the code then you should probably fork the project. I am not using kea in my current job, so you actively using the code means...

If more than a few people are using this project then forking might be counter-productive. I really did not know that anyone was using this code. I am willing to...

You are trying things that I have not done so I am interested to see how things turn out.

Sure. I keep getting distracted by my other (hardware and software) project, so it is not fair on you to leave you hanging. By all means fork my code and...

I was wondering how bad my initialisation method for those smart pointers was. The C++ pointers live in memory allocated on the C heap (by the Python interpreter), so C++...

Ahhh. I just realised. They have changed some more API with 1.8.0. I need to add some more conditional compilation to handle the changes. I am building 1.8.2 at the...

Hmmm... I am going to need to download a different docker image to replicate your problem. It compiled fine with centos:7. ***@***.***:~/play/kea_python$ VER=1.8.2 make build-kea docker build --build-arg VER=1.8.2 --tag...

I am now building the code with 21.04 from here https://hub.docker.com/_/ubuntu - it takes a while, but I will get there. If/when I make any progress I will send another...

I have not tried 1.8.0, but have built 1.82 fine on ubuntu 21.04 without the errors you see, The thing that worries me is I am seeing the same warnings...

Sorry for being unresponsive. Work has been a bit insane lately. I remembered that in the past I had worked with someone a lot more C++ savvy than me. I...