You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently launching lmms from the build directory without installing results in a mostly broken setup. A fair number of plugins complain that they cannot be found and virtually all UI graphics missing. A user should not be forced to install the software (regardless to the fact that you can specify the install directory) in order for it to be functional.
Steps to replicate.
get a system with no prior lmms installation
clone and mkdir build && cd build && cmake .. && make && ./lmms
Expected Result
Lmms to launch normally and to present the user with various dialogs concerning this being the first use of the program
Actual Results
Lots of warnings and windows looking like
The text was updated successfully, but these errors were encountered:
It makes sense to me that the program would require some level of installation step; why would I expect that the object tree has the same structure as the output tree for all components?
On the other hand, you don't have to install to your system directory. My build script looks like:
rm -rf build target; mkdir build target
cd build
cmake ../lmms -DCMAKE_INSTALL_PREFIX=../target &&time make -j8 install &&../target/bin/lmms
cd ..
Currently launching lmms from the build directory without installing results in a mostly broken setup. A fair number of plugins complain that they cannot be found and virtually all UI graphics missing. A user should not be forced to install the software (regardless to the fact that you can specify the install directory) in order for it to be functional.
Steps to replicate.
Expected Result
Lmms to launch normally and to present the user with various dialogs concerning this being the first use of the program
Actual Results
Lots of warnings and windows looking like
![Broken GUI](https://camo.githubusercontent.com/ee772129561ea82160586084612809424b15f161ee0f02c9a0599d29a90e9f13/687474703a2f2f66756e64616d656e74616c2d636f64652e636f6d2f746d702f62726f6b656e2d6c6d6d732e706e67)
The text was updated successfully, but these errors were encountered: