vndf-client depends on vndf-server to provide a local server for testing. This means that every time I build client binaries for testing (from vndf-launcher), I also need to build vndf-server, which significantly adds to the build time. This is also completely useless, as the local debug server functionality is not exposed by vndf-launcher.
The most straight-forward solution would be to move the vndf-client binary into a dedicated package, while leaving the library part (which doesn't depend on vndf-server) in the vndf-client package. But maybe this is also an opportunity to clean up the overall package structure.
vndf-clientdepends onvndf-serverto provide a local server for testing. This means that every time I build client binaries for testing (fromvndf-launcher), I also need to buildvndf-server, which significantly adds to the build time. This is also completely useless, as the local debug server functionality is not exposed byvndf-launcher.The most straight-forward solution would be to move the
vndf-clientbinary into a dedicated package, while leaving the library part (which doesn't depend onvndf-server) in thevndf-clientpackage. But maybe this is also an opportunity to clean up the overall package structure.