Just compiled MuseScore; some questions

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Just compiled MuseScore; some questions

char0xff
Hello, new here.
I've successfully compiled MuseScore on Windows 7 following this instructions:
http://musescore.org/en/developers-handbook/compilation/compile-instructions-windows-mingw-git

I got a few questions now.

1)
In the Qt Creator IDE section, the page says:

Build Location:
For the first Cmake run, it will offer a build directory such as MuseScore-build, if MuseScore is your checkout directory. Change this to choose a build directory of MuseScore/build.qtc instead.
Please make sure the name of your build directory does not contain spaces.

It's not clear to me what's MuseScore/build.qtc
So I chose the "MuseScore\build" folder as my build location, where "MuseScore\" is my Git clone folder of MuseScore. I hope this is correct.

2)
I got some CMake errors about Jack, with the last line saying:
This warning is for project developers.  Use -Wno-dev to suppress it.
Not sure if these errors are to be expected. In case I'll post all the errors log.

3)
How do you paste/format segments of code in a mailing list?

4)
I'll take my time to read the code and start with bug fixing, but my first goal is to implement MIDI Out without using Jack, which can then be used with tools like LoopBe or LoopMIDI to connect to a VST. Any particular reason why this hasn't been made yet? Do you have any suggestion? If there's any problem with PortAudio, would you mind a temporary Windows-specific implementation?
Reply | Threaded
Open this post in threaded view
|

Re: Just compiled MuseScore; some questions

lasconic
Administrator
Hi,

1/ No this is probably a bad idea. You don't want your build folder to be an existing directory in the MuseScore code. 

2/ It should be OK.

3/ Except if it's very small, you don't. Use http://gist.github.com or http://paste.kde.org or another service and post a link. Same for an error log.

4/ That could be a separate discussion. The main reason is because it's very hard to have a good RT timer to decide when MuseScore will need to send a MIDI event to the OS.

I saw you said Hello on IRC, stayed 4 minutes and left. That's not going to work :) If you want to use IRC you need to stay there more than 4 minutes.

lasconic

2015-02-06 16:13 GMT+01:00 char0xff <[hidden email]>:
Hello, new here.
I've successfully compiled MuseScore on Windows 7 following this
instructions:
http://musescore.org/en/developers-handbook/compilation/compile-instructions-windows-mingw-git
<http://musescore.org/en/developers-handbook/compilation/compile-instructions-windows-mingw-git>

I got a few questions now.

1)
In the /Qt Creator IDE/ section, the page says:
/
Build Location:
For the first Cmake run, it will offer a build directory such as
/MuseScore-build/, if MuseScore is your checkout directory. Change this to
choose a build directory of /MuseScore/build.qtc/ instead.
Please make sure the name of your build directory does not contain spaces.
/
It's not clear to me what's /MuseScore/build.qtc/
So I chose the /"MuseScore\build"/ folder as my build location, where
/"MuseScore\"/ is my Git clone folder of MuseScore. I hope this is correct.

2)
I got some CMake errors about Jack, with the last line saying:
/This warning is for project developers.  Use -Wno-dev to suppress it./
Not sure if these errors are to be expected. In case I'll post all the
errors log.

3)
How do you paste/format segments of code in a mailing list?

4)
I'll take my time to read the code and start with bug fixing, but my first
goal is to implement MIDI Out without using Jack, which can then be used
with tools like LoopBe or LoopMIDI to connect to a VST. Any particular
reason why this hasn't been made yet? Do you have any suggestion? If there's
any problem with PortAudio, would you mind a temporary Windows-specific
implementation?




--
View this message in context: http://dev-list.musescore.org/Just-compiled-MuseScore-some-questions-tp7579101.html
Sent from the MuseScore Developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer


------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: Just compiled MuseScore; some questions

char0xff
lasconic wrote
1/ No this is probably a bad idea. You don't want your build folder to be an existing directory in the MuseScore code.
I see. What's this "MuseScore/build.qtc" anyway? I dont' understand that sentence in that page.

2)
CMake logs: https://paste.kde.org/ptnfb4cpp

About IRC, I know, I was just looking around and then I found the mailing list and I preferred to use that.