@Sufian, Thanks for chiming in. We need the help!
We use QT for our GUI (and many other items). - If you're an IDE-type person, Dave French @curlymorphic had a YouTube video he sent me a while back which outlined how to configure Qt Creator and CMake to get LMMS to build in an IDE. - If you're a kate/gedit/vi/emacs type coder, you can get started right away with the tutorials that @musikBear linked above In regards to OS... are you on Linux, Mac or Windows? - Windows doesn't have a working build tutorial yet. I tried for a few days and was unsuccessful <https://github.com/tresf/lmms/wiki/Compiling-lmms-(on-Windows)>. Linux is currently recommended. Ubuntu is the quickest platform to get started with. - Linux building is pretty straight forward on all distros so as long as you know your way around the package managers to meet dependencies. Debian and Ubuntu are pretty much a copy and paste of commands to get started. - Mac building is pretty straight forward as well. Homebrew will probably get you started faster than MacPorts, but our tutorial is still written around MacPorts, so you'd be fastest looking at this travis recipe <https://github.com/LMMS/lmms/blob/master/.travis/osx..install.sh> . In regards to patches, we use Pull Requests exclusively now. - If you're not familiar with PRs and GitHub, this might be your biggest battle at first - They allow us to comment and make tweaks before patches are merged - If you're already familiar with GitHub pull requests, you can get started now, just fork our main branch, master preferably. In regards to what work to do... that is often the second biggest battle... - Our bug tracker on GitHub is a good place to start. Just post a comment before starting if unsure. - Development is slow at the moment, so there isn't a whole lot of toes to be stepping on, so to speak. - GUI vs. Core/DSP - Depending on your expertise, we have many areas in both GUI and the core digital signal processing areas which need help. We can point you in the right direction if needed. - Cumulative bug reports -- We have some large bug reports that try to organize some features and bugs into a centralized area... here they are: - Better MIDI support: https://github.com/LMMS/lmms/issues/1472 - Better Sample Track support: https://github.com/LMMS/lmms/issues/1471 - Better Jack support: https://github.com/LMMS/lmms/issues/1467 - New UI / Better Transport: https://github.com/LMMS/lmms/issues/1911, https://github.com/LMMS/lmms/issues/1357 - Better Color Handling: https://github.com/LMMS/lmms/issues/1665 Hopefully that's enough to get you started. Welcome. :) -Tres - tres.finocchi...@gmail.com On Fri, Jun 12, 2015 at 6:19 AM, musikbear <mkru...@hotmail.com> wrote: > This link > https://lmms.io/get-involved/ > under 'Develop' > And this from the wiki > https://github.com/LMMS/lmms/wiki > about creating your own fork and repository, should give you first ideas. > I > am not sure everything is fully updated, but someone else will chime in, if > so :) > > > > -- > View this message in context: > http://linux-multimedia-studio-lmms.996328.n3.nabble.com/How-to-get-started-tp11795p11796.html > Sent from the lmms-devel mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > _______________________________________________ > LMMS-devel mailing list > LMMS-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lmms-devel >
------------------------------------------------------------------------------
_______________________________________________ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmms-devel
