[PlanetCCRMA] Qtractor 0.2.1?

[Nexxus Six]

Fernando,
Thanks for the speedy update to qTractor 0.2.1! =]

If I wanted to recompile my own version with VST support, do you have all of the source files, or... what do I need to do in order to compile a custom (in compliance with Steinberg's license) version?

I have already downloaded Qtractor 0.2.1 source, and Steinberg's VST 2.4 developer packages, so I have the license here, but seem to be missing a few key libraries... (QT4.1???)  What did you do to get this to compile for FC8?

Cheers!
-NexxuSix


----- Original Message ----
From: Fernando Lopez-Lezcano <nando at ccrma.Stanford.EDU>
To: Nexxus Six <nexxusix at yahoo.com>
Cc: planetccrma at ccrma.Stanford.EDU
Sent: Tuesday, September 23, 2008 5:33:40 PM
Subject: Re: [PlanetCCRMA] Qtractor 0.2.1?

On Tue, 2008-09-23 at 15:25 -0700, Nexxus Six wrote:
> Well.. maybe I will wait then... but will the option exist for VST?

Sorry but no. It would require the Steinberg include file and its
license in incompatible with the GPL. 

>  For now, when I run YUM, I get:
> 
> [root at localhost NexxuSix]# yum install qt4-devel
> Setting up Install Process
> Parsing package install arguments
> Resolving Dependencies
> --> Running transaction check
> ---> Package qt4-devel.i386 0:4.3.3-1.fc8 set to be updated
> --> Processing Dependency: libjpeg-devel for package: qt4-devel
> --> Processing Dependency: qt4 = 4.3.3-1.fc8 for package: qt4-devel
> --> Processing Dependency: libGLU-devel for package: qt4-devel
> --> Running transaction check
> ---> Package mesa-libGLU-devel.i386 0:7.0.2-3.fc8 set to be updated
> ---> Package qt4-devel.i386 0:4.3.3-1.fc8 set to be updated
> --> Processing Dependency: qt4 = 4.3.3-1.fc8 for package: qt4-devel
> ---> Package libjpeg-devel.i386 0:6b-39.fc8 set to be updated
> --> Finished Dependency Resolution
> Error: Missing Dependency: qt4 = 4.3.3-1.fc8 is needed by package
> qt4-devel
> 
> But, if I try to YUM install qt4, it says No such package. Is there
> perhaps a few repositories I need to enable (testing, devel, etc) to
> find the right upgrades?

No, it should be in the standard repos. Have you done a "yum upgrade"
recently? You might have the old keys, you will have install the new
fedora release file with the new pointers to their repositories and new
signing key. 

See:
http://fedoraproject.org/wiki/Enabling_new_signing_key

-- Fernando


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ccrma-mail.stanford.edu/pipermail/planetccrma/attachments/20080923/1aef4b20/attachment-0001.html