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!

[ghostseven]

I was wondering if there was any build info for MacOS as I am struggling to get this to build.

[Jo2003]

I can confirm that building the tool isn't easy nor straight forward. Yes, I plan a release with binaries. For Mac I'm only able to build for the Intel Macs since I don't have an ARM Mac (Intel also only through VM).

[ghostseven]

Thanks for the response, I appreciate it is a pain supporting multiple platforms and it is great that you do. I am running the build on an intel mac as I figured that would be easier. I assume I have to do a fair bit more than just tweak the create_mac_bundle.sh and make sure I have the right version of QT installed. Thank you again for this project and the hard work you put in.

[ghostseven]

I have actually managed to work out the issues and have got the build working on MacOS.

I have written up a little guide it this will help anyone else. It does require making some changes to CMakeLists.txt and create_mac_bundle.sh. I have uploaded changed versions in the guide. I am not sure if the changes to CMakeLists.txt would break linux builds (the only change that could is the addition of a missing cdrutil.cpp in add_executable, but I could patch that to only do the for Apple builds), so I have not done a fork and pull request yet.

Also with further testing I have had to replace libsndfile.1.dylib in the prebuilt folder with the one from the latest live build. If i don't there LP2 and LP4 do not work.... It is very odd. But that is a quick and dirty fix for it.

MacOS Build

OS

Build tested on MacOS Sequoia (Intel)

packages installed via Brew

brew install qt@5 libusb libgcrypt

create src folder and checkout sources

cd ~ && mkdir -p src && cd src
git clone https://github.com/Jo2003/cd2netmd_gui.git

copy updated CMakeLists.txt, create_mac_bundle.sh and libsndfile.1.dylib to src

cd ~/src/cd2netmd_gui
curl https://www.ghost7.com/netmdwiz/CMakeLists.txt > CMakeLists.txt
curl https://www.ghost7.com/netmdwiz/create_mac_bundle.sh > create_mac_bundle.sh
curl https://www.ghost7.com/netmdwiz/libsndfile.1.dylib > prebuilt/mac/lib/libsndfile.1.dylib
chmod +x create_mac_bundle.sh

patch pkg config files

cd ~/src || exit 1; D=$(pwd); find cd2netmd_gui/prebuilt/mac -name "*.pc" | while IFS= read -r i; do echo "Updating: $i"; sed -i '' "s|/Users/joergn/src|${D}|g" "$i"; done

export pkg-config folder

cd ~ && export PKG_CONFIG_PATH=$(pwd)/src/cd2netmd_gui/prebuilt/mac/lib/pkgconfig

create build folder

cd ~/src && mkdir -p build_nw && cd build_nw

configure build and compile

cmake -DCMAKE_BUILD_TYPE=Release -DQt5_DIR=$(brew --prefix qt5)/lib/cmake/Qt5 ../cd2netmd_gui
make

create mac bundle

cd ~/src/cd2netmd_gui
./create_mac_bundle.sh ../build_nw/

install the app

The app is located at ~/src/build_nw/ copy it to Applications or wherever you wish to run the program from.