Missing build documentation

[tsundoku39]

I don't see anything in the Readme or elsewhere that describes how the project is to be compiled. While I'm trying to unravel it myself, I'm running into errors, and I would like a reference for what kind of build environment is expected and how the binaries were produced, especially for Linux. Could this information be added to the Readme?

[Jo2003]

Hi, sorry, right now I haven't the time to go in detail about the whole build stuff. Since you are interested in Linux here are some informations:

• as Linux build environment I use Ubuntu 18.04
• you need build-essential, cmake, git, qt5-default, qt5-qmake, qtbase5-dev-tools, qt5-doc
• to build this tool you have to init and update the submodules:
  • git submodule init
  • git submodule update
• you need to build some libs since they change in later Ubuntu versions: https://github.com/Jo2003/cd2netmd_gui/blob/main/linux.md
• for Ubuntu 18.04 all these libraries are already prebuilt (so you don't need the step above)
• the build is done through cmake:
  • mkdir -p ~/build_cd2n && cd ~/build_cd2n
  • cmake -DCMAKE_BUILD_TYPE=Release ../[path to git repo]
  • make
  • cd ../[path to git repo]
  • ./create_deb.sh ../build_cd2n/netmd_wizard

Hope this helps, Jörg

[tsundoku39]

Thank you for the details.

I'm confused by the linux.md page contents, though. Does this mean the project has a maximum compatible version of libraries like json-c and libcdio? Does it need to be built against your own forked version of libcue? I'm not clear on what is happening with the whole prebuild setup described here.

[Jo2003]

The libraries listed in linux.md getting incompatible updates in the next Ubuntu versions (18.10 and later). To not break the compatibility of the App in these later Ubuntu versions I decided to pre-build these libraries and link them statically to the App.

Yes, you have to use my fork of libcue since the original has some naming issues in combination with libcdio (function naming).

If you build for your version of Linux only you can use the libraries shipped with your distro. But also in this case you might end up with the libcue naming issue.

If you need further help please give some further details about the problems you face. If you are confused, tell what exactly confuses you.

[tsundoku39]

I was mostly confused by the prebuild arrangement because it is unusual for a Linux package, and while I see a lot of minimum version dependencies for packages, a maximum version dependency is much less common. What are the specific compatibility breaks?

When I have some time to focus on it, I may try tweaking the build setup for my own purposes to use system packages when possible, but the libcue vs. libcdio situation is really unfortunate. Thanks for clarifying your intentions!