request musescore 1.0 [SOLVED]
- morgonzola
- Posts: 161
- Joined: Thu 22 Apr 2010, 03:14
- Location: Los Angeles, CA
request musescore 1.0 [SOLVED]
Last edited by morgonzola on Sat 04 Jun 2011, 21:25, edited 2 times in total.
musescore
Dear puppians,
The new version of musescore requires QT 4.7.x. I would prefer to get this thing in two parts: (i) a full and updated QT4.7.x - with bin and dev stuff and GTK+ theme support compiled in - placed in /opt and (ii) the latest musescore that uses these dynamic QT libs. It is a tall order, I know. I compiled QT4 once from scratch and my machine whirred and groaned for about 5 hours.
Many thanks in advance,
vovchik
The new version of musescore requires QT 4.7.x. I would prefer to get this thing in two parts: (i) a full and updated QT4.7.x - with bin and dev stuff and GTK+ theme support compiled in - placed in /opt and (ii) the latest musescore that uses these dynamic QT libs. It is a tall order, I know. I compiled QT4 once from scratch and my machine whirred and groaned for about 5 hours.
Many thanks in advance,
vovchik
- morgonzola
- Posts: 161
- Joined: Thu 22 Apr 2010, 03:14
- Location: Los Angeles, CA
hey vovchik if it just an issue of the time it takes to compile qt i can undertake that if you tell em a gist of what i'm supposed to do. i know about compiling somewhat (aka i know what make is and ./configure)
but i need to know 2 things first
1.what do you mean by bin and dev stuff?
2.and why does it need to be placed in /opt
but i need to know 2 things first
1.what do you mean by bin and dev stuff?
2.and why does it need to be placed in /opt
Dear GustavoYz and morgonzola,
Thanks for the offer. The reason for /opt/qt4 for qt4 is that many puppy distros have placed it there, which is a good idea because updates can be done simply by replacing the /opt/qt4 dir. Otherwise there are bits and pieces of qt4 in /usr/lib, /usr/bin etc. What I mean by a "dev" version is the full qt4, including binaries and header files (so that the user can compile things himself/herself) and also those extra modules needed for musescore and opther apps (such as libqtscript and libqtwebroot). Also, styles plugin support in libqtcore (needed for support of gtk themes).The gtk support business may have changed a bit in qt4.7.x as compared to earlier versions but it still exists. The developers left it out by mistake in one of the qt4.7.x versions, but have restored it in the latest source bundle (according to the developement blogs). You also need to compile qtconfig, that allows for setting the qt4 theme (including the qt4 gtk style).
Musescore itself can reside in /usr/bin but will find the qt4 libs if compiled against a qt4 library located at /opt/qt4.
With kind regards,
vovchik
Thanks for the offer. The reason for /opt/qt4 for qt4 is that many puppy distros have placed it there, which is a good idea because updates can be done simply by replacing the /opt/qt4 dir. Otherwise there are bits and pieces of qt4 in /usr/lib, /usr/bin etc. What I mean by a "dev" version is the full qt4, including binaries and header files (so that the user can compile things himself/herself) and also those extra modules needed for musescore and opther apps (such as libqtscript and libqtwebroot). Also, styles plugin support in libqtcore (needed for support of gtk themes).The gtk support business may have changed a bit in qt4.7.x as compared to earlier versions but it still exists. The developers left it out by mistake in one of the qt4.7.x versions, but have restored it in the latest source bundle (according to the developement blogs). You also need to compile qtconfig, that allows for setting the qt4 theme (including the qt4 gtk style).
Musescore itself can reside in /usr/bin but will find the qt4 libs if compiled against a qt4 library located at /opt/qt4.
With kind regards,
vovchik
- morgonzola
- Posts: 161
- Joined: Thu 22 Apr 2010, 03:14
- Location: Los Angeles, CA
so i got the package from the qt website and just before i do anything i want to check to see if im doing the right thing.
so i did ./configure -help
and got
EDIT wait i just realized that the stars mean defaults, so i should just hunt and find the things that are not default and make them default?
so now i want to do something like etc etc.
to sum it up if it has an option to build it with i should include that option but only if its in the qt/x11 only section? or if it has a no-x and a -x option i should always go with the -x
also does it matter if its static/shared?
(sorry about the huge block of help text )
so i did ./configure -help
and got
Code: Select all
sh-4.1# ./configure -help
Usage: configure [-h] [-prefix <dir>] [-prefix-install] [-bindir <dir>] [-libdir <dir>]
[-docdir <dir>] [-headerdir <dir>] [-plugindir <dir> ] [-importdir <dir>] [-datadir <dir>]
[-translationdir <dir>] [-sysconfdir <dir>] [-examplesdir <dir>]
[-demosdir <dir>] [-buildkey <key>] [-release] [-debug]
[-debug-and-release] [-developer-build] [-shared] [-static] [-no-fast] [-fast] [-no-largefile]
[-largefile] [-no-exceptions] [-exceptions] [-no-accessibility]
[-accessibility] [-no-stl] [-stl] [-no-sql-<driver>] [-sql-<driver>]
[-plugin-sql-<driver>] [-system-sqlite] [-no-qt3support] [-qt3support]
[-platform] [-D <string>] [-I <string>] [-L <string>] [-help]
[-qt-zlib] [-system-zlib] [-no-gif] [-qt-gif] [-no-libtiff] [-qt-libtiff] [-system-libtiff]
[-no-libpng] [-qt-libpng] [-system-libpng] [-no-libmng] [-qt-libmng]
[-system-libmng] [-no-libjpeg] [-qt-libjpeg] [-system-libjpeg] [-make <part>]
[-nomake <part>] [-R <string>] [-l <string>] [-no-rpath] [-rpath] [-continue]
[-verbose] [-v] [-silent] [-no-nis] [-nis] [-no-cups] [-cups] [-no-iconv]
[-iconv] [-no-pch] [-pch] [-no-dbus] [-dbus] [-dbus-linked] [-no-gui]
[-no-separate-debug-info] [-no-mmx] [-no-3dnow] [-no-sse] [-no-sse2]
[-no-sse3] [-no-ssse3] [-no-sse4.1] [-no-sse4.2] [-no-avx] [-no-neon]
[-qtnamespace <namespace>] [-qtlibinfix <infix>] [-separate-debug-info] [-armfpa]
[-no-optimized-qmake] [-optimized-qmake] [-no-xmlpatterns] [-xmlpatterns]
[-no-multimedia] [-multimedia] [-no-phonon] [-phonon] [-no-phonon-backend] [-phonon-backend]
[-no-media-backend] [-media-backend] [-no-audio-backend] [-audio-backend]
[-no-openssl] [-openssl] [-openssl-linked]
[-no-gtkstyle] [-gtkstyle] [-no-svg] [-svg] [-no-webkit] [-webkit] [-webkit-debug]
[-no-javascript-jit] [-javascript-jit]
[-no-script] [-script] [-no-scripttools] [-scripttools]
[-no-declarative] [-declarative][-no-declarative-debug] [-declarative-debug]
[additional platform specific options (see below)]
Installation options:
These are optional, but you may specify install directories.
-prefix <dir> ...... This will install everything relative to <dir>
(default /usr/local/Trolltech/Qt-4.7.3)
* -prefix-install .... Force a sandboxed "local" installation of
Qt. This will install into
/usr/local/Trolltech/Qt-4.7.3, if this option is
disabled then some platforms will attempt a
"system" install by placing default values to
be placed in a system location other than
PREFIX.
You may use these to separate different parts of the install:
-bindir <dir> ......... Executables will be installed to <dir>
(default PREFIX/bin)
-libdir <dir> ......... Libraries will be installed to <dir>
(default PREFIX/lib)
-docdir <dir> ......... Documentation will be installed to <dir>
(default PREFIX/doc)
-headerdir <dir> ...... Headers will be installed to <dir>
(default PREFIX/include)
-plugindir <dir> ...... Plugins will be installed to <dir>
(default PREFIX/plugins)
-importdir <dir> ...... Imports for QML will be installed to <dir>
(default PREFIX/imports)
-datadir <dir> ........ Data used by Qt programs will be installed to <dir>
(default PREFIX)
-translationdir <dir> . Translations of Qt programs will be installed to <dir>
(default PREFIX/translations)
-sysconfdir <dir> ..... Settings used by Qt programs will be looked for in <dir>
(default PREFIX/etc/settings)
-examplesdir <dir> .... Examples will be installed to <dir>
(default PREFIX/examples)
-demosdir <dir> ....... Demos will be installed to <dir>
(default PREFIX/demos)
You may use these options to turn on strict plugin loading.
-buildkey <key> .... Build the Qt library and plugins using the specified
<key>. When the library loads plugins, it will only
load those that have a matching key.
Configure options:
The defaults (*) are usually acceptable. A plus (+) denotes a default value
that needs to be evaluated. If the evaluation succeeds, the feature is
included. Here is a short explanation of each option:
* -release ........... Compile and link Qt with debugging turned off.
-debug ............. Compile and link Qt with debugging turned on.
-debug-and-release . Compile and link two versions of Qt, with and without
debugging turned on (Mac only).
-developer-build ... Compile and link Qt with Qt developer options (including auto-tests exporting)
-opensource ........ Compile and link the Open-Source Edition of Qt.
-commercial ........ Compile and link the Commercial Edition of Qt.
* -shared ............ Create and use shared Qt libraries.
-static ............ Create and use static Qt libraries.
* -no-fast ........... Configure Qt normally by generating Makefiles for all
project files.
-fast .............. Configure Qt quickly by generating Makefiles only for
library and subdirectory targets. All other Makefiles
are created as wrappers, which will in turn run qmake.
-no-largefile ...... Disables large file support.
+ -largefile ......... Enables Qt to access files larger than 4 GB.
-no-exceptions ..... Disable exceptions on compilers that support it.
* -exceptions ........ Enable exceptions on compilers that support it.
-no-accessibility .. Do not compile Accessibility support.
* -accessibility ..... Compile Accessibility support.
-no-stl ............ Do not compile STL support.
* -stl ............... Compile STL support.
-no-sql-<driver> ... Disable SQL <driver> entirely.
-qt-sql-<driver> ... Enable a SQL <driver> in the QtSql library, by default
none are turned on.
-plugin-sql-<driver> Enable SQL <driver> as a plugin to be linked to
at run time.
Possible values for <driver>:
[ db2 ibase mysql oci odbc psql sqlite sqlite2 sqlite_symbian tds ]
-system-sqlite ..... Use sqlite from the operating system.
-no-qt3support ..... Disables the Qt 3 support functionality.
* -qt3support ........ Enables the Qt 3 support functionality.
-no-xmlpatterns .... Do not build the QtXmlPatterns module.
+ -xmlpatterns ....... Build the QtXmlPatterns module.
QtXmlPatterns is built if a decent C++ compiler
is used and exceptions are enabled.
-no-multimedia ..... Do not build the QtMultimedia module.
+ -multimedia ........ Build the QtMultimedia module.
-no-audio-backend .. Do not build the platform audio backend into QtMultimedia.
+ -audio-backend ..... Build the platform audio backend into QtMultimedia if available.
-no-phonon ......... Do not build the Phonon module.
+ -phonon ............ Build the Phonon module.
Phonon is built if a decent C++ compiler is used.
-no-phonon-backend.. Do not build the platform phonon plugin.
+ -phonon-backend..... Build the platform phonon plugin.
-no-svg ............ Do not build the SVG module.
+ -svg ............... Build the SVG module.
-no-webkit ......... Do not build the WebKit module.
+ -webkit ............ Build the WebKit module.
WebKit is built if a decent C++ compiler is used.
-webkit-debug ...... Build the WebKit module with debug symbols.
-no-javascript-jit . Do not build the JavaScriptCore JIT compiler.
+ -javascript-jit .... Build the JavaScriptCore JIT compiler.
-no-script ......... Do not build the QtScript module.
+ -script ............ Build the QtScript module.
-no-scripttools .... Do not build the QtScriptTools module.
+ -scripttools ....... Build the QtScriptTools module.
-no-declarative ..... Do not build the declarative module.
+ -declarative ....... Build the declarative module.
-no-declarative-debug ..... Do not build the declarative debugging support.
+ -declarative-debug ....... Build the declarative debugging support.
-platform target ... The operating system and compiler you are building
on (linux-g++).
See the README file for a list of supported
operating systems and compilers.
-graphicssystem <sys> Sets an alternate graphics system. Available options are:
raster - Software rasterizer
opengl - Rendering via OpenGL, Experimental!
openvg - Rendering via OpenVG, Experimental!
-no-mmx ............ Do not compile with use of MMX instructions.
-no-3dnow .......... Do not compile with use of 3DNOW instructions.
-no-sse ............ Do not compile with use of SSE instructions.
-no-sse2 ........... Do not compile with use of SSE2 instructions.
-no-sse3 ........... Do not compile with use of SSE3 instructions.
-no-ssse3 .......... Do not compile with use of SSSE3 instructions.
-no-sse4.1.......... Do not compile with use of SSE4.1 instructions.
-no-sse4.2.......... Do not compile with use of SSE4.2 instructions.
-no-avx ............ Do not compile with use of AVX instructions.
-no-neon ........... Do not compile with use of NEON instructions.
-qtnamespace <name> Wraps all Qt library code in 'namespace <name> {...}'.
-qtlibinfix <infix> Renames all libQt*.so to libQt*<infix>.so.
-D <string> ........ Add an explicit define to the preprocessor.
-I <string> ........ Add an explicit include path.
-L <string> ........ Add an explicit library path.
-help, -h .......... Display this information.
Third Party Libraries:
-qt-zlib ........... Use the zlib bundled with Qt.
+ -system-zlib ....... Use zlib from the operating system.
See http://www.gzip.org/zlib
-no-gif ............ Do not compile GIF reading support.
* -qt-gif ............ Compile GIF reading support.
See also src/gui/image/qgifhandler_p.h
-no-libtiff ........ Do not compile TIFF support.
-qt-libtiff ........ Use the libtiff bundled with Qt.
+ -system-libtiff .... Use libtiff from the operating system.
See http://www.libtiff.org
-no-libpng ......... Do not compile PNG support.
-qt-libpng ......... Use the libpng bundled with Qt.
+ -system-libpng ..... Use libpng from the operating system.
See http://www.libpng.org/pub/png
-no-libmng ......... Do not compile MNG support.
-qt-libmng ......... Use the libmng bundled with Qt.
+ -system-libmng ..... Use libmng from the operating system.
See http://www.libmng.com
-no-libjpeg ........ Do not compile JPEG support.
-qt-libjpeg ........ Use the libjpeg bundled with Qt.
+ -system-libjpeg .... Use libjpeg from the operating system.
See http://www.ijg.org
-no-openssl ........ Do not compile support for OpenSSL.
+ -openssl ........... Enable run-time OpenSSL support.
-openssl-linked .... Enabled linked OpenSSL support.
-ptmalloc .......... Override the system memory allocator with ptmalloc.
(Experimental.)
Additional options:
-make <part> ....... Add part to the list of parts to be built at make time.
(libs tools examples demos docs translations)
-nomake <part> ..... Exclude part from the list of parts to be built.
-R <string> ........ Add an explicit runtime library path to the Qt
libraries.
-l <string> ........ Add an explicit library.
-no-rpath .......... Do not use the library install path as a runtime
library path.
+ -rpath ............. Link Qt libraries and executables using the library
install path as a runtime library path. Equivalent
to -R install_libpath
-continue .......... Continue as far as possible if an error occurs.
-verbose, -v ....... Print verbose information about each step of the
configure process.
-silent ............ Reduce the build output so that warnings and errors
can be seen more easily.
* -no-optimized-qmake ... Do not build qmake optimized.
-optimized-qmake ...... Build qmake optimized.
-no-gui ............ Don't build the Qt GUI library
-no-nis ............ Do not compile NIS support.
* -nis ............... Compile NIS support.
-no-cups ........... Do not compile CUPS support.
* -cups .............. Compile CUPS support.
Requires cups/cups.h and libcups.so.2.
-no-iconv .......... Do not compile support for iconv(3).
* -iconv ............. Compile support for iconv(3).
-no-pch ............ Do not use precompiled header support.
* -pch ............... Use precompiled header support.
-no-dbus ........... Do not compile the QtDBus module.
+ -dbus .............. Compile the QtDBus module and dynamically load libdbus-1.
-dbus-linked ....... Compile the QtDBus module and link to libdbus-1.
-reduce-relocations ..... Reduce relocations in the libraries through extra
linker optimizations (Qt/X11 and Qt for Embedded Linux only;
experimental; needs GNU ld >= 2.18).
* -no-separate-debug-info . Do not store debug information in a separate file.
-separate-debug-info .... Strip debug information into a separate .debug file.
Qt/X11 only:
-no-gtkstyle ....... Do not build the GTK theme integration.
+ -gtkstyle .......... Build the GTK theme integration.
* -no-nas-sound ...... Do not compile in NAS sound support.
-system-nas-sound .. Use NAS libaudio from the operating system.
See http://radscan.com/nas.html
-egl ............... Use EGL instead of GLX to manage contexts.
When building for desktop OpenGL, this option will
make Qt use EGL to manage contexts rather than the
GLX, which is the default. Note: For OpenGL ES, EGL
is always used.
-no-opengl ......... Do not support OpenGL.
+ -opengl <api> ...... Enable OpenGL support.
With no parameter, this will auto-detect the "best"
OpenGL API to use. If desktop OpenGL is available, it
will be used. Use desktop, es1, or es2 for <api>
to force the use of the Desktop (OpenGL 1.x or 2.x),
OpenGL ES 1.x Common profile, or 2.x APIs instead.
-no-openvg ........ Do not support OpenVG.
+ -openvg ........... Enable OpenVG support.
Requires EGL support, typically supplied by an OpenGL
or other graphics implementation.
-no-sm ............. Do not support X Session Management.
* -sm ................ Support X Session Management, links in -lSM -lICE.
-no-xshape ......... Do not compile XShape support.
* -xshape ............ Compile XShape support.
Requires X11/extensions/shape.h.
-no-xvideo ......... Do not compile XVideo support.
* -xvideo ............ Compile XVideo support.
Requires X11/extensions/Xv.h & Xvlib.h.
-no-xsync .......... Do not compile XSync support.
* -xsync ............. Compile XSync support.
Requires X11/extensions/sync.h.
-no-xinerama ....... Do not compile Xinerama (multihead) support.
* -xinerama .......... Compile Xinerama support.
Requires X11/extensions/Xinerama.h and libXinerama.
By default, Xinerama support will be compiled if
available and the shared libraries are dynamically
loaded at runtime.
-no-xcursor ........ Do not compile Xcursor support.
* -xcursor ........... Compile Xcursor support.
Requires X11/Xcursor/Xcursor.h and libXcursor.
By default, Xcursor support will be compiled if
available and the shared libraries are dynamically
loaded at runtime.
-no-xfixes ......... Do not compile Xfixes support.
* -xfixes ............ Compile Xfixes support.
Requires X11/extensions/Xfixes.h and libXfixes.
By default, Xfixes support will be compiled if
available and the shared libraries are dynamically
loaded at runtime.
-no-xrandr ......... Do not compile Xrandr (resize and rotate) support.
* -xrandr ............ Compile Xrandr support.
Requires X11/extensions/Xrandr.h and libXrandr.
-no-xrender ........ Do not compile Xrender support.
* -xrender ........... Compile Xrender support.
Requires X11/extensions/Xrender.h and libXrender.
-no-mitshm ......... Do not compile MIT-SHM support.
* -mitshm ............ Compile MIT-SHM support.
Requires sys/ipc.h, sys/shm.h and X11/extensions/XShm.h
-no-fontconfig ..... Do not compile FontConfig (anti-aliased font) support.
* -fontconfig ........ Compile FontConfig support.
Requires fontconfig/fontconfig.h, libfontconfig,
freetype.h and libfreetype.
-no-xinput ......... Do not compile Xinput support.
* -xinput ............ Compile Xinput support. This also enabled tablet support
which requires IRIX with wacom.h and libXi or
XFree86 with X11/extensions/XInput.h and libXi.
-no-xkb ............ Do not compile XKB (X KeyBoard extension) support.
* -xkb ............... Compile XKB support.
-no-glib ........... Do not compile Glib support.
+ -glib .............. Compile Glib support.
so now i want to do something like
Code: Select all
./configure -prefix=/opt -gtkstyle -opengl -sm -xshape -xvideo
to sum it up if it has an option to build it with i should include that option but only if its in the qt/x11 only section? or if it has a no-x and a -x option i should always go with the -x
also does it matter if its static/shared?
(sorry about the huge block of help text )
I'm not sure if a static Qt is a good idea...
Static means that it will include the required dependencies, instead of share those from system paths (which is the most usual).
I think that the configure step in Qt should include most of the final configurations about x compatibility by default if you've the headers there -and i'm pretty sure that they're in the devxxx of all versions-.
In example, Lilypond requires python and the static version offered in the official site includes a well-enought version compiled statically, next to Guile and some other deps.
But the included Python, Guile, etc. are dead weight to the rest of the system and made LilyPond really big (like 70 MB).
-I've been surprised by the portable Win*** version offered into the official site. Why Linux doesn't have a portable Musescore version available?
Static means that it will include the required dependencies, instead of share those from system paths (which is the most usual).
I think that the configure step in Qt should include most of the final configurations about x compatibility by default if you've the headers there -and i'm pretty sure that they're in the devxxx of all versions-.
In example, Lilypond requires python and the static version offered in the official site includes a well-enought version compiled statically, next to Guile and some other deps.
But the included Python, Guile, etc. are dead weight to the rest of the system and made LilyPond really big (like 70 MB).
-I've been surprised by the portable Win*** version offered into the official site. Why Linux doesn't have a portable Musescore version available?
- morgonzola
- Posts: 161
- Joined: Thu 22 Apr 2010, 03:14
- Location: Los Angeles, CA
ok so i have made some headway in this business.
so i compiled qt with all the headers pointing at /opt/qt-opensource-4.7.3 ( i made it into an sfs so i need a place to upload it because its kinda big)
by the way, in that sfs should i make links of the usr and lib folders to their respective places?
anyways so i also compiled jack into the mix (can upload that as well) and i tried to do musescore. so i got past the first hurdle and it compiled. then you have to cd in to build and run make lupdate.
this is where the problem is, it says that lupdate cant find libQTxml.so.4 which i did build and is in the /lib folder. I don't know how to make lupdate find this lib. i have tried setting my path to it and it still doesn't pick it up.
i guess i have two questions,
1. how can i make lupdate find the lib
2. should i build musescore again with everything available like the firewire support and all the other things like portaudio?
so i compiled qt with all the headers pointing at /opt/qt-opensource-4.7.3 ( i made it into an sfs so i need a place to upload it because its kinda big)
by the way, in that sfs should i make links of the usr and lib folders to their respective places?
anyways so i also compiled jack into the mix (can upload that as well) and i tried to do musescore. so i got past the first hurdle and it compiled. then you have to cd in to build and run make lupdate.
this is where the problem is, it says that lupdate cant find libQTxml.so.4 which i did build and is in the /lib folder. I don't know how to make lupdate find this lib. i have tried setting my path to it and it still doesn't pick it up.
i guess i have two questions,
1. how can i make lupdate find the lib
2. should i build musescore again with everything available like the firewire support and all the other things like portaudio?
I posted 0.9.6 a while ago for lucid. It's 7.9 M with the libs included, and another 5.4 M with the soundfont (I bundled it separately).GustavoYz wrote:
-I've been surprised by the portable Win*** version offered into the official site. Why Linux doesn't have a portable Musescore version available?
http://murga-linux.com/puppy/viewtopic. ... 624#464277
edit. I see there's also a QT package linked, 41M.
qt4.7.x and musescore
Dear morgonzola,
I see you're making nice progress. Congratulations. If you want somebody to test the qt4, please post it somewhere (a filesharing service). Somebody on the forum must have access to a server:)
With thanks in advance and kind regards,
vovchik
I see you're making nice progress. Congratulations. If you want somebody to test the qt4, please post it somewhere (a filesharing service). Somebody on the forum must have access to a server:)
With thanks in advance and kind regards,
vovchik
- morgonzola
- Posts: 161
- Joined: Thu 22 Apr 2010, 03:14
- Location: Los Angeles, CA
ok so here are some of the odds and ends i have compiled into this plus the
HUGE QT SFS
version = 4.7.3
size=161.11 mb
and jpeeps thanks for the post but im looking for the 1.0 version. but any tips on how you compiled it would be appreciated.
im starting the compile of musescore right now so cross your fingers
HUGE QT SFS
version = 4.7.3
size=161.11 mb
and jpeeps thanks for the post but im looking for the 1.0 version. but any tips on how you compiled it would be appreciated.
im starting the compile of musescore right now so cross your fingers
- Attachments
-
- portaudio-V19-i486.pet
- portaudio.
- (83.25 KiB) Downloaded 857 times
-
- libiec61883-1.2.0-i486.pet
- this was needed to compile ffado just thought id throw it up here
- (98.79 KiB) Downloaded 868 times
-
- jack-1.9.7-i486.pet
- Jack 2 library
- (400 Bytes) Downloaded 873 times
-
- libffado-2.0.0-i486.pet
- ffado firewire library
- (376 Bytes) Downloaded 876 times
- morgonzola
- Posts: 161
- Joined: Thu 22 Apr 2010, 03:14
- Location: Los Angeles, CA
I didn't; just grabbed a version from ubuntu, added necessary libs, and made it into a pet.morgonzola wrote: and jpeeps thanks for the post but im looking for the 1.0 version. but any tips on how you compiled it would be appreciated.
im starting the compile of musescore right now so cross your fingers
- morgonzola
- Posts: 161
- Joined: Thu 22 Apr 2010, 03:14
- Location: Los Angeles, CA
-
- Posts: 13
- Joined: Fri 05 Nov 2010, 07:06
Musescore 1.0
Please upload Musescore 1.0 pet and dependencies pet format also, if u get working this score editor on Puppy Linux 5.2.5 Thanks in advance