Mille grazie ! Mil dankojn !

You got it.

I have now an operating beta, when specifying paths before launching the 
binary from a terminal. (the binary itself was compiled under these paths)

leleu@leleu-portable:~/musescore/MuseScore/build.release/mscore > export 
QT_PLUGIN_PATH=/home/leleu/Qt5/5.3/gcc_64/plugins/
leleu@leleu-portable:~/musescore/MuseScore/build.release/mscore > export 
LD_LIBRARY_PATH=/home/leleu/Qt5/5.3/gcc_64/lib/
leleu@leleu-portable:~/musescore/MuseScore/build.release/mscore > 
./mscore -F


So I hope that my next upload are also operational, at least for debians 
and derivatives, perhaps with some tweaking


However make install doesn't give an operational entry in the menu.
I try to get one operating menu entry




la 15/09/2014 11:26, ABL skribis (esperanto estas la unua internacia lingvo)
> I think that I (hopefully) solved the problem.
> First, I managed to reproduce your problem on my system: it happens if I
> rename the Qt folder.
> In this case the qt.conf approach does not seem to solve the problem.
> So I think that something strange actually happened during your both Qt
> installations.
>
> I had to use the LD_LIBRARY_PATH (so that the application does not try to
> use the Qt installed in the system) AND I also had to define QT_PLUGIN_PATH
> to point to Qt plugins path.
>
> In summary, in my environment:
> export
> LD_LIBRARY_PATH=/home/antonio/Qt5.3.1_renamed/5.3/gcc_64/lib:$LD_LIBRARY_PATH
> export QT_PLUGIN_PATH=/home/antonio/Qt5.3.1_renamed/5.3/gcc_64/plugins
> These should work also for you, provided, of course, that you adjust the
> PATHs according to your installation(s).
>
> Let me know if this solves the problem (...finger crossed...)
>
> Ciao,
> ABL
>
>
>
> --
> View this message in context: 
> http://dev-list.musescore.org/Linux-Mint-64-compilation-fails-tp7578930p7578994.html
> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Mscore-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

Reply via email to